Hreflang the way it actually works
Most international sites have at least one hreflang bug. Here's how to find yours.
Hreflang is conceptually simple and operationally brutal. The bugs are almost always in the return-tag chain, not the syntax. Every international audit we run finds at least one broken cluster, and most find five. The fix is rarely glamorous, but the traffic recovery is.
The audit
Crawl every alternate URL and verify it returns to its sibling. If the chain breaks, Google falls back to the wrong locale and CTR on the right market collapses. Use Screaming Frog's hreflang report or a custom script — Search Console's coverage of hreflang errors is incomplete.
The deployment
Sitemap-based hreflang scales better than head tags. Generate from a single source of truth, not per-template. Head-tag implementations break the moment a developer copies a template without remembering the locale logic.
The five most common bugs
- Missing x-default — usually the global English site should claim it.
- Wrong region code (en-UK doesn't exist; it's en-GB).
- Self-referencing tag missing from one locale in the cluster.
- Trailing-slash inconsistency between locales.
- Stale alternates pointing to URLs that 404 or redirect.
What to measure after the fix
Locale-specific impressions in GSC, country-specific CTR, and bounce rate from organic by country. Expect a 10–25% lift on the markets that were previously being served the wrong locale.
