Is hreflang distorting your indexation reports in Search Console?

Why does Google canonicalize regional versions that are supposed to be distinct?

When multiple URLs offer quasi-identical content in the same language (German for DE, AT, CH for example), Google treats them as duplicates. Rather than indexing all variants, it chooses one as the canonical version and consolidates signals there.

The problem? This canonicalization happens even when hreflang is correctly implemented. Google sometimes ignores your annotations if the content is too similar.

How does Search Console report these canonicalized pages?

Search Console displays only the canonical version chosen by Google. The other regional URLs disappear from indexation reports, performance data, and coverage.

Concretely, you see your /de/ page indexed, but /de-at/ and /de-ch/ don't appear anywhere — even though they're technically crawled and eligible. This is a reporting black hole.

What are the practical consequences of this confusion?

You might panic thinking your regional variants have been deindexed or penalized. In reality, they're simply hidden from reporting because Google treats them as duplicates of the canonical.

Another risk: you might over-optimize or unnecessarily modify these pages thinking they have an indexation problem.

• Google canonicalizes regional versions with too-similar content even if hreflang is present
• Search Console only reports the canonical chosen by Google, not all variants
• The other URLs aren't deindexed — they're just invisible in reports
• This confusion can lead to incorrect diagnostics and unnecessary SEO actions

Is this statement consistent with real-world observations?

Yes, and it's frustrating. We regularly observe multilingual sites with perfectly configured hreflang where Google completely ignores the annotations and canonicalizes to a single version. The content is often too close for Google to consider the regional distinction meaningful.

The major problem? Google doesn't warn you. No alerts in Search Console. You discover canonicalization by analyzing server logs or testing the URL Inspection Tool on each variant — and there, surprise, Google tells you a different canonical than the one you declared.

What nuances should be added to this claim?

Gary Illyes remains vague about what exactly triggers this canonicalization. He talks about "quasi-identical" content — but what similarity threshold does Google apply? 90%? 95%? No concrete data. [To verify] on your own sites with content at different differentiation levels.

Another point: this statement implies hreflang is respected except when content is too similar. Let's be honest — that amounts to saying hreflang only works when content is sufficiently distinct, which severely limits its usefulness for legitimate regional variants.

In what cases does this rule not apply?

If your regional variants have genuinely differentiated content — local adaptations, currencies, cultural references, region-specific customer testimonials — Google should respect your hreflang annotations and not arbitrarily canonicalize.

But watch out — this is where it gets tricky: even with visible differences, if the HTML structure and main body text remain identical at 85-90%, Google may still decide it's duplicate. You really need to make a strong effort to differentiate.

How do you verify if Google is canonicalizing your regional variants?

Use the URL Inspection Tool in Search Console on each regional variant. Look at the "Canonical URL selected by Google" line. If it points to a different version than the one declared in your hreflang, you're affected.

Supplement with a site:yourdomain.com/de-at/ search in Google. If results are empty or only show the /de/ version, it's confirmed: canonicalization underway.

What concrete steps should you take to avoid this problem?

The only reliable solution: genuinely differentiate content between your regional variants. Not just changing two words — you need unique sections, local examples, adapted calls-to-action, region-specific customer testimonials.

If content must remain identical (for legal reasons or standardized products, for example), accept the canonicalization. Focus your SEO efforts on the canonical version and use hreflang only for geographic distribution of search results.

• Audit all regional variants with the URL Inspection Tool to identify unwanted canonicalizations
• Analyze content similarity rate between variants (tools like Copyscape, Siteliner)
• Differentiate each variant's content with unique local sections (minimum 20-30% distinct content)
• Regularly monitor server logs to verify Googlebot crawls all versions
• Don't rely solely on Search Console — cross-check with site: and URL Inspection Tool
• If canonicalization is unavoidable, focus SEO on the canonical version and accept that others serve only for regional distribution