Why Google Shows the Wrong Language Version: The Query Language Decides
Dominik Breitbach founded taismo GmbH and works as lead SEO strategist on SEO retainers and visibility inside AI answers. He runs taismo as an SEO and GEO agency from Munich and advises companies in German and English.
Google shows the wrong language version of your page when someone searches in the other language, even in the right country and even with correct hreflang. Google names the language of the query as the first of five factors it uses to pick the result language: “The language you type your search in is important.” In our own data, the English version of a glossary entry collected 36,533 impressions from Germany in three months, the German version 128, because people typed “ai mode” in English. hreflang only tells Google which pages are language versions of each other, and Google’s documentation mentions no ranking advantage for it. To be shown in the right language, a page needs the words its audience actually types, in the language they type them.
👉 How well do Google and AI systems read your page? Run the free AI visibility check
The reason: Google matches the result language to the query
Why does Google show English pages to people in Germany, or Spanish pages to people in Texas? Because the query was in that language. Google chooses the result language from several signals, and the language someone searches in is explicitly one of them. If someone in Munich types an English product name, an English page fits that query well from Google’s point of view. Location and hreflang change little about that.
The same logic hits every multilingual website: A Canadian site with French and English versions, a US retailer with English and Spanish pages, a German manufacturer with an English export site. Whenever the core term of a page is commonly typed in another language, the version in that language competes for it.
Our case: AI Mode in German and in English
Our own SEO wiki shows the effect clearly. The glossary entry on Google’s AI Mode exists in German (779 words) and in English (860 words). Both have been online since August 13, 2026, are linked to each other with hreflang, and carry a canonical tag pointing to their own URL. In Google Search Console, filtered to the country Germany, the English page received 36,533 impressions from July 4 to October 2, 2026, the German page 128. Almost all of it came from one query: “ai mode” with 33,153 impressions, where the English page held an average position of 5.7 and the German page 20.2.
The trigger was a wave of demand in late August and September 2026, when many people in Germany searched for the new feature. Most of them wanted to open AI Mode itself, a navigational search intent, so there were hardly any clicks. For the question of which language version Google picks, the case is still a clean test setup: Same content, same date, correct technical setup, and a clearly English query.
The counter-check: German query, German page
If the query language tips the balance, a German query has to bring up the German page. That is exactly what our data from Germany shows for the same period:
- “ai modus”: 18 impressions for the German glossary page and 46 for our German article on AI Mode. The English page does not appear for this query.
- “local seo agentur”: 339 impressions for our German local SEO page. The English version does not appear here.
- “local seo services”: 165 impressions for the English version, 1 for the German one. English query, English page, even in Germany.
One observation calls for caution. In the US, Google mostly shows the English version for the German query “local seo agentur” (119 impressions versus 5). There, location and language settings evidently weigh more. The query language is a strong signal among several. Our data are strong indications, and they stop short of proof: Search Console shows what Google displayed and keeps the reasons to itself.
What Google says about result language and hreflang
Google has described how it picks the language of search results. The Google Search help names five factors: The language you search in, the language you use on Google, the language of your computer or phone, where you are, and what website owners say. On the first factor, the help page states: “The language you type your search in is important.” Location helps, according to Google, “when words are the same in different languages, like ‘taxi.’”
In the Search Central Blog, Google explains why settings alone do not decide: “About half the people searching with Google are multilingual and often search in a language that doesn’t match their settings.” After several updates, the same post says, the changes “should better match results to the language someone searches in.”
On hreflang, Google says two things. You use it “so that we can understand that these pages are localized variations of the same content.” And: “Google doesn’t use hreflang or the HTML lang attribute to detect the language of a page; instead, we use algorithms to determine the language.” Elsewhere, Google writes: “Google uses the visible content of your page to determine its language.” None of these pages mentions a ranking advantage.
hreflang is hygiene: It maps the versions, the content supplies relevance
Google’s description leads to a sober assessment. hreflang is mandatory for every multilingual website, because without it Google does not know which pages belong together. If the return links are missing, Google warns that the annotations “may be ignored or not interpreted correctly.” hreflang therefore helps Google serve the right version when several versions fit a query about equally well.
Our reading, backed by the case above: If one version fits the query clearly better, that version stays in the results. Whether a page is relevant for a term is decided by its visible content. If you start fixing a language problem by tweaking hreflang, you often look in the wrong place. Once hreflang is reciprocal and complete, the lever sits on the page itself, in the words it contains.
Five lessons for multilingual websites
1. The language of the search term decides which version wins
A local-language page competes with its own English version for every term people type in English. That covers product names such as “AI Mode”, specialist terms such as “local seo services”, software features, and job titles. For every important page, find out in which language each audience types its core term. That language belongs in the title, the H1, and the first paragraph.
2. Both the English term and the local term belong on the page
Google itself calls the feature “KI-Modus” in Germany, since its launch in Germany, Austria, and Switzerland on October 8, 2025. Many people still type “ai mode” or “ai modus”. A German page that carries both the English term and the German term its audience uses has a chance for both queries. A simple rule: The local term of the audience first, the English term as a secondary term, both already in the title and the first paragraph. Search Console shows you which local term that is. The vendor’s official name is a good candidate, and your audience’s data decide.
3. Localizing means writing for search behavior
A literal translation carries over the terms of the source language and often misses how people search in the target market. Localizing starts with the question of which words people there actually type. Sometimes that is the translation, sometimes the English original, sometimes a different word entirely. The result is two versions that match in content and each fit their own market’s searches.
4. Keyword research runs across languages
Keyword research in one language misses the variants people in that market type in another language. Check three forms for every core term: The local one, the English one, and hybrids such as “local seo agentur”. Search Console shows which of them your pages already reach today. For new terms, Google’s search suggestions in both languages help.
5. Glossaries, software terms, and AI answers are hit hardest
The pages most affected are those whose core term is English: Glossaries of specialist terms, product pages for software, and pages about new features of large platforms. For answers from AI search, we expect the same logic, because there too a question is asked in a specific language and answered with matching sources. That is our assessment; we have not measured it yet. If you want your local-language version to be cited, it needs a page that carries the local terms. How we build this for companies is part of answer engine optimization (AEO), also called generative engine optimization or GEO, described on our page about AEO and GEO services.
We analyze your Search Console by country, language, and query and show you which terms are missing on which version. As part of a monthly retainer, with fixed measurement dates.
How to check your terms in 6 steps
You can find out with Google’s own tools whether Google shows your audience the wrong language version:
- Step 1, filter by country: In Search Console under Performance, select the country where your most important audience lives.
- Step 2, filter by language folder: Narrow the pages to /en/ or your other language code.
- Step 3, read the queries: Mark the terms for which the local-language page should actually answer.
- Step 4, compare the counterpart: Pull the same queries for the other language version. Which version gets the impressions, and which gets the better position?
- Step 5, check the hygiene: Make hreflang reciprocal with a self-reference and point the canonical to the page’s own URL. This is a one-time duty.
- Step 6, add the terms and measure again: Bring the local term of the audience and the English variant into the title, H1, first paragraph, and FAQ, then filter again after four weeks.
| Checklist item | Done when |
|---|---|
| hreflang | Every version lists all versions, itself, and x-default |
| Canonical | Points to the page’s own URL |
| Core term in the target language | Appears in the title, H1, and first paragraph |
| Local term of each audience | Is on the page, verified in Search Console |
| English variant | Appears as a secondary term on the local-language page |
| Language switcher | Visible on every page |
| Measurement | Search Console by country and query, at least once a quarter |
For projects across several countries, this check is part of the basic setup. How we approach it is described on our page about international SEO for multilingual websites.
When the other language version hurts and when it helps
- It hurts on pages that are supposed to sell. A prospect from Germany lands on the English service page and finds an English form, a different tone, or prices without the usual details.
- It hurts with mandatory information, when legal, health, or financial notes are complete only in one language version.
- It helps with bilingual audiences. Professionals who search for English terms get a page in the language of their query.
- It is harmless with waves of navigational queries, as in our AI Mode case: Many impressions, hardly any clicks, no lost customer.
Countermeasures almost never mean hiding the other version. Google writes: “Don’t use IP analysis to adapt your content.” Instead, Google recommends links that let users choose their language or region themselves, because “it’s important to consider users who land on the ‘wrong’ version of your site.” The most effective lever remains a page with the right words.
Tip for searchers: How to get results in your language
If you get results in a language you did not want, you have two tools: The results language filter under Tools and Any language, and the language field in Advanced Search. Google points out that “language filters mostly work for web results.” The simplest measure works most reliably: Search in the language you want results in.
Our test: The German page is now called KI Mode
We are testing the second lesson on our own case. In early October 2026, we renamed the German glossary page to “KI Mode”: A German word part, with the English product name still recognizable. The page received a new URL, and the old one redirects to it. The English page stays unchanged. We measure until mid-November 2026: The German page’s share of impressions for “ai mode” (so far 0.2 percent), its position for this query (so far 20.2), and its impressions for German variants such as “ki mode” and “ki-modus”. Because the wave of demand has subsided, we compare shares and positions. The new URL is a second change, and we account for that in the evaluation. An update will follow in this article.
We look at your Search Console by country, language, and query and tell you which terms are missing on your pages. Write to us, in English or German, and we will get back to you with a proposed date.
Frequently asked questions about language versions in Google
Why does Google show the wrong language version of my site?
Usually because the query was in the other language. Google weighs the language of the query alongside location and language settings and often shows the version that matches the words someone typed.
Is hreflang a ranking factor?
Google describes hreflang as a way to tell it that pages are localized variations of the same content. Google’s documentation mentions no ranking advantage from hreflang anywhere.
How do I force Google to show results in English?
Search in English, then use the results language filter under Tools or the language field in Advanced Search. Google notes that these filters mostly work for web results.
Should English terms appear on a page in another language?
Yes, if your audience types them that way. Put the local term your audience uses first and the English term next to it, already in the title and the first paragraph.
Is a translation enough for a multilingual website?
A translation delivers the content, but the terms also have to match how people search in each market. Localizing means checking for every core term which word the audience there actually types.
How can I see which language version Google shows in a country?
In Google Search Console under Performance, filter by country, then narrow the pages to one language folder such as /en/. The list of queries shows which terms trigger that language version.
Sources
- Google Search Central: “Localized Versions of your Pages”, Google for Developers, last updated September 21, 2026.
- Google Search Central: “Managing Multi-Regional and Multilingual Sites”, Google for Developers, last updated December 10, 2025.
- Nahar, S., Tawfiq, A., Sullivan, D.: “How Google Search handles multilingual searches”, Google Search Central Blog, September 8, 2023.
- Google: “How Google knows what language to show in search results”, Google Search Help, accessed October 4, 2026.
- Google: “AI Mode launches in Germany, Austria, and Switzerland” (German-language post, title translated), Google Blog Germany, October 8, 2025.
- taismo GmbH: Own measurement in Google Search Console for the property taismo.de, country Germany (plus the US comparison), period July 4 to October 2, 2026, retrieved October 4, 2026.
