SEO

49 AI Search Localization Statistics

49 figures on whether AI engines cite local-language pages or English ones, per engine and per market, each traced to its origin.

Author:
Wihan van Zyl
Contributors
Vlad Shvets
Date:
October 1, 2026

Ask an AI engine a category question in Spanish, from Spain, and 26.4% of the pages behind its answer are Spanish-language. Ask the identical question in English, from the same country, and that share falls to 1.7%.2 The pages on the web did not change between those runs. The question did.

Most localization budgets assume the opposite, that a strong English site competes everywhere and translation is a concession to the markets that complain loudest. The year of measurement that now exists says the English estate is mostly not in those answers at all.

Highlights

85.4% of citations behind a non-English prompt are in the prompt’s language on Google AI Overviews, against 51.7% on Grok, across six languages.1
43% of research steps run on the English-speaking web when somebody asks ChatGPT a question in another language.6
80% of stable sources in Google AI Mode are German for German queries, while 68% of ChatGPT’s are English.5
71.8% of citations in French-language B2B software questions go to vendor pages, and 1.6% to third-party sources of any kind.8
24% to 42% of Reddit citations in non-English markets point at Reddit’s own machine translations, against under 1% in English-language markets.7
61% in Japan against 6% in the United States, the local-source share on identical B2B software prompts across twelve markets.4
A 41.4-point spread separates the highest and lowest of 47 categories, wider than the spread between engines.1

Read together they describe a system nobody is selling you. The engines do read the buyer’s language, most of them heavily. But they disagree about how much, they reach that language by opposite routes, and in B2B software the pages they land on are mostly ones you already own. The decision in front of you is not whether to translate. It is which pages, in which markets, for which engine.

Asking In Another Language Returns Another Web

The cleanest evidence here comes from the dullest experiment. Ask the same question twice, change only the language, and hold the market constant.

Weglot ran 400 questions across five topic categories and three lengths, each written in English and in the local language, through four systems in five countries, for more than 16,000 answers.

Dumbbell chart of the share of cited sources written in the market’s own language, asked in English against asked in the local language: Japan 1.3% to 34.8%, France 2% to 30.2%, Spain 1.7% to 26.4%, Argentina 1.1% to 22.6%.
Each market measured twice with the same 400 questions. The left point is the English-language run and the right point the local-language run. Source language detection is not described by the study.
34.8% of sources in Japan were Japanese-language, against 1.3% when the same questions were asked in English.2
30.2% in France were French-language, against 2%.2
26.4% in Spain and 22.6% in Argentina, against 1.7% and 1.1%.2

Four markets, four languages, one direction, and the smallest of those multiples is roughly eleven-fold. Senuto’s analysis of 17.8 million Polish keywords puts the ceiling higher, with 96.03% of citations in Polish AI Overviews coming from local Polish sources, though it never says how it decided a source was foreign.12

The English pages in those runs were not ranking badly. They were close to absent, which is a different problem with a different fix, and it is why this decision cannot be made from traffic data.

What changes with the language is not only which pages get cited but which products get named. A preprint published in August 2026 ran the same accounting-software question from the same connections in two languages, six identical runs per cell.

6 of 6 runs from a Berlin connection asking in German named Lexware, sevdesk and Papierkram, with no global vendor appearing at all.13
3 of 6 for those same three when the question was asked in English from that connection, while FreshBooks, Wave and QuickBooks appeared in five or six.13
1 of 24 runs produced a global vendor across the four cells where the question was asked in the exit country’s own language.13

The study is small and its author says so. It also carries the limit that matters most: in its control category, project management software, no domestic vendor appeared in any cell in any language.13

So the effect needs a category where credible local vendors already exist. In a category owned by global products, asking in the buyer’s language will not conjure a local shortlist out of nothing.

Which Engine Answers Decides How Much Of Your Language It Reads

There is no single behavior here to plan against. Temso matched every cited URL to its detected page language across more than four million source-to-prompt language pairs on non-English prompts, in six languages.

