GEO and Translation: Why AI Cites Your English Version and Ignores Your French Content

Why generative AI prefers English and ignores your translated content

AI answer engines (ChatGPT, Perplexity, Claude, Gemini) consistently cite your English content more than its French, Spanish, or German equivalents, even when the translated content is of identical quality. This asymmetry is not accidental: it results from three fundamental factors that structure the training and operation of language models. First, the massive training data used by these AIs is numerically dominated by English—between 40 and 60% of publicly accessible online corpora are in English, while French represents less than 3 to 5%. Second, AIs apply an implicit hierarchy of reliability: they identify and favor native sources, deemed more authoritative (an English article from an English-speaking company seems more relevant than a translation). Finally, the internal ranking mechanisms of AIs do not weight the user language the same way as Google Search, creating major visibility gaps between your original version and your localizations.

How AI processes hreflang signals and multilingual structures

Hreflang is an HTML tag that you insert into your pages to indicate to engines the linguistic and regional variants of the same content. Google Search has used it for years to consolidate versions of your site and avoid duplicate content. However, AI answer engines do not process hreflang the same way. ChatGPT and Claude do not systematically read these tags; instead, they evaluate the content itself, its domain authority, and its position in the global index. Perplexity, which seeks to cite the best sources, does consult your site's architecture, but applies a sorting by model language upstream: if the model has learned that English dominates a given sector, it will favor English sources even if a perfect hreflang exists.

This discordance creates a paradox: a well-thought-out multilingual structure (secondary domains like site.com/fr/, subdomains fr.site.com, or distinct domains) does not guarantee equitable visibility in AI responses. Regional subdomains (fr.site.com) seem slightly better treated than URL paths (/fr/) because they signal an independent entity, but the effect remains limited if the French content does not itself accumulate external authority comparable to English. Gemini, in particular, tends to consolidate sources by main domain rather than by linguistic variant, which means that if your site.com domain accumulates trust signals, your French pages benefit from a halo effect—but only if they are integrated into the same root domain structure.

Training biases: why Claude, ChatGPT, and Perplexity do not see French the same way

Each AI model is trained on different data and according to distinct objectives. ChatGPT, developed by OpenAI, was partially trained on Common Crawl, a massive archive of the web including all public domains; this archive reflects the real distribution of the web, roughly 60% English. When a user asks a question in French, ChatGPT mentally translates that question, searches for answers in its training corpus (where English dominates), then processes its response. This process creates a cognitive delay and a loss of contextual information. Claude, developed by Anthropic, is trained on a slightly more language-balanced corpus, but applies a stricter reliability filter: it favors academic and official sources, which are numerically overrepresented in English in technological and scientific fields.

Perplexity, a conversational search engine focused on citation, uses a different approach: it consults the current search index and ranks results according to a domain authority metric, then recites them. Although this seems neutral, Perplexity applies a language weighting at the level of the language model underlying it, de facto favoring native sources. Gemini (formerly Bard) from Google uses the Google index itself, but applies a complex multilingual normalization that remains partially opaque—Google Discover and voice search ranking signals (heavily dominated by English) influence its response, creating comparable visibility biases.

These technical differences mean that the same brand can receive a ChatGPT citation in English, be ignored by Claude in French, and be cited by Perplexity if it has accumulated SEO traffic in English. There is no single "multilingual AI"; there are parallel AIs with contradictory underlying rules.

Why your translated content receives fewer citations even when it answers the same query

Suppose you have written a complete guide in English: "How to Implement API Rate Limiting." You translated it into French: "Comment implémenter le rate limiting d'API." These two articles cover exactly the same topic, with the same depth and the same structure. Yet when a user asks ChatGPT in English "How to rate limit APIs," the English version is cited in 90% of cases. When the same user asks their question in French, the French version is cited in only 40% of cases—sometimes the English version is cited with a translation warning.

This asymmetry comes from three combined mechanisms. First, the dominant domain effect: your root domain accumulates backlinks, authority, and organic traffic density proportionally to the dominant language of your site. If 70% of your SEO traffic is in English, domain signals heavily weight your English pages in the mental models of AIs. Second, the reverse causality of citation: sources often cited on the public web (and therefore in the training corpus) accumulate more AI citations. English articles receive more links from blogs, technical forums, and external publications, simply because the English-language external content ecosystem is denser. AIs detect this density and reproduce it. Third, the first-language position effect: AIs have learned that primary content (the originally written version, not translated) is generally more reliable than a translation. Even if your French translation is native and not automated, the model does not know this and applies a mental discount.

