Common hreflang Errors on Multilingual Sites: The Full List
Key takeawayhreflang tells search engines how your language and region versions relate to each other. Its implementation is more fragile than most people expect: a single annotation mistake can invalidate the entire reciprocal group, causing language versions to replace each other in search results.
When this applies
- Standalone sites offering the same product in multiple languages
- Sites that split pages by region rather than language (e.g. de-DE / de-AT)
- Sites using hreflang that have never received any confirmation in search tools
- Sites whose language versions randomly appear in regions where they should not
| Error type | Typical pattern | Consequence | Correct approach |
|---|---|---|---|
| Reciprocal loop not closed | A points to B, but B does not point back to A | The whole group is invalidated | Every version must point back to every other version |
| Non-200 response codes | A language version returns 302 or 404 | That annotation is ignored | Language versions must be directly accessible |
| Missing x-default | Only specific languages, no fallback | No fallback behavior | Add an x-default annotation |
| Inconsistent case or format | zh-CN mixed with zh-cn | Treated as different regions | Use one standard format consistently |
| Pointing to a non-canonical URL | hreflang targets a URL with query parameters | The signal points to the wrong page | Point to the canonical target |
| Placed outside the head | Tags written inside the body | Some parsers ignore them | Keep all hreflang tags inside <head> |
| Relative URLs | href="/en/page" | Ambiguous resolution base | Use absolute URLs |
Step-by-step diagnosis
- List every URL on the site that uses hreflang and export all annotation values.
- For each URL, verify that every target returns 200 — any annotation pointing to a non-200 URL is invalid.
- Verify the reciprocal loop: the set of languages each URL declares should match what the target pages declare, and the targets must point back.
- Confirm that every hreflang target matches the page's own canonical target, so the two signals do not conflict.
- Standardize the language tag format (BCP 47 is recommended, e.g. zh-Hans, en-US, de-DE) and apply it site-wide.
- Add x-default, pointing to the language selector page or the primary language version.
- Review the International Targeting report in GSC for annotations actually recognized, and fix the reported errors.
Common mistakes
- Assuming hreflang "tells Google which language to show" — its role is to declare version relationships, not to force a display choice.
- Adding hreflang to only some pages — partial coverage is worse than none, because it creates inconsistent signals.
- Injecting hreflang with JavaScript — many parsers read the head before executing JS.
- Having language versions 302-redirect to the homepage — that effectively means you have no language versions.
- Missing the case where hreflang and canonical point to different pages, so the two signal sets cancel each other out.
FAQ
What happens if hreflang and canonical conflict?
When the two signal sets contradict each other, search engines may ignore one of them or pick the most conservative interpretation. The safest setup is a self-referencing canonical on every URL that hreflang points to.
Does missing hreflang always hurt rankings?
Not rankings directly, but it does affect how international traffic is distributed and the accuracy of regional targeting.
Can language versions be implemented with parameterized URLs?
Not recommended. Parameters make both hreflang and canonical harder to configure correctly. Path prefixes (/en/, /de/) are more robust.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Why Google Does Not Index Infinite Scroll Product Lists — and the FixesCanonical Tag Conflicts Causing Duplicate Indexing: How to Fix ThemXML Sitemap Errors: Types and Fixes ComparedWhy Breadcrumb Schema Errors Make Rich Results DisappearOn-Site Duplicate Content: Judgment Criteria and a Prevention ChecklistNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.