Diverging bar chart of citation language by engine on non-English prompts: Google AI Overview 85.4% local language against 8.7% English, Microsoft Copilot 76.7% against 15.4%, ChatGPT 70.2% against 23.7%, Grok 51.7% against 39.6%.
Six non-English prompt languages pooled. The remainder of each engine’s citations was in a third language. The study does not name the tool it used to detect a page’s language.
85.4% of citations matched the prompt’s language on Google AI Overviews, with 8.7% English.1
76.7% on Copilot, then 70.2% on ChatGPT, then 51.7% on Grok.1
53.5% against 38.3%, English sources outnumbering Dutch ones on Grok for Dutch prompts.1

Temso does not name the tool it used to detect a page’s language, which is the one step all of it rests on, so read that as an ordering rather than four precise rates. The ordering holds in two other studies that measured different things.

80% of stable domains in Google AI Mode are German-language for German queries, against 68% of ChatGPT’s being English.5
ChatGPT and Perplexity lean most to the prompt’s language, Gemini sits near balanced, and for Claude English dominates with non-English a very small share.14

That second one is a University of Toronto preprint, and it prints no percentage for any engine, so it is a direction and not a number. It was collected in August 2025 on model versions since replaced.

Claude is still the one to flag to anyone whose buyers use it, because it is the only engine measured where translating a page may not change what gets cited at all.

The engines also differ in how much room they have. ChatGPT cites a median of 3 to 4 domains per answer against Google AI Mode’s 14 to 16, and for the same prompt the two Google surfaces share only 17% of cited domains.5

Wihan van Zyl
GTM Consultant @ Empact Partners
The thirty-four point spread between the most and least local-language engine is the number to argue with, not the 85.4%. It says one localization decision cannot be right for every surface a buyer might open, because Google is reading the market’s own web while Grok is largely reading English about that market. What it does not say is which engine your buyers use, and that is market-specific and measurable. Start there, because getting the engine wrong wastes the whole budget rather than part of it.

Measuring per engine rather than once per brand is the first thing we do in Generative Engine Optimization, the work of becoming the brand an engine names when a buyer asks their category question, because a baseline averaged across engines hides the one market where a partner is absent.

ChatGPT Re-Asks Your Question In English

The spread has a mechanism, and it is observable rather than inferred. Peec AI analyzed over 10 million prompts and 20 million query fan-outs and found that ChatGPT does not simply read pages in the language it was asked in.

43% of research steps ran on the English-speaking web when the prompt was not in English.6
Nearly 78% of sessions in another language contained at least one English sub-query.6
94% for Turkish at the high end and 66% for Spanish at the low, with no language tested falling below 60%.6

The pattern Peec describes is a first fan-out in the user’s language and later ones in English. An English page can therefore enter a German answer without anything being translated, and without the engine ever leaving German on the surface.

Statcard of the share of ChatGPT’s background research steps that ran on the English-speaking web when the prompt was in another language: 43%.
Measured across more than 20 million query fan-outs from over 10 million prompts. The window is given only as recent months.

Google reaches the same local-language surface by the opposite route. Reddit machine-translates its own threads and publishes them at distinct URLs, and Peec found those translations cited heavily outside English-speaking markets.

24% to 42% of Reddit citations in eight non-English markets pointed at a translation, against under 1% in the four English-language markets.7
71.6% against 10.1%, the translated share for Google AI Overviews and for ChatGPT in Sweden.7

One engine manufactures a local-language source out of an English thread. The other reads English directly and answers in German anyway. Only the first can be influenced by publishing in that language, and neither is what a translation vendor means by local-language visibility.

None of it is stable enough to treat as settled. ChatGPT’s translated-Reddit share fell from 6.14% to 0.66% between April and May 2026, and Peec says plainly it cannot tell whether that sits in the model, the grounding layer or the index.7

Line chart of ChatGPT’s translated share of its own Reddit citations by month: 3.93% in March 2026, rising to 6.14% in April, then falling to 0.66% in May.
Translated pages identified by Reddit’s own translation parameter in the cited URL. The incomplete June period is left off. The publisher does not say whether the change sits in the model, the grounding layer or the index.

The consequence shows up when somebody translates a site. Weglot compared Spanish and Mexican sites with and without a second language version, across 1.3 million citations.

327% more visibility in AI Overviews on queries in a language the site had not previously served.3
0.3% to 1.8% more citations on ChatGPT, for the same sites and the same comparison.3

Weglot sells translation and is measuring translation, so hold the magnitude loosely. The shape is what matters: the same spend buys a great deal on one surface and close to nothing on another.

