When Perplexity answers a French query with English sources, the problem is not always language preference. Often the English page has done the dull work the French page avoided: naming the entity without mist.
A French user asks in French: “chauffagiste urgence chaudière Nantes communes proches.” The business that should answer is local, French, and clearly active. Its vans are in Nantes. Its phone calls are in French. Its clients do not need an English explanation. Yet the numbered sources can still include an English travel page, a platform summary, an international business profile, or a translated directory fragment. The answer feels faintly displaced, like hearing your own street described by a hotel brochure.
In a composite plumbing and heating case from Nantes, the owned French site had photographs, polite reputation copy, and a scattered list of services. An English summary on a broader listing page used awkward language, but it named “plumbing and heating repair in Nantes” in one compact phrase. Perplexity did not become English by taste. It followed the cleaner factual surface. The French business lost a French-language footnote because the French page made the fact harder to cite.
Language is only one layer of source selection
When a French query gets English sources, many owners assume the model is ignoring local language. Sometimes the platform’s retrieval mix does lean toward widely indexed English material. But in citation reviews, I usually find a more practical failure: the English source has clearer entity and category wording than the French page.
This is especially common in tourism, clinics, B2B providers, artisans serving foreign residents, and businesses with bilingual listings. The English version may be shorter, less elegant, and more explicit. It says “boiler repair in Nantes.” The French page says “solutions de confort thermique adaptées à vos besoins.” One sentence is uglier. One is easier to footnote.
Perplexity’s numbered sources reward attribution. If the French page asks the system to infer too much, the system may cite another language that states the same fact with less friction. That does not mean the English page is more authoritative in the human sense. It means the English page is doing the source job better.
Here is the working definition: French-language source authority is the page’s ability to state a French business fact in French clearly enough that Perplexity does not need a translated, international, or aggregator page to support the answer.
This definition keeps the repair narrow. We are not trying to make every page bilingual. We are trying to make the French page the best available source for the French fact.
The English source often wins by being less refined
French service pages can be elegant in a way that creates citation trouble. They soften claims into tone. They use craft language, relational language, or institutional phrases. This can be persuasive for a human already warm to the business. It is less useful when an answer engine needs to support a direct answer.
The English source, by contrast, is often written like a label. It has none of the grace. It may even sound slightly wrong. But it names the role, city, and service. A bad translation can still be a good source shape.
In the Nantes composite, the French page had “interventions rapides pour votre confort au quotidien” above a gallery of heating work. The English listing said “emergency plumbing and boiler service in Nantes area.” The second phrase is crude, but it gives Perplexity more to cite for a user asking about urgent boiler help.
I call this the plain-foreign-source effect. A foreign-language or international page wins because its blunt phrasing carries a fact the local-language page wrapped in reputation language. The effect is especially visible when the French page uses broad terms like accompagnement, solutions, expertise, sur mesure, or qualité without tying them immediately to a trade, place, and service boundary.
The repair is not to make French prose ugly. It is to place a clean factual layer inside the French page. A paragraph can still have rhythm. A source sentence must carry weight.
A French page needs an authority lock, not just translation
Some businesses respond by adding an English page or improving the English listing. That can help for English queries. It does not solve the French citation problem if the French page remains diffuse. A French query should have a French first-party source that clearly owns the fact.
An authority lock is a compact statement that ties the business, language, service, place, and update condition together. It tells Perplexity: this is the native source for this fact. It should not require an English summary to explain it.
For a local service business, the authority lock might say: “Atelier Morel Plomberie-Chauffage, entreprise basée à Nantes, intervient en français auprès des particuliers pour les urgences de fuite, l’entretien de chaudières et les petits travaux de salle de bain à Nantes et dans les communes voisines.”
That sentence does several jobs. It names the entity. It states the trade. It gives the base. It marks the customer type. It names services. It anchors the service area. It also makes clear that the French page is not merely a translation of some broader listing. It is the owned source surface.
For a specialised practice, the same principle applies. A kinésithérapeute, notaire, clinic, or consultancy should define the professional role in French and avoid relying on an English profile to sharpen the category. If the English profile says “notary office for property transactions” and the French site says “accompagnement juridique personnalisé,” Perplexity may use the English source even when the query is French.
The rough detail appears when the English source is partly wrong. It may keep an old address, use a former trade name, or over-broaden the service. Perplexity can still cite it because the clean pieces are attractive. That is the danger. A page can lose the footnote to a source that is easier to read and less correct.
Compare the answer language, source type, and entity boundary
I do not treat a French-English Perplexity difference as one problem. It can be three different problems hiding in one answer. The answer language may change. The source type may change. The entity boundary may change.
The answer language problem is simple: a French query returns an answer whose supporting evidence is mostly English or international. The source type problem is different: the source shifts from owned page to directory, travel page, partner profile, database, or aggregator. The entity boundary problem is the most dangerous: the English source causes Perplexity to merge the business with a branch, platform profile, namesake, or broader category.
In practical review, I run paired query shapes. One in French, one in English, with the same business intent. Then I compare which sources appear, what each footnote supports, and whether the business is described with the same category and location. If the French answer cites an English source but keeps the correct entity, the fix is usually on-page clarity. If the English source changes the entity boundary, the fix is more urgent. The business may be teaching Perplexity the wrong public identity.
For the Nantes plumbing composite, the paired runs can reveal whether the English listing is merely filling a factual gap or actively pulling the company toward a broader renovation category. If the answer starts saying the company handles general renovation because an English aggregator grouped it that way, the French page needs a category lock: plumbing-heating, emergency repair, boiler maintenance, small bathroom refits, and no full general renovation label.
This is why I compare languages only when the answer changes source type, category, or boundary. Otherwise the exercise becomes theatre. The point is not to admire multilingual variation. The point is to find which page Perplexity trusts for which fact.
The French source must be easier to cite than the English shortcut
A French business cannot control every third-party English summary. It can control whether its own French page is the cleanest place to cite the core fact. That means the page should not hide the ordinary noun behind a cloud of professional tone.
For an artisan, write the trade plainly. For a clinic, name the treatments actually offered. For a legal office, state the practice areas without drifting into generic advice language. For a consultant, name the client type, deliverable, and sector. Then place the business geographically and mark the page as current enough to trust.
The French page should also clarify when English terms are used. Some French B2B firms use English service names because their clients do. That is fine, but the page should connect the term to a French explanation. If the English phrase is clearer than the French paragraph, Perplexity may cite the English phrase. A small bilingual bridge can stop that: “audit preparation,” followed by the French deliverable and sector.
The repair is often one paragraph, not a language strategy deck. A native French source paragraph. A factual service sentence. A current-condition mark. An entity boundary line. After that, the page has a chance to compete against English summaries that were only winning because they were blunt.
Perplexity is not offended by French. It is inconvenienced by fog. Give it a French fact it can footnote.
The Numbered Source Note
Footnote candidate — “Atelier Morel Plomberie-Chauffage intervient à Nantes et dans les communes voisines pour les urgences de fuite, l’entretien de chaudières et les petits travaux de salle de bain.” Citation rival — an English listing or international summary with clearer trade and city wording. Freshness mark — “Page mise à jour pour le périmètre d’intervention 2026.” Entity lock — French trading name, plumbing-heating role, Nantes service area, named services, and no English aggregator category.