What breaks rankings when hreflang is set up slightly wrong?
- Published November 6, 2026
- Linked from 2 answers
- In a cluster of 4
Not rankings so much as which version of the page appears where. A hreflang mistake affects the pairs of pages it touches: Google’s documentation on localized versions says “If two pages don’t both point to each other, the tags will be ignored.” The broken pair loses its routing, and Google falls back to its own judgment of which version to show, which can put your US page in front of UK searchers or your English page in front of German speakers. Other pairs in the same group that are set up correctly keep working.
Errors and their effect
| Error | What happens |
|---|---|
| Missing return link: page A lists page B, but B does not list A | Google ignores the annotation between A and B |
| A wrong code, such as a country code where a language code should be | The annotation is not understood for that version |
| Hreflang pointing to a URL that redirects, returns an error or is noindexed | The reference points to a page Google will not show, so it has nothing to route to |
| Hreflang and canonical disagree: a version canonicals to another language's page | Google is told the version is a duplicate of a page in another language, and the version may drop out |
| Each version missing its own self-reference | The set is incomplete, and Google may not read it as intended |
The canonical row is the one that can cost visibility, not only routing. A page translated into another language should not canonical to the main language version. Same-language regional versions are a separate case: where they are close copies, Google’s multi-regional guidance is to pick a preferred version and use canonical and hreflang together, so check the Google-selected canonical in URL Inspection rather than assuming every version is its own. Hreflang’s self-reference, the last row, is a different thing from a self-canonical; do not treat one as the other.
Finding the problem
- Search for your page from the affected country, or check the Performance report filtered by country and page, to see which version appears.
- For the affected pair, open both pages’ source or headers and confirm each lists the other and itself with the right code.
- Check that every URL in the hreflang set returns 200 and is indexable, and that its canonical matches your plan: a distinct language or regional version canonicals to itself, while a close same-language regional copy may point to the preferred version, as the section above explains. Then compare each declared canonical with the Google-selected canonical in URL Inspection.
- If you generate hreflang in the sitemap, confirm the sitemap and the pages do not contradict each other.
Every fix above assumes the versions are worth keeping; if that is in doubt, start with when hreflang is worth the complexity. If you rank abroad but not at home, the setup is only one of the causes in what it means when you rank in some countries but not your own. Fix the pair that is broken, and the rest of the group stays as it was.
Add a comment