How to check if your French content is under-cited in multilingual GEO

To diagnose a citation disparity between your language versions, start by asking the same query to ChatGPT, Claude, and Perplexity in each target language. For example, ask in English: "What is schema markup and why does it matter for SEO," then the same question in French: "Qu'est-ce que le schema markup et pourquoi est-ce important pour le SEO." Note whether your content is cited in both cases, and the volume of citations. Also identify the language of the cited source: if your French article is ignored in favor of an English source, that is a signal of asymmetry.

Next, consult your Google Search Console for each region and language. Performance data by country (in the "Performance" report, then filter by "Country") shows you organic SEO traffic by language. Compare impressions, clicks, and CTR for your English vs. French content. A disparity of 3:1 or higher suggests a structural problem. Finally, use AI monitoring tools like Semrush AI SEO Radar (if available) or conduct regular manual tests by asking your own questions to each AI engine, recording the sources cited across 20-30 queries per language. This "simulated user test" approach reveals biases that traditional tools do not capture.

Strategy 1: Strengthen the domain authority of your localized versions via backlinks and traffic signals

AIs observe the external authority of content via proxies: number of referring domains, detected organic traffic, page depth in the hierarchical structure. To increase citations of your French content, directly increase these signals. Start with internal linking: aggressively link to your French content from your French pillar pages, localized case studies, and regional homepages. Each additional internal link creates a relevance signal for AI engines, which analyze your site structure.

Second, invest in French-only backlinks. Contact blogs, publications, and forums in your sector that operate exclusively or primarily in French (Actualité Hosting, Journal du Net, French tech blogs, French-language academic publications). Offer guest posts, exclusive data citations, or content partnerships. These backlinks signal to AIs that your French content is referenced and approved by native sources. Cross-lingual backlinks (English pointing to French) have lower value for multilingual AI GEO.

Third, amplify direct organic traffic to your French content via a localized SEO strategy. Optimize for French keywords with real search volume (not just the direct translation of English keywords). For example, the French query "API rate limiting" may have little volume (French speakers rarely search in English), but "limiter les requêtes API" or "throttling API" may have a larger volume. Capture these long-tail queries and accumulate organic traffic. AIs observe this traffic (via indirect signals like Google SEO positioning, which all models consult) and weight your French content more highly.

Strategy 2: Localize, don't just translate—create unique value in French

Word-for-word translation creates content that looks like a duplicate in the eyes of AIs. To improve citation, create truly localized content with unique elements not present in the English. If your English guide is about "Best Practices for Cloud Infrastructure," your French version can include French case studies (French clients, specific GDPR regulations, French-speaking cloud infrastructures like OVH or Scaleway). These additions transform the French page from a "translation" into an "authorized local variant" in the eyes of AIs.

Next, adapt data, statistics, and references to your target market. If you cite a study on cloud performance, include data specific to France or French-speaking Europe if it exists. This creates a page whose content profile differs from the English, reducing the duplication signal and strengthening local relevance. AIs detect these differences and treat the French version as an independent and valid source.

Also develop content exclusively in French that you do not publish in English. For example, if you observe a frequent French-language query not covered on your English site ("Comment monétiser mon contenu en tant que créateur français"), write an article exclusively in French answering it. This effort signals that you understand your French-speaking market and creates a reverse asymmetry—later, if you translate this article into English, AIs sometimes cite the French original as the source of innovation, reversing the usual hierarchy.

Strategy 3: Optimize multilingual architecture and metadata for AI readability

Your multilingual architecture (URL path, domain, or subdomain) influences how AIs segment and weight your content. The three common models offer different results with AIs:

Distinct regional domains (site-fr.com, site-de.com, site-es.com): This approach is clearly ideal for AIs. Each domain is treated as an independent source, accumulating its own authority. However, it dilutes your root domain authority. Backlinks and traffic fragment. Use this approach if you have the resources to manage multiple domains and if regionalization is strong (France vs. Canada vs. Belgium).

