Hreflang is the single most-broken thing on multi-region websites. Out of 100 international sites we audit in a typical year, 80+ have hreflang errors that cost rankings — usually silently.
This is the 2026 hreflang checklist we use on every multi-region engagement. Validate your implementation, fix the common mistakes, and build country-specific link profiles to support each market.
The hreflang fundamentals
Hreflang tells Google which page version to serve which user. The basic syntax:
en-us— English content for US users.en-gb— English content for UK users.es-mx— Spanish content for Mexico users.x-default— fallback for everyone else.
Done right, hreflang prevents duplicate-content issues and serves the right page to the right region. Done wrong, it confuses Google and tanks rankings everywhere.
The 8 most common hreflang mistakes
- Missing self-references. Each page must have a hreflang tag pointing to itself.
- Inconsistent return tags. If page A points to page B, page B must point back to page A.
- Wrong language/region codes. Use ISO 639-1 for language, ISO 3166-1 alpha-2 for region. Not
en-uk— it''sen-gb. - Pointing to non-canonical URLs. Hreflang must point to canonical versions, not redirected or parameterised URLs.
- Missing x-default. Without it, Google guesses where to send users from regions you haven''t covered.
- Mixed implementation. Hreflang in HTML head + sitemap + HTTP headers — pick one method and stick with it.
- HTML-only on JS-rendered pages. If your hreflang only renders client-side, Google may miss it. Use server-side or sitemap.
- Wrong country variants. Don''t serve generic "English" to UK users when you have a UK-specific version available.
How to validate
Three tools we use on every multi-region audit:
- Search Console — International Targeting report shows hreflang errors at scale.
- Screaming Frog — crawl with hreflang checks enabled, exports the full mismatch list.
- Manual SERP testing — search from VPNs in target regions, confirm the right version appears.
Beyond hreflang: country-specific signals
Hreflang alone doesn''t guarantee local rankings. Each market needs supporting signals:
- Country-specific content — local pricing, currency, examples, terms.
- Local backlinks — links from country TLDs (
.uk,.com.au,.in) signal local authority. - Local Business Profile / GMB — for any market where you have a physical presence.
- Country-specific schema — Organization addressCountry, areaServed properties.
Key Takeaways
- 80% of multi-region sites have broken hreflang — usually from missing return tags or wrong codes.
- Validate via Search Console, Screaming Frog and VPN-based SERP testing.
- Hreflang is necessary but not sufficient — local content and backlinks must support it.
- Pick one implementation method (head, sitemap, or HTTP) and stick with it.