The Local Share Is A Variable, Not A Number

Every figure above is an average of markets and categories you may not sell in. The only study to run identical commercial B2B software prompts across many markets found the local share moving across almost the whole available range.

MaxAEO ran 200 commercial-intent B2B software prompts per market in each market’s own language, across seven engines and twelve markets, logging 1.06 million citation links.

Horizontal bar chart of the local-source share of non-vendor citations on B2B software prompts across twelve markets: Japan 61%, South Korea 58%, Brazil 44%, Poland 41%, Italy 37%, Spain 35%, France 33%, Germany 29%, Netherlands 19%, Sweden 17%, United Kingdom 12%, United States 6%.
Identical commercial-intent prompts asked in each market’s own language across seven engines. The denominator is non-vendor citations, which excludes the vendor pages that dominate B2B answers.
61% in Japan and 58% in South Korea at the top.4
41% in Poland, 37% in Italy, 35% in Spain, 33% in France, 29% in Germany.4
17% in Sweden, 12% in the United Kingdom, 6% in the United States.4

Those twelve figures are shares of non-vendor citations, which excludes the vendor pages that dominate B2B answers, so each one is narrower than it first reads.

Category moves it at least as much as market does. SE Ranking’s 100,000-keyword run in France found 89.34% of sources in French overall, but 57.38% for business queries against roughly 97% in regulated verticals.10 Across Temso’s 47 categories the gap between highest and lowest is 41.4 percentage points, wider than the gap between its most and least local-language engine.1

The one category in that data a software buyer can read directly is the uncomfortable one. In data analytics software, engines cited English pages 48.8% against 47.3% in the prompt’s own language.1

Wihan van Zyl
GTM Consultant @ Empact Partners
A category splitting almost evenly between the two languages should stop a translation plan built from the headline. The pooled 85.4% is carrying consumer and local-services categories where the local web is dense, and B2B software is one of the places where it is not. Nobody has published your category in your markets, so the number you budget against has to be measured rather than borrowed. Watch the share of answers in each locale that name you at all, per engine, before anything is translated.

In B2B Software The Answer Runs On Pages You Own

Here the advice inverts. The assumption behind most local-language programs is that the lever is third-party coverage in the market, because that is the lever in English-language software categories. In the two tests that exist in non-English languages, it is not.

Evocia asked 200 B2B software purchase questions in French, four times each with no history, logging 2,259 citations across 288 domains.

71.8% of citations went to vendor-published pages and 17% to vendor documentation.8
8.5% went to institutions and regulators.8
1.6% went to third-party sources of any kind, and comparison sites took none at all.8

Radyant and OMR Reviews ran 96 German-language commercial-intent software prompts across five engines over 20,160 chats and found vendor and manufacturer sites taking 63% of citations.9 Two languages, two prompt sets, two vendors, the same answer.

SISTRIX is the only source anywhere that crosses page type with language, and it does so without a single percentage: product and shop pages dominate the core Google AI Mode keeps, while documentation and institutional sources form ChatGPT’s, with editorial guides rotating through the periphery of both.5

The page-type half we can measure ourselves. Qvery is our sister company, and it has tracked millions of ChatGPT and Google AI Mode citations since January 2026, so discount what follows accordingly and check each figure at its source below. Its content-type classifier, which names roughly an eighth of citations, puts listicles at 5.33% and news at 0.11%.26

A translated marketing site sitting in front of untranslated documentation is the wrong way round for the engine most of your buyers are using.

Where the third-party layer does matter, it is a different set of sites per market rather than less of the same ones. SE Ranking ran one method in Germany and the United States on the same day and found review platforms in 31.9% of German AI Overviews against 34.5% of American ones, while G2’s share of those citations fell from 23.1% to 9.3% and German platforms took the places the American ones held.11

Getting named on the right third-party pages in a market is the mentions half of what we run as Generative Engine Optimization, the formula being what real users say about you in public plus where independent sources name you.

In a thin non-English market the honest sequence is your own estate first and the local third-party layer second, which is the reverse of the order that works in English.

The Engine Is Reaching For Density

All of this has one explanation, and it is not that engines prefer English or prefer the local language. They reach for whichever body of pages covers the question best, and language is how the field gets narrowed first.