Regional subdomains (fr.site.com, de.site.com): This approach offers a balance. AIs recognize the subdomain as a distinct "branch" of the root domain, allowing it to accumulate partially independent authority while inheriting root authority. Backlinks to fr.site.com strengthen fr.site.com; backlinks to site.com strengthen the whole. For AIs, this is more effective than URL paths but less isolated than distinct domains.

Regional URL paths (site.com/fr/, site.com/de/): This is the most common structure. Unfortunately, for AIs, it is also the least effective. URL paths do not create a clear demarcation for language models, which see fr/ as a simple directory of the main domain. All authority accumulates at the root domain, and AIs weight your French vs. English content according to the global domain's traffic/backlink ratio, not by language.

If you use URL paths (site.com/fr/), compensate by structuring robust metadata tags. Add a <meta name="og:locale" content="fr_FR" /> tag to each French page, a clear language tag in the DOCTYPE (<html lang="fr">), and an explicit hreflang pointing to the linguistic variants. Also include a JSON-LD language schema block: {"@context": "https://schema.org", "@type": "WebPage", "inLanguage": "fr"}. These signals help AIs identify and segment your content by language, even within a URL path structure.

Strategy 4: Implement specific linguistic authority signals

After being trained on corpora where English dominates, models apply an implicit bias: English sources are presumed more authoritative. To counteract this, create explicit signals of French linguistic authority. First, develop certifications or recognitions within your French-speaking ecosystem: if you can be cited by prestigious French-language publications (Challenges, Le Monde, Figaro Tech, academic journals), these citations strengthen local authority. AIs observe who talks about you and give increased weight to high-profile sources.

Second, publish "thought leadership" content in French in formats that attract AIs: long, well-structured articles (2000-4000 words), original data (surveys, benchmarks), and local news analysis. AIs seek content that nowhere else offers; if you publish an exclusive survey on "Cloud adoption among French SMEs," this content becomes a unique source in French, difficult to ignore.

Third, actively participate in French-speaking discussion ecosystems: French-language Reddit forums (r/france, r/webdev in French), LinkedIn groups targeting French speakers, comments on French-language articles, etc. These participations do not create backlinks, but they create monolingual brand mentions, and AIs observe mention patterns to measure local authority.

Strategy 5: Test and monitor AI citations by language, over the long term

The impact of multilingual strategies on AI visibility is not immediate. AIs retrain their models every 3 to 12 months depending on the engine (ChatGPT more often, Claude less often, Perplexity continuously via its live index). You must therefore establish a continuous monitoring process. Each month, ask a set of 10-20 key questions to ChatGPT, Claude, and Perplexity, alternating English and French, and record:

• Is your domain/page cited?
• If so, is it the English version, French version, or both?
• What is the citation context (direct excerpt, paraphrased summary, link only)?
• What is the position of your citation (first, second source, etc.)?

Keep this data in a spreadsheet to detect monthly trends. You will likely see a gradual improvement in French citations if you implement the above strategies. Effective diagnosis will also allow you to pivot quickly if an approach does not deliver the expected results.

Also note that AI behavior can diverge from one user to another, depending on geolocation, conversation history, and model settings. Test from French geographic locations (via VPN if necessary) to observe behavior specific to French-speaking users, who may receive slightly different responses from English-speaking users testing from the United States.

How AI processes regional vs. universalist content

One last underestimated issue: AIs distinguish between universalist and regional content. An English article on "How to SEO" is perceived as universal—applicable everywhere. A French article on "Comment faire du SEO" is sometimes implicitly perceived as regional—relevant mainly for France. This creates a hierarchy: AIs consider universal content (English) as more useful for the global user, even if the user is French-speaking.

To combat this, write your French content in a universalist way: avoid excessive references to France, Belgium, or Quebec except when regionalization is relevant. A guide "Comment implémenter le rate limiting API" in French should be readable by a Quebecois, Swiss, or African developer, not just French. Use clear language, without strong regional expressions. This repositions your French content as universal rather than regional in the eyes of AIs, increasing its probability of citation in response to broadly French-speaking questions.

Simultaneously, create frankly regional content with a good markup strategy: "Guide du SEO en France 2024" or "Meilleures pratiques cloud pour les startups québécoises." AIs detect these explicitly regional titles and reserve them for the appropriate localized users. Together, these two strategies—universal and regional—ensure a balanced presence in AI responses across a spectrum ranging from the worldwide French-speaking user to the deeply localized user.