A directory citation is rarely just an insult. Read it closely and it becomes a diagnostic note written in machine language: this is the fact your own page made too hard to quote.
A composite scenario from Lyon: a 23-person B2B compliance consultancy works with small food manufacturers. In meetings, the team can explain HACCP documentation, audit preparation, supplier traceability, and the difference between a practical compliance file and generic management advice. On the site, the language is softer. It says the firm supports “operational performance” and “quality processes.” An English partner profile, meanwhile, says “food safety compliance documentation for small manufacturers” in one flat sentence.
A buyer asks Perplexity for a French consultancy that helps small food producers prepare HACCP documentation. The answer includes the firm, but the numbered source goes to the partner profile or an aggregator listing. Sometimes the source even makes the firm look broader than it is, almost like a management consultancy with a food sector side interest. The business is present and displaced at the same time. This is how an annuaire wins: not by knowing more, but by stating less vaguely.
The directory is a rival source surface
Many French businesses treat directories as background clutter. They exist, they are imperfect, and occasionally they bring calls. In source-based answers, they become something sharper: rival source surfaces. If Perplexity needs a numbered footnote and the directory has the cleaner fact, the directory can become the public authority for a business it barely understands.
That is uncomfortable. It also gives us a useful object to inspect.
The question is not “Why is the directory stronger?” in some general domain sense. The better question is: which fact did the directory make easier to cite than the owned page? In the Lyon consultancy composite, the directory had a service label, a sector label, and a short description. The owned site had richer knowledge, but its expertise was wrapped in internal language. “Quality process support” could mean many things. “HACCP documentation for food manufacturers” means something Perplexity can attach to a buyer query.
Here is the working definition I use: a rival source surface is any third-party page that wins a Perplexity footnote because it states the business fact more extractably than the business’s own page. It is a rival because it competes for attribution, not because it competes commercially.
That distinction matters. A directory may be commercially irrelevant and citation-relevant. A buyer may never visit the directory. The answer engine may still use it as the supporting source, shaping the language of the answer before the buyer clicks anything.
First-party pages lose when they require translation into facts
The most common owned-page defect is not absence. It is translation burden. The page contains true material, but Perplexity has to translate it from brand language into source language.
A consultant writes, “We help agri-food actors secure their operational flows.” A human in the sector may understand the hint. A Perplexity answer about HACCP documentation needs a sturdier bridge. It needs to know whether the firm produces HACCP plans, prepares audit files, reviews supplier traceability, trains staff, or only advises management on quality systems.
When the owned page does not say the exact thing, the engine looks elsewhere. The directory’s blunt category field suddenly has value. “Conseil HACCP Lyon” is crude, but it can support an answer sentence. The first-party site may be more accurate in spirit and weaker in citation form.
This is where many repair plans go wrong. The business rewrites the page to sound more impressive. It adds a longer mission statement, a wider “expertise” section, and a few client-friendly abstractions. The citation problem gets worse. Perplexity now has more text to parse and fewer firm facts to footnote.
The repair is smaller and more disciplined. Write the service as an attributable statement. Name the firm. Name the sector. Name the service boundary. Add proof that belongs on the page: typical deliverables, client type, regulatory context, dated update, or named practice area. Avoid the temptation to claim the whole category if the firm works in a narrow lane.
For the Lyon consultancy, a useful first-party sentence might be: “Cabinet Virelle Conseil accompagne les petits fabricants alimentaires en région lyonnaise dans la documentation HACCP, la préparation d’audits et les dossiers de traçabilité fournisseurs.” That sentence is less grand than “operational excellence.” It is more citable.
What the winning directory usually has
In my citation logs, directories that win footnotes tend to carry a small set of plain signals. They are not elegant. They are almost clerical. That is why they work.
First, they classify the entity. They give a trade, profession, sector, or service category. Second, they place it. City, department, region, branch, service area. Third, they attach a contact or operational fact, even a basic one. Fourth, they often contain a one-paragraph description written in the kind of blunt noun phrases a model can reuse.
For local services this may be opening hours, emergency radius, or intervention zone. For specialised B2B providers it may be sector, audience, deliverable, and market. The directory does not need to be rich. It only needs to be easier to quote.
I call these the four directory clues: category field, place field, scope phrase, and current marker. They are clues because they tell the business what to bring back onto its own domain. If the directory’s category field is wrong, that is not only a reputation issue. It is evidence that the owned page has failed to publish a safer category lock. If the directory’s place field is the only clear location signal, the first-party page is leaving the answer engine to choose its own geography.
The roughness is important. In one recurrent pattern similar to the Lyon example, the English partner profile gave a cleaner description but used an old service name. Perplexity borrowed the clear part and kept part of the old label. The result was half-useful and half-wrong. That is exactly the danger of letting third parties become your best source. They may win the footnote with a sentence that is easier to cite and less faithful to the work.
Moving the footnote back to your own domain
Winning the footnote back does not mean copying the directory. The directory is a skeleton. The owned page must add accuracy, proof, and entity control.
The first move is to map the cited fact. Take the Perplexity answer, write down the claim attached to the directory footnote, and ask whether the owned page states that claim in one compact place. If not, do not start with a new article. Start with the page that should already support the claim.
The second move is to add a factual source block. For a local business, this may sit near the top of a service page. For a specialised practice, it may belong on the main service page and again, in shorter form, on the About page. For a B2B provider, it should name deliverables in buyer language, not only internal methodology language.
The third move is to mark freshness without pretending that everything changes weekly. A stable business can still publish a current condition. “Updated for 2026 service scope.” “Current audit-preparation support for small food manufacturers.” “Service area reviewed in 2026.” These are modest marks. They tell the answer engine that the page is not a preserved brochure from another operating period.
The fourth move is entity boundary. Directory pages often mix legal names, trade names, categories, and platform labels. Your page should not. If the business has a legal name and a commercial name, state the relationship. If there are branches, state which page refers to which branch. If the firm is a compliance consultancy and not a general management consultancy, say so plainly.
The owned page should become a better source than the directory in three ways: more precise, more current, and more accountable. A directory can list. The business can define.
Directory citations are evidence, not defeat
I do not tell clients to ignore directories. That would be sentimental. Perplexity uses the public web it can read, and directories are part of that web. The point is to stop letting them be the cleanest public version of your business.
A directory footnote is most useful before anyone starts rewriting broadly. It identifies the source shape that won. If the directory won because of service scope, repair the service page. If it won because of location, repair the local or branch page. If it won because of an English summary, repair the French source sentence. If it won because the owned page is stale, add a current-condition mark.
The work is not glamorous. It is sentence surgery, with a filing-cabinet smell to it. Still, the result can change how Perplexity reads the entity. Once the first-party page carries the fact cleanly, the directory becomes less necessary as a citation crutch.
For the Lyon consultancy, the goal is not to make the site louder about expertise. The people already have that expertise. The goal is to make the exact service legible enough that Perplexity no longer needs an aggregator to explain the firm to a buyer.
The Numbered Source Note
Footnote candidate — “A Lyon compliance consultancy supports small food manufacturers with HACCP documentation, audit preparation and supplier-traceability files.” Citation rival — an English partner profile or aggregator listing with cleaner sector and service wording. Freshness mark — “Service scope reviewed for 2026 food-manufacturing compliance work.” Entity lock — commercial name, Lyon base, food-manufacturer audience, HACCP deliverables, and no generic management-consulting label.