The supply side sets the ceiling. On W3Techs’ sample, 93.6% of .de websites are German-language and 5.9% are English, while 67.1% of .com websites are English.18 A company whose whole estate sits on a .com is not in the local-language pool its buyers’ questions are answered from, whatever its domain authority says.

Thin supply has been measured for years, in cleaner settings than commercial search.

22% of questions across seven non-English languages become answerable only by searching English Wikipedia.16
59.8%, 56.3% and 71.5%, the share of German-locale queries that native-language results, English results, and both together answered sufficiently.15
2.49 to 2.80 sources per query for local-language questions against 3.37 to 3.50 for English, in every market tested.2

Neither language alone is enough, which is the finding that most resembles an instruction. Asking in your own language also buys fewer chances at the same time as it narrows the field, which is the squeeze a thin local estate sits inside.

Only one engine maker documents any of this. Microsoft defines the retrieval selector for Bing-grounded answers as a market, and defines a market as a language-and-country pair.17 Its market-codes reference lists most countries with a single language.28 For those surfaces, serving a market and serving a language are the same instruction. OpenAI, Anthropic and Google document no retrieval-language parameter at all.

Our own side of this points the other way, and it is worth saying so rather than leaving it out. Qvery published two platform studies with no stated method at all.

95% of TripAdvisor citations land on its English-language hosts and under 1% on its non-English ones, holding even for queries from non-English-speaking countries.24
1.19% of all citations are TripAdvisor’s in that dataset, so this describes one platform rather than a market.24
97% ChatGPT for Wikipedia, 100% Google AI Mode for Quora, 91% Google AI for YouTube.24

Qvery’s own explanation is density: the English edition carries more reviews per entity and is what the engines have processed most.24 It reports the same pattern on Quora without attaching any figure to it.25

That reconciles with everything above rather than contradicting it. Inside a global platform the English edition is the dense one, so that is where an engine lands. Across a whole market, the dense body of pages in the buyer’s language is usually a set of local domains instead.

Wihan van Zyl
GTM Consultant @ Empact Partners
Put our own platform findings next to the market-level ones and the rule is the same in both: the engine goes where the coverage is, and language is how it narrows the field rather than what it optimizes for. That is why a thin translated page loses to a dense English one, and why translating forty pages into six languages usually buys less than translating six hundred into one. It also means our own figures carry an unstated method, so weigh them accordingly and read the sources underneath.

Nobody Can Hand You Your Own Number

The gap here is specific, and it is not closing. Anthropic computed how often each language appears in Claude.ai conversations across a million of them, then declined to publish the base rates, calling a fuller cross-lingual analysis a direction for future work.20 OpenAI’s own study of roughly 1.1 million conversations reports the country an account was registered in and no language composition at all.21

The measurement industry has the same hole by design, and so does the trade that sells localization.

11.84 billion citations in Profound’s study carry a limitation stating it does not account for differences along the dimensions of region or language.22
1,058 participants across 45 countries answered the 2026 European Language Industry Survey, which does not use the phrase AI search anywhere in the report.23
The best-known vendor studies, from Semrush and Ahrefs, are United States only.22

So the famous numbers in this field were not built to answer the question you are being asked to sign off on, and the people selling you the answer have not measured it either.

A country figure would not rescue you even if one existed. In WildChat, the only corpus publishing both tables side by side, German is 1.30% of turns while Germany is 3.58% of conversations by location.19 A meaningful share of buyers in non-English markets ask in English, so you are serving two populations in every market and the engines treat them differently.

Wihan van Zyl
GTM Consultant @ Empact Partners
The reason this has to be measured rather than read off a study is sitting in the WildChat numbers: German is 1.30% of turns while Germany is 3.58% of conversations. Every market you sell into contains buyers asking in English and buyers asking in their own language, and the engines answer those two populations from different webs. A single localization decision serves one of them. Which one it should serve is a question about your own locales, and it has an answer you can go and get.

Empact Partners is a consultancy that runs go-to-market work for B2B software companies. This is the measurement we run before anybody signs a translation budget, reading what each engine already cites in each language a partner sells in, per locale rather than once per brand.

