Diagnosing Hreflang Errors and Wrong-Country Rankings

A typical report reads: "our UK page ranks in Germany". Before anyone edits tags, write down exactly what was observed: the query, the country and language settings used, the date, the URL that appeared and the URL that should have appeared. Without that record, a fix cannot be confirmed and a coincidence can be mistaken for a cure.

Step 1: confirm the symptom

Search results vary by location, language and device, and in September 2026 Google documented Search features that differ by country. A screenshot from one office does not show what users in another country see. Re-check with a method you can repeat, note the settings, and keep the record. If you cannot reproduce the problem, say so in the report instead of fixing something that may not be broken.

Step 2: read the annotations on both pages

Look at the rendered HTML (or the HTTP header, or the sitemap entry) of the page that appeared and of the page that should have appeared. Check them against Google's list of common mistakes:

• Missing return links. The German page lists the UK page, but the UK page does not list the German page. Google ignores tags that are not confirmed in both directions.
• Incorrect language codes. A non-ISO 639-1 value, or a country code typed in place of a language.
• Incorrect region codes. en-UK instead of en-GB, or a region with no language.

Paste both sets into the workbench for a quick syntax pass, then compare them line by line. Small differences such as a trailing slash count.

Step 3: check the canonical of every version

Google asks that, with hreflang, each page's canonical is in the same language. If the German page names the UK page as canonical, Google may fold the German page into the UK page, and the UK page then appears in Germany for queries the German page should answer. Google's canonicalization guide also says that when choosing canonicals it prefers URLs in hreflang clusters, which is one more reason to fix the cluster rather than the symptom.

Also check for the case Google warns about directly: localized versions are only considered duplicates if the main content remains untranslated. A "German" page with English body text is, to Google, a duplicate of the English page.

Step 4: check whether Google can see each version

This step matters more in iGaming than in most sectors, because gambling sites often block visitors by country for legal reasons. Google's multi-regional guidance says Googlebot usually originates from the USA and sends requests without an Accept-Language header. Two consequences follow:

1. If a market version is only served to visitors with a local IP address, or redirects US visitors elsewhere, Googlebot may never receive it. Google warns that it might not find and crawl all variations of locale-adaptive pages.
2. If the server picks the language from Accept-Language, Googlebot gets the default version every time.

Test each URL the way Googlebot would: from a US connection, without an Accept-Language header. Use the URL Inspection tool in Search Console to see the page Google fetched. If the market page is not reachable that way, no hreflang edit will fix the problem. Our switching and redirects guide covers how to keep information pages crawlable while gambling functions stay restricted where the license requires it.

Step 5: rule out plain competition

Hreflang helps Google choose between your own versions. Google describes its benefit as pointing users to the most appropriate version of a page by language or region. It does not make a weaker page outrank a stronger one. If the "wrong" result in Germany is a page from your global site, that is an hreflang question. If it is a competitor, it is a ranking question, and the report should say so.

Step 6: write the finding so others can check it

A useful finding names the page, the evidence, the cause and the confidence. For example: "On October 26, 2026, the de-DE page listed five alternates but not the en-GB page; the en-GB page listed the de-DE page. Return link missing; fix the de-DE template." Avoid promises about traffic or rankings. Google's guidance supports saying the cluster is now valid; it does not support predicting how much traffic will move.

Questions

Where did the hreflang report in Search Console go?

Google deprecated the International Targeting report, including its country-targeting setting, and said it would continue to support and use hreflang tags. There is no direct replacement, so crawl your own site to audit annotations.

Does Google use the HTML lang attribute to detect language?

No. Google says it does not use hreflang or the HTML lang attribute to detect a page's language; it uses the visible content. Set lang correctly for accessibility and other tools, but fix the content if Google reads the language wrongly.

How long until a fix shows in search?

Google has to recrawl every page in the cluster before the corrected pairs count. That depends on crawl frequency, so record the date of the fix and re-check over the following weeks rather than promising a date.

Sources

1. Google Search Central, Tell Google about localized versions of your page, last updated September 21, 2026.
2. Google Search Central, How to specify a canonical with rel="canonical" and other methods, last updated July 10, 2026.
3. Google Search Central, Managing multi-regional and multilingual sites, last updated December 10, 2025.
4. Google Search Central, Latest Google Search documentation updates (entry of September 8, 2026, on Search features that differ by country).
5. Google Search Console Help, The International Targeting report is deprecated, no date shown.