HB Crossborder Get a free check

Insights ⁠·⁠ Search and AI trends

Wrong language page in Google? Eight multilingual site mistakes

2026-09-11 ⁠·⁠ By Uihyun Moon ⁠·⁠ 5 min read

A close-up of an open dictionary page
Photo: Words as Pictures / StockSnap (CC0)

A buyer in Zurich searches for your brand and Google shows the page for Germany, with euro prices and a delivery note that leaves out Switzerland. A buyer in Lyon lands on your English homepage because a script guessed wrong. Neither is really a ranking problem. Both are labelling problems, and most can be found in an afternoon.

In three lines
  • Google reads a page's language from its visible text and chooses a country version from signals such as hreflang, the domain, local addresses and currency.
  • hreflang links that are not returned by the other page are ignored, and codes such as en-UK or es-419 do not work as intended.
  • Near-identical country versions in one language are grouped under one canonical URL, and Google says the alternates can still be shown to the matching audience.

How Google decides which version to show

Google picks a version of your page for each searcher from several signals, and most mistakes come from sending mixed ones. Its guide to multi-regional and multilingual sites (updated 10 December 2025) lists them: a country-code domain such as .de, hreflang annotations, server location, and other clues such as local addresses, phone numbers, currency and your Business Profile. It reads the language of a page from the visible text, not from the lang attribute or the URL, and it ignores geo meta tags.

Two details catch many small sites out. Most Googlebot crawling comes from the US, and the crawler sends requests without an Accept-Language header. A site that chooses the language by IP address or browser setting may therefore show Googlebot only one version, and Google cannot index what it never sees. Google's advice is to give each language its own URL, link the versions to each other, and avoid automatic redirects.

For your company: hreflang does not push a page up the rankings. Google describes it as a way to point people to the most appropriate version of a page. If your German page never ranks in Germany, look at the content first. If your English page ranks in Germany while a German version exists, that is a labelling problem, and the rest of this column is for you.

Eight mistakes and their fixes

Each row below comes from Google's own documentation: the hreflang guide (updated 22 December 2025), the multilingual sites guide, the guide to locale-adaptive pages and the canonical URL guide (updated 10 July 2026).

MistakeWhy it mattersFix
Page A lists page B, but B does not list AGoogle ignores links that are not returnedEvery version lists itself and all the others
A country code on its own, such as be for BelgiumThe first code is always a language; be means BelarusianLanguage first: nl-BE, fr-BE, de-BE
Codes like en-UK, en-EU or es-419UK and EU are ignored as regions; es-419 is not supportedISO codes only: en-GB, es-MX, or plain es
Relative links such as /de/pageAlternate URLs must be fully qualifiedFull URLs starting with https://
Every language's canonical points to the English pageGoogle asks for a canonical in the same languageEach translation names itself as canonical
Redirects by IP address or browser languageGooglebot may only ever see one versionLet people choose; link the versions visibly
Only the menu and footer are translatedPages count as duplicates if the main content is untranslatedTranslate the main content, or skip that version
noindex or robots.txt rules differ by localeGoogle asks for the same robots rules in every localeApply one set of rules across all versions

Keeping every pair complete gets harder as you add languages. The hreflang guide allows some slack: you can leave some languages out on some pages, and Google still processes the pairs that point to each other. What it asks you not to skip is the two-way link between a new language version and your original main language.

For your company: pick one product page and open its source code in each language. You should see the same set of hreflang links on every version, each with a full https address, including one pointing to the page itself. Where the sets differ, the unmatched pairs are ignored. Then check which of these rules your website builder or translation plugin handles for you, and which it leaves to you.

Same language, different countries

The hardest case for small exporters is one language in several countries: German for Germany, Austria and Switzerland, or English for the UK, Ireland and the US. When the pages are nearly identical, Google groups them and picks one canonical URL. That is expected. Gary Illyes of Google wrote on LinkedIn, as reported by Search Engine Roundtable on 10 August 2026, that hreflang alternates are "not in fact indexed in the proper sense". They become alternate names of the canonical URL, and Google can still show them to the audience they are meant for. A "not indexed" or duplicate status for your de-AT page in Search Console is not, on its own, a fault.

Google's canonical guide adds one detail that matters here: when choosing a canonical, Google prefers URLs that are part of an hreflang cluster. If /de-de/ and /de-ch/ point to each other but neither points to /de-at/, the Austrian page is the one left out.

John Mueller of Google said in June 2026 that he would not expect a practical SEO difference between /blog/ and /en-us/blog/ for US content, and suggested avoiding exact copies across country versions (Search Engine Roundtable, 16 June 2026).

For your company: build a separate country version only when something real differs: price, currency, delivery terms, stock or legal notices. If nothing differs, one German page labelled de can serve all three countries, and you keep one page current instead of three.

Give everyone else a way out

Google recommends an x-default entry for visitors whose language matches none of your versions, and says it was designed for language selector pages. Its multilingual guide also says geotargeting "isn't an exact science" and suggests visible links on every page so people can switch language or region themselves.

For your company: point x-default at your language selector or your main international page. Make the language switcher link to the same page in the other language, not to the other homepage, so a visitor who lands on the wrong version is one click from the right one.

Check it in one hour

  1. In Search Console, open the Performance report, filter by one target country and look at the Pages tab. If Germany shows mostly /en/ addresses while German versions exist, start there.
  2. Run the URL Inspection tool on that German page and compare the canonical you declared with the one Google selected.
  3. Compare the hreflang lines in the source of two language versions, line by line.
  4. Search the way a customer would, with Google set to that language, for example markenname versandkosten schweiz (brand name, shipping costs, Switzerland), and note which version appears.

If you have been searching for "hreflang not working" or "Google shows the wrong country version of my site", run the four checks above before changing anything. A fix to one mismatched set of tags is often enough, and a redesign rarely is.

If you would like a second pair of eyes, HB Crossborder's free visibility check covers website basics and tests five real customer questions in Google AI Overviews, ChatGPT and Perplexity, with the report in English, German, French, Korean or Chinese. See what we do, or send one URL and get a free visibility check within 48 hours.

Try this week
  1. Open the Search Console Performance report, filter by each target country and list the pages shown in the wrong language.
  2. Compare the hreflang lines in the source of two language versions of one product page and fix any set that differs.
  3. Replace country-only or invalid codes such as be, en-UK or es-419 with ISO codes such as nl-BE, en-GB or es-MX.
  4. Remove any redirect that chooses the language by IP address or browser setting and add a visible language switcher instead.
  5. Point x-default at your language selector or main international page.
  6. Merge same-language country versions that differ in nothing but the URL.
Wondering how your business shows up today?

Send us one URL and get a free visibility report within 48 hours.

Get a free check
Sources
  1. Tell Google about localized versions of your page, Google Search Central (2025-12-22)
  2. Managing multi-regional and multilingual sites, Google Search Central (2025-12-10)
  3. How Google crawls locale-adaptive pages, Google Search Central (2025-12-10)
  4. How to specify a canonical URL with rel="canonical" and other methods, Google Search Central (2026-07-10)
  5. Google: Hreflang URLs Not Indexed In The Proper Sense, Search Engine Roundtable (2026-08-10)
  6. Google: No Practical SEO Difference By Going With Folder For US Site, Search Engine Roundtable (2026-06-16)

General information, not legal or tax advice. Check with a professional before acting on it.