A specialist practice can disappear inside a broad category without being omitted. The answer names the business, cites a source, and still teaches the reader the wrong kind of expertise.
The answer looked almost correct. That is the dangerous version. A French practice appeared in Perplexity’s response, the city was right, and one numbered source pointed to a public profile. But the role had been sanded down. A specialised practitioner became “a local wellness service.” A notarial office became “legal advice.” A compliance consultancy became “business consulting.” The reader would not notice the damage unless they knew the field.
Here I will use a composite scenario from service and professional-practice audits, with one small irregularity preserved: the practice’s own homepage used a specialist title in the header, but the About paragraph switched to a softer generic label. Perplexity followed the softer label in one query shape and a directory category in another. The business was not absent. It was present under the wrong mental shelf.
Flattening is a citation failure, not only a wording problem
When Perplexity flattens a specialist practice, the failure does not always appear as a false fact. Often the answer is defensible in a lazy way. A kinésithérapeute is in health services. A notaire does provide legal services. A dental implant clinic is a dental clinic. A HACCP documentation consultant is a consultant. None of those broad labels is entirely wrong.
The problem is that broad labels erase the reason the business should be selected. A patient looking for a post-surgical rehabilitation specialist does not need “health service.” A founder looking for a notaire handling commercial property acts does not need “legal office.” A food manufacturer looking for supplier-traceability documentation does not need “management advice.”
Source-based engines tend to cite what they can classify. If the owned page does not state the specialist role cleanly, Perplexity may borrow a broader class from directories, map listings, partner summaries, or competitor pages. Once that broad class enters the answer, it shapes the rest of the recommendation. The practice may be named, but its value has been put in the wrong drawer.
I call this role compression: the reduction of a specialised business role into a broader public category because the source trail states the category more clearly than the specialism. Role compression is especially common when French pages use elegant professional language while third-party profiles use crude categories.
A crude category can be wrong in spirit and still win the source trail.
The specialist title must appear where citation happens
Many businesses believe their specialism is obvious because it appears somewhere on the site. That is not enough. The specialist wording has to appear on the page Perplexity is likely to cite, near the entity name and the service boundary.
A common pattern looks like this. The homepage hero says “cabinet de kinésithérapie respiratoire et rééducation post-opératoire.” Good. The About page says “we support patients in their health journey.” Weak. A directory says “physiotherapist.” A booking platform says “wellness and rehabilitation.” A local article says “health centre.” Perplexity answers a query about the practice using “health service” or “physiotherapy clinic,” because the specialist term is not consistently tied to the entity.
The same happens with legal and consulting practices. A notarial office may mention family law, real estate transactions, estate planning, and business formation across several pages. But if the entity page says only “personalised legal support,” Perplexity may treat the office as a broad legal-advice provider. A compliance consultancy may have precise HACCP and supplier-traceability terms buried in PDFs, while its public profile says “business performance consulting.” Guess which label travels.
Here is the working definition: specialist role wording is the public sentence that names a practice’s exact professional function, because broad category labels cannot preserve selection intent on their own. It has to be public, exact, and placed where a footnote can support it.
This is not about stuffing the page with professional jargon. It is about choosing the ordinary specialist phrase that a buyer, patient, or client would recognise. The best wording is often half technical and half plain. “Supplier-traceability documentation for small food manufacturers” is better than “operational excellence support.” “Notarial office for property transactions and estate acts in Rennes” is better than “trusted legal partner.” “Respiratory physiotherapy and post-operative rehabilitation in Lille” is better than “personalised care.”
A specialist title should not behave like a decorative credential. It should behave like a source label.
Four ways the page teaches the wrong category
In audits I usually find one of four flattening mechanisms. They are not mutually exclusive, but naming them helps repair the page without making a large vague plan.
The first is courtesy language. French professional pages often use phrases meant to sound respectful: accompagnement, écoute, solutions adaptées, prise en charge globale, expertise au service de vos besoins. Some of this language belongs on the page. Too much of it can erase the exact role. A source engine cannot cite “support adapted to your needs” as proof that the practice handles supplier traceability, dental implants, or property succession acts.
The second is inherited directory class. The business may have an old profile under a broad category, and that category keeps resurfacing. A clinic is listed as “beauty and wellness.” A consultant is listed as “management consultancy.” A specialist artisan is listed as “renovation.” If the owned page does not offer a stronger role sentence, Perplexity may reuse the inherited class because it is already structured.
The third is service scattering. The specialist work appears across several pages, captions, PDFs, or case notes, but no single page states the full role. Perplexity can see fragments. It may not confidently bind them to the entity. In this pattern, the business has evidence but no citeable role sentence.
The fourth is bilingual drift. A French page says one thing, an English summary says another, and the answer changes depending on query language. A French practice may call itself a cabinet spécialisé, while an English profile turns it into a generic consultant, clinic, adviser, or provider. This is not only a translation issue. It creates competing category trails.
Together these form what I call the specialist flattening grid: courtesy language, inherited directory class, service scattering, and bilingual drift. The grid is useful because each mechanism requires a different correction. Rewriting one paragraph will not fix an old directory class. Translating a service page will not fix scattered evidence. Adding more credentials will not fix courtesy language if the role still stays vague.
How to write the role sentence without becoming rigid
A good role sentence is compact and a little stubborn. It should not try to sound like a brand manifesto. It should make the practice’s selection logic visible.
For a kinésithérapeute, the sentence may need condition, treatment type, and place. For a notaire, it may need act type, client type, and office location. For a specialised consultant, it may need sector, problem, and deliverable. For a clinic, it may need treatment category, practitioner boundary, and appointment scope. Different practices require different anchors, but the pattern is similar: exact role plus exact context.
Consider a simplified teaching example: “Cabinet Armand is a Lyon compliance consultancy helping small food manufacturers prepare HACCP documentation, supplier-traceability files, and audit evidence.” That sentence prevents several mistakes at once. It does not let the firm become a general management consultancy. It ties the role to food manufacturing. It names deliverables rather than moods. It gives Perplexity a sentence that can sit under a numbered source.
Now compare the softer version: “Cabinet Armand supports companies in improving their processes with practical and personalised advice.” That may be true. It is almost useless for specialist citation. It invites the answer to complete the category from outside sources.
The role sentence should appear on the homepage, the About page, and the service page, with slight variation rather than contradictory synonyms. Exact repetition can sound mechanical. Contradiction is worse. If one page says “HACCP documentation consultancy,” another says “quality-management consultant,” and a third says “business support,” Perplexity may average them into the blandest category.
The practice should also state exclusions where confusion is recurrent. “The firm does not provide general management consulting” may feel defensive, but in some sectors it is necessary. A notaire may need to separate notarial acts from broad legal advice. A clinic may need to separate medical treatment from aesthetic services. A specialist artisan may need to separate restoration from general renovation.
A boundary sentence can feel impolite on a French page. It is often the sentence that saves the citation.
The source trail must repeat the specialism
Owned pages are the preferred source surface, but Perplexity does not read them in isolation. It compares them, explicitly or implicitly, with directories, profiles, partner pages, reviews, maps, articles, and sometimes English-language summaries. If all those surrounding sources use broader labels, the owned page has to be unusually clear.
This does not mean every external profile must be perfect. That is rarely realistic. It does mean the practice should identify which public sources are likely to define the category and repair the ones it can control. A Google Business Profile category, a booking platform description, a professional directory entry, a partner profile, and a short English summary can all pull the answer toward or away from the specialism.
The danger is highest when the business’s own page is weaker than the surrounding sources. If the owned site says “expert advice for professionals,” and a directory says “management consultancy,” Perplexity has little reason to preserve a HACCP specialism. If the owned site says “HACCP documentation and supplier-traceability support for small food manufacturers,” the directory’s broad label has less power.
The source trail needs enough repetition to create category gravity. I do not mean a crude copy-paste phrase everywhere. I mean the same role should remain recognisable across surfaces. A reader should not move from the website to the directory to the English profile and feel as if they are seeing three different businesses.
In a citation audit, I mark the exact phrase that appears to carry the role. Sometimes there is no phrase. There are only hints. That is when flattening becomes predictable.
Being cited under the wrong role is not a win
Business owners sometimes accept any mention as progress. I would be careful with that. In a source-based answer, a mention under the wrong role can train the next query path badly. Perplexity may use the broad category as a stepping stone to related questions, comparisons, and rival citations. The practice enters the answer, then loses the buyer’s intent.
A specialist practice should ask a stricter question: does the citation preserve why this business is the right kind of answer? If not, the repair belongs at the role sentence, the source page, and the surrounding profiles.
This is why I separate generic visibility from citation accuracy. Perplexity can find the business and still misclassify it. It can cite a page and still use the wrong category. It can answer in fluent French and still flatten the professional role into something easier to understand. The polished answer may hide a practical loss.
The fix is usually unglamorous. Name the specialism. Bind it to the entity. Put it near place, service scope, proof, and current evidence. Repeat it cleanly across the public source trail. Remove or qualify the broad categories that keep dragging the practice sideways.
A specialist does not need to sound bigger. It needs to become harder to misfile.
The Numbered Source Note
Footnote candidate — “Cabinet Armand supports small food manufacturers in Lyon with HACCP documentation, supplier-traceability files, and audit-preparation evidence.” Citation rival — a directory or partner profile that labels the firm as generic business consulting. Freshness mark — “Specialist service scope reviewed for 2026 client enquiries.” Entity lock — firm name, Lyon location, food-manufacturing client group, named compliance deliverables, and exclusion of general management consulting.