What follows it is the partner’s own estate first, documentation included, then the local third-party layer, and it moves over quarters rather than weeks. We built the measurement because search stopped being one box on one site, and Search Everywhere Optimization covers every surface a buyer searches, each language included.

On the partnership whose case study publishes the shape of it, buycycle expanded into 32 languages and countries with 500%+ organic growth.27

What To Watch Before You Spend

Watch one thing before you spend anything: the share of answers in each locale that name you at all, split by engine. Not the average across markets, which will look survivable while one market sits at zero, and not traffic, which measures the wrong surface entirely.

If you are being asked to sign for localization and cannot say what the engines in those markets already cite, book a meeting with me. We will start with the locales you sell into, and what the engines there already cite.

Sources

  1. Temso AI, “Lost in Translation: How AI Models Handle Local-Language Sources”, last updated 20 April 2026. Over 4 million source-to-prompt language pairs for non-English prompts, drawn from a dataset of 7,058,891 citations across 350,000 responses, four engines, six non-English languages, 12 countries and 47 industries, window stated as early 2026. The language detector is not named. Read 1 October 2026.
  2. Weglot, “How AI Search Engines Cite Sources by Language and Country”, 27 July 2026, updated 8 September 2026. 400 questions across five categories and three lengths, each asked in English and in the local language, four systems across five countries, more than 16,000 answers. Per-market shares are printed as chart data labels. How page language was detected is not stated. Read 1 October 2026.
  3. Weglot, “Does AI Favor Translated Content? (+1.3 Million Citations Analyzed)”, 2026. 153 sites without an English version across 22,854 queries, then 83 sites carrying both versions across 12,138 queries, 1.3 million citations in total. A translation vendor measuring translation. Read 1 October 2026.
  4. MaxAEO, “Local sources in AI citations by country”, 2026. 200 commercial-intent B2B software prompts per market in each market’s own language, seven engines, twelve markets, 412,000 answer captures and 1.06 million citation links, 1 March to 15 June 2026. Shares are of non-vendor citations. Read 1 October 2026.
  5. SISTRIX, “AI Citation drift: How stable are sources in AI search results?”, 28 April 2026, updated 21 August 2026. 82,619 prompts and 1,548,213 snapshots across six countries, three platforms and 17 weeks, 17 December 2025 to 8 April 2026. The language and page-type findings rest on a classification of 2,556 cited URLs and describe the stable core of cited domains. Read 1 October 2026.
  6. Peec AI, “ChatGPT searches in English, even when you don’t”, 12 February 2026. Over 10 million prompts and 20 million query fan-outs from the vendor’s own platform data, ChatGPT only, window stated only as recent months. Read 1 October 2026.
  7. Peec AI, “Translated Reddit Is Winning AI Citations”, 22 June 2026. 64.77 million Reddit citations across 20 countries and four engines, 1 March to 10 June 2026, of which 3,699,577 carried Reddit’s own translation parameter. Every share has Reddit citations as its denominator. Read 1 October 2026.
  8. Evocia, “AI Sources Index 2026”, published 14 September 2026, data recalculated 17 September 2026. 200 B2B software purchase questions in French across ten sectors, five intents and four query forms, each asked four times: 800 responses, 2,259 citations, 288 domains, through the OpenAI Responses API rather than the consumer product. Read 1 October 2026.
  9. Radyant and OMR Reviews, “Software prompt study”, 2026. 96 German-language, Germany-located commercial-intent B2B software prompts in eight categories on five engines, 20,160 chats and roughly 156,000 source mentions, 4 to 30 June 2026, built from aggregated Peec AI exports. Read 1 October 2026.
  10. SE Ranking, “AI Overviews Already Appear on Over 52% of French Searches”, 18 August 2026. 100,000 keywords across 20 niches in France collected 7 and 8 August 2026, 52,564 answers carrying sources, 363,330 citations. How source language was detected is not stated. Read 1 October 2026.
  11. SE Ranking, “Review Platforms in AI Overviews”, 2026. 30,801 keywords, a 1 December 2025 snapshot of 22,975 German AI Overviews against 22,729 American ones, same day and same method. Measures domain composition rather than page language. Read 1 October 2026.
  12. Senuto, “Raport z Analizy AI Overviews w Polsce”, updated 21 August 2025. 17,763,868 phrases for Poland, May to June 2025, from Google Search Console data plus 1,435 Polish domains after filtering. How a source’s language or foreignness was determined is not stated. Read 1 October 2026.
  13. arXiv, “The Language of the Question Selects the Market”, 2026, a preprint. 234 usable runs collected 29 and 30 August 2026, six query languages across four exit countries, six identical runs per cell, on the logged-out ChatGPT interface and the OpenAI API. Read 1 October 2026.
  14. arXiv, “Generative Engine Optimization: How to Dominate AI Search”, University of Toronto, 10 September 2025, a preprint with no stated venue. 100 ranking-style prompts across ten consumer verticals translated into five languages, data collected August 2025. Figure 12 prints no per-engine percentages. Read 1 October 2026.
  15. Amazon, “XRAG: Cross-lingual Retrieval-Augmented Generation”, Findings of EMNLP 2025. Table 7 reports the share of queries for which native-only, English-only and both sets of results independently provided sufficient information, for three locales, with sufficiency judged by Claude 3.5 Sonnet. Read 1 October 2026.
  16. Association for Computational Linguistics, “XOR QA: Cross-lingual Open-Retrieval Question Answering”, NAACL 2021. 40,000 information-seeking questions across seven non-English languages that could not be answered in their own language, on Wikipedia. Used for mechanism rather than magnitude. Read 1 October 2026.
  17. Microsoft, “Grounding with Bing Search” documentation, last updated 27 August 2026. Defines the retrieval market parameter as a language-and-country pair. Read 1 October 2026.
  18. W3Techs, “Distribution of content languages among websites that use .de”, a continuously updated survey of a sample stated as well over 20 million sites, with the .com segmentation read from the same survey. The denominator is websites whose content language W3Techs knows, and the detection method is not stated. Read 1 October 2026.
  19. arXiv, “WildChat: 1M ChatGPT Interaction Logs in the Wild”, ICLR. Table 5 reports the language breakdown of conversation turns beside the share of conversations by country, collected by offering free access to a ChatGPT front end in exchange for consent. Read 1 October 2026.
  20. Anthropic, “Clio: Privacy-Preserving Insights into Real-World AI Use”, one million Claude.ai Free and Pro conversations. The paper describes computing a per-language base rate and states that a fuller cross-lingual analysis remains a direction for future work. Read 1 October 2026.
  21. OpenAI and the National Bureau of Economic Research, “How People Use ChatGPT”, Working Paper 34255, approximately 1.1 million conversations sampled between 15 May 2024 and 26 June 2025, with country taken from the country of account registration. No language composition is reported. Read 1 October 2026.
  22. Profound, “Where do AI citations come from?”, 11.84 billion citations across eight engines and 8,061 categories, 16 April to 16 July 2026. Its limitations state that the analysis does not account for differences along the dimensions of region or language. Read 1 October 2026.
  23. European Language Industry Survey, ELIS 2026 report, 1,058 participants across 45 countries. The full report text was extracted and searched; the phrase AI search does not appear in it. Read 1 October 2026.
  24. Qvery, “Why Google AI Mode Cites TripAdvisor 9x More Than ChatGPT”, 8 May 2026. No method, sample size, window or host-classification rule is stated on the page. Shares are of that platform’s own citations across ChatGPT and Google AI Mode. Our sister company. Read 1 October 2026.
  25. Qvery, “ChatGPT Has Cited Quora Zero Times. Google AI Mode Cites It Constantly.”, 8 May 2026. No method is stated, and its statements about non-English content carry no figures. Our sister company. Read 1 October 2026.
  26. Qvery, “Listicles Are the Most Cited Content Type in AI Search”, March 2026. Content type classified by title-pattern matching, which names roughly 12% of citations, across ChatGPT and Google AI Mode. Our sister company. Read 1 October 2026.
  27. Empact Partners, the buycycle case study, read 1 October 2026. The expansion into 32 languages and countries, the organic growth and the raise are the figures the case study itself publishes; the case study states its organic growth only as a percentage, so no session count appears anywhere here.
  28. Microsoft, Bing Web Search language and market support reference, marked retired by Microsoft. States that Bing returns content only for the markets it lists, and lists most countries with a single language-and-country pair. Read 1 October 2026.

Ready
To Connect?

Let's Partner