A branch does not become citeable because the brand is known. It becomes citeable when the page gives Perplexity enough local facts to separate one door from the others.
A composite scenario I see often: a French service company has six locations, a respectable national page, a neat “Nos agences” section, and one branch that Perplexity keeps treating as the whole business. Almost always it is Paris. The answer says the company is “based in Paris,” cites the Paris office page, and then uses that same source for questions from Lyon, Nantes, Rennes, or Lille. One small detail breaks the smooth story: the Paris page may not even be the strongest branch commercially. It is just the cleanest page.
The other branches exist, but they exist like faint pencil marks. A map pin, a phone number, a copied paragraph, maybe a staff photo with no caption. The Paris page has a proper address, opening hours, a named manager, a few local references, and a date line for the current service area. When Perplexity has to footnote the answer, it takes the page with the best handle. It is not thinking, “Paris is more important.” It is finding the only branch that can be cited without stitching facts from three places.
The brand page is usually too heavy to carry branch facts
The first trap is the national brand page. Owners like it because it feels efficient. One polished page describes the company, the services, the values, the sectors, and the cities served. The page says, in one breath, that the firm operates in Paris, Lyon, Marseille, Bordeaux, and Nantes. Then the branch pages are treated as contact cards.
For ordinary visitors, that may be enough. A human can infer that the Lyon number belongs to the Lyon office and that the services described on the main page are available there unless stated otherwise. Perplexity has a different problem. It must decide which page supports which sentence. If the answer says, “The Lyon office offers audit preparation for small food manufacturers,” the source needs to make that branch-level fact visible. A national sentence plus a Lyon address may be too loose.
In a composite case based on several B2B service audits, the typical setup is a consultancy with a strong Paris page and thinner regional pages. The Paris page names the practice areas, includes a few client sectors, shows office hours, and uses wording such as “our Paris team supports food, cosmetics, and packaging clients.” The Lyon page says only “contact our Lyon office” and repeats the national promise. Perplexity then cites Paris for brand-level questions and ignores Lyon for regional questions. The Lyon branch is present, but not source-shaped.
That is the awkward phrase I use in my notes: source-shaped. A branch page becomes source-shaped when it contains the facts needed to support a branch-specific answer without borrowing the identity of the whole brand.
A location page is not a location proof
Many French chains have location pages that are really routing pages. They help the visitor find the nearest office, clinic, agency, shop, or practice. They do not prove much. Perplexity can read the page, but it cannot always use it.
A useful location page needs more than name, address, and phone. It needs a local service statement. It needs hours if hours matter. It needs a current service area if the branch serves surrounding communes. It needs staff or team wording if the branch’s expertise differs from the national description. It needs a boundary: what this branch does, what it does not do, and how it relates to the main entity.
Here is the working definition I use with clients: branch citeability is the ability of one location page to support a specific Perplexity answer about that branch, because the page states the entity, place, service scope, and current local proof in one verifiable surface.
This is not elegant prose. It is closer to a label on a jar in a laboratory. That is the point. Perplexity’s numbered source does not reward the loveliest version of the company story. It rewards the page that lets the answer say something without guessing.
The Paris branch often wins because it accidentally has these ingredients. The head office was photographed. The founding story mentions Paris. The recruitment page names Paris. The press page mentions the Paris team. The Google Business Profile is tidier. The legal footer matches the Paris address. None of this proves that Paris is the only real branch. It only makes Paris easier to footnote.
The copied paragraph makes every branch look like one branch
I have a special dislike for copied branch paragraphs. They are practical, I know. A marketing team writes one “agency description” and drops it onto fifteen local pages with the city name swapped in. It looks consistent. It also creates a strange fog.
Perplexity sees near-identical pages. Paris offers “personalised support for professionals.” Lyon offers “personalised support for professionals.” Nantes offers the same. Bordeaux too. The pages differ only by address and phone. If one of them has stronger external evidence, that one becomes the safe source. Usually it is the oldest, largest, or most-linked office. Again: often Paris.
The fix is not to write theatrical local copy. “Our Lyon team lives the vibrant spirit of the Rhône” will not help. The page needs local discriminators, small and factual. A compliance consultancy might state that the Lyon office works mainly with food manufacturers across the Rhône-Alpes supplier network. A dental chain might state that the Lille clinic provides orthodontic consultations on certain days, while implant surgery is referred to another branch. A tourism operator might state the actual departure port, season, and booking desk.
In most cases, the differences are already known internally. They sit in calendars, sales calls, invoices, appointment scripts, staff notes, and the receptionist’s head. The page just refuses to say them. So Perplexity falls back to the branch that says the most.
Paris becomes the citation magnet, then the model repeats the shape
Once one branch is cited a few times, it becomes a convenient hinge for later answers. I do not mean that Perplexity has a permanent memory in the ordinary human sense. I mean that the public source set around the brand begins to point in the same direction. Aggregators cite the Paris office. Partner profiles use the Paris address. English summaries shorten the company to “a Paris-based firm.” Old media snippets mention a founder in Paris and never mention the branch network.
The result is what I call Paris magnetisation. Paris magnetisation is a citation pattern where branch-light evidence makes the capital office function as the default source for the whole French entity. It is not only a geographic error. It is a source selection error caused by unequal page structure.
For a multi-city company, this can become expensive in quiet ways. A buyer in Lyon asks for a local specialist and gets the brand, but with Paris as the cited proof. A patient near Rennes sees the Paris branch first and assumes local availability is weaker. A non-Paris office becomes a sales satellite in the answer, even when it has its own team, hours, and local expertise.
The data here is subtler than it looks. Perplexity may still mention the other city. It might say, “The company also has a Lyon office.” That sentence feels comforting. But if the numbered source attached to the answer is the Paris page or a national directory, the Lyon office has not really won a citation. It has been included as a secondary fact.
The page must give one citeable local sentence
When I repair branch pages, I do not start by expanding everything. I start with one sentence. The sentence must carry enough local weight to be lifted into an answer.
For a branch, the sentence usually needs the branch name, city, service or role, local area, and one proof or current condition. A plain example: “Viremont Conseil Lyon supports small food manufacturers in the Rhône-Alpes region with HACCP documentation, audit preparation, and supplier traceability reviews.” That sentence is dry, but it can stand in a numbered source. It gives Perplexity the branch, the place, the target client, and the service scope.
Then the page needs supporting details around the sentence. Not much at first. A local address. Hours or consultation rhythm. Named service boundaries. Staff or responsibility wording if appropriate. A short dated update if the service area, appointment delay, or seasonal availability changes. If the branch serves surrounding communes, name them. If it does not provide a service that the Paris office provides, say so plainly. Silence is often read as sameness.
The page should also link back to the national entity without dissolving into it. I like wording such as “This page describes the Lyon office of [legal name], not the Paris head office or the national contact form.” It feels almost too blunt. That bluntness is useful. It locks the branch.
The source trail must agree outside the owned site
Owned pages are my preferred source surface, but branch citation rarely depends on the owned site alone. Perplexity may take its numbered source from a directory, a booking platform, a chamber listing, an industry profile, a map listing, or an English partner page. If those sources say only “Paris,” the branch page has to work uphill.
This is where many owners misread the problem. They see a directory citation and say, “Perplexity prefers directories.” Sometimes it does. More often, the directory is the only place where the machine can see the branch facts in a clean line. The directory may have the city, hours, sector, and phone number in separate fields. Your page may have the same information, but scattered across a hero paragraph, footer, image caption, and PDF.
For non-Paris branches, the repair plan should include a small external alignment check. Does the branch’s legal name match? Does the city appear in the title or heading? Does the aggregator use the old address? Does the English profile collapse every branch into “Paris-based”? Does the staff page assign local people to the right office? These are not glamorous tasks. They are closer to tightening screws on a sign before winter.
When the sources agree, Perplexity has less reason to compress the company into one capital-city entity. When they disagree, it takes the path with the fewest loose parts.
The Numbered Source Note
Footnote candidate — “The Lyon branch of Viremont Conseil supports small food manufacturers in Rhône-Alpes with HACCP documentation, audit preparation, and supplier traceability reviews.” Citation rival — the Paris office page or a national directory with clearer branch fields. Freshness mark — “Updated for 2026 Lyon office services and regional appointment availability.” Entity lock — branch name, legal entity, city, local service area, and wording that separates Lyon from the Paris head office.