A shared name is not only a branding inconvenience. In a source-based answer, it becomes a fork in the evidence trail, and Perplexity may choose the wrong road if the page gives no signs.
Type a common French business name into Perplexity with a service query and the answer may look confident enough to be dangerous. “Atelier Saint-Martin,” “Cabinet Moreau,” “Azur Conseil,” “Maison Bernard” — names like these belong to more than one real business. Add a city and the answer improves, but not always. Add a trade and it improves again, until an old directory, a branch page, or a better-structured namesake pulls the source trail sideways.
A composite scenario: a 23-person compliance consultancy in Lyon shares a short trade name with a small HR advisory office in another French city and a former training provider whose old listing still appears in aggregator pages. The Lyon firm works with small food manufacturers on HACCP documentation, audit preparation, and supplier traceability. Its owned pages use the short name everywhere. The legal name appears only in a footer image. The English partner profile calls it “a French compliance consultancy.” Perplexity has enough pieces to build an answer. It also has enough loose pieces to build the wrong one.
Name confusion begins before the answer looks wrong
The frightening part of a shared-name problem is that the answer may not look obviously broken. Perplexity can cite the right city and still borrow the wrong category. It can name the right company and still attach services from a namesake. It can cite a directory for the Lyon firm and an English profile for another business with the same short name, then blend the two into one tidy paragraph.
This is why I do not begin with the brand name alone. I begin with name plus city, name plus service, name plus legal form, name plus founder if public, name plus English variant, and sometimes name plus old address. The point is not to create a theatrical test set. It is to see where the entity boundary cracks.
An entity boundary is the set of public facts that lets a source-based answer distinguish one business from another because the name, legal identity, location, trade, and service scope agree across sources. If those facts do not travel together, Perplexity may complete the missing parts with a nearby source.
That definition sounds dry. In practice, it is the difference between a buyer finding the Lyon compliance consultancy and a buyer reading about a different “Azur Conseil” that does recruitment workshops in another region. Both may be legitimate businesses. The error is in the stitching.
A shared name turns every weak page into an invitation for Perplexity to borrow identity from elsewhere.
The four name-collision patterns
I use a simple classification during audits: same-name collision, branch bleed, old-name residue, and category borrowing. The names are ugly because the cases are ugly. Clean language would lie.
Same-name collision is the obvious one. Two unrelated businesses share a name. They may be in different cities, sectors, or legal forms. Perplexity’s citations can cross between them when one has clearer public pages. The wrong business does not need to be famous. It only needs to publish cleaner facts.
Branch bleed happens when one location becomes the evidence for another. A business has several offices, or once used a branch address, or appears in a directory with multiple locations. Perplexity cites the Paris page while answering about Lyon, or treats a national page as if it describes every local office. This pattern is especially common when local pages are thin.
Old-name residue is quieter. A firm changed name, merged, moved, or stopped using an English trade name. Old directory pages still carry the previous label. Partner profiles may keep the old wording because nobody had the dull courage to update them. Perplexity sees the old and new names as connected, but it may not know which facts are current.
Category borrowing is the most damaging for specialised practices. The Lyon consultancy’s English partner profile says “management consultancy.” An aggregator says “business services.” Another listing says “training.” The owned French site says “accompagnement qualité.” Perplexity then answers a food-manufacturing compliance query with a generic consulting description. The name is correct. The role is wrong. That is still an entity failure.
These four patterns rarely appear alone. A shared name often combines with old-name residue and category borrowing. That is why a single correction in the footer is usually too weak. The identity has to be repeated at the places where evidence is gathered.
The page must carry the full identity, not just the logo
French business sites often assume the logo does more work than it can. The short name sits in the header. The rest of the page speaks in warm generalities. The legal name, city, and service scope are somewhere in the footer, in an image, inside a PDF, or scattered across contact pages. A human who already knows the business can assemble the identity. Perplexity may not.
For the Lyon consultancy in the composite scenario, the homepage should not rely on “Azur Conseil” alone. A source-worthy identity sentence might say: “Azur Conseil Lyon SAS advises small food manufacturers on HACCP documentation, audit preparation, and supplier traceability in France.” If that is too compressed for the homepage hero, it can sit near the top of the About page or service page. The exact wording depends on the real legal form and scope. The principle does not.
The sentence ties the short name to legal identity, place, audience, and service. It also prevents several wrong paths. It separates the firm from HR consultancies. It narrows “compliance” into food-manufacturing work. It gives English-language answers a stable translation. It makes a directory less necessary because the owned page carries the facts.
A useful entity lock usually has five parts. The public business name. The legal name when relevant. The city or branch. The trade or professional role. The service boundary. For regulated or specialised practices, professional status may also belong there. For local services, service radius may matter more. For chains, branch wording becomes essential.
The awkwardness is acceptable. A clean entity sentence is allowed to feel denser than ordinary brand copy. It is a label on a laboratory sample. Pretty labels are nice. Correct labels prevent the wrong sample from being tested.
Directories are clues, not enemies
When Perplexity confuses two businesses, owners often blame directories. Sometimes they are right: an aggregator may contain a stale address, a wrong category, or a copied description. Still, I prefer to treat directories as clues first. They reveal which identity facts have escaped the owned site.
If a directory states the legal name and the owned site does not, that is a signal. If the directory separates the Lyon office from the Paris office and the owned site gives only a national contact page, that is a signal. If an old profile says “training provider” and the current page never says “we do not provide certification training,” the wrong category has room to survive.
This does not mean the business must mirror directory language. Some directories use blunt categories that make specialists wince. A kinésithérapeute becomes “health service.” A notaire becomes “legal office.” A food compliance adviser becomes “business consultant.” The owned page should correct those reductions with clearer wording, not with another cloud of prestige phrases.
The repair usually begins with a citation table. I write the sources in rows: owned page, map listing, directory, partner profile, old PDF, English page, social profile. Then I mark how each one states name, city, legal identity, role, service, and date. The table often shows a diagonal pattern: every source has one part of the identity, but no source has the whole thing.
Perplexity does not need every source to be perfect. It needs at least one first-party page that carries the whole identity cleanly, and supporting sources that do not contradict it too loudly.
Writing for the namesake you cannot control
You cannot make another French business change its name. You cannot erase every old listing. You often cannot control the way partner pages describe you. What you can do is make your own page the strongest identity source in the cluster.
That means writing against possible confusion. If the name is common, say where this business operates. If there are branches, say which branch the page describes. If the business changed name, publish a short current-name note. If the English category has caused drift, provide a direct translation of the role. If the firm does not provide a service commonly attached to the name, state the exclusion without drama.
For the Lyon consultancy, a compact clarification might read: “This page describes Azur Conseil Lyon SAS, the food-manufacturing compliance consultancy; it is separate from similarly named HR, training, or general advisory firms.” Some owners resist sentences like this because they feel defensive. I understand the discomfort. Yet a source-based answer engine does not share local memory. It needs the fork in the road marked.
The wording should be factual, not anxious. Do not write a long paragraph about confusion. Do not attack namesakes. Do not overfill the page with legal clutter. Place the entity lock near the top, repeat the correct role on service pages, and keep directories aligned where possible.
A business with a shared name needs a stronger identity sentence than a business whose name is unique.
This is not glamorous work. It feels like tightening bolts under a sink while everyone else discusses brand story. But the bolt matters. Without it, Perplexity may cite a page that knows the name but not the business, or a page that knows the category but not the city, or a page that knows the old version and presents it as current fact.
The Numbered Source Note
Footnote candidate — “Azur Conseil Lyon SAS advises small food manufacturers on HACCP documentation, audit preparation, and supplier traceability in France.” Citation rival — an aggregator or partner profile that separates the name, city, and service more clearly. Freshness mark — “Identity and service scope checked for 2026 source listings.” Entity lock — legal name, Lyon office, food-manufacturing compliance role, current trade name, and separation from similarly named advisory firms.