Technical SEO
Hreflang Explained: Implementation and Common Errors
Hreflang tells Google which version of a page suits which language or country. Small mistakes make Google ignore it.
If you have versions of a page for different languages or regions, Google recommends telling it about them with hreflang, so it can show searchers the most appropriate version. Google says it uses algorithms, not hreflang or the HTML lang attribute, to detect a page’s language.
For Laylar’s markets, a typical case is English pages for the US, UK, Canada and Australia, alongside German and Dutch versions.
Short answer: Hreflang annotations tell Google about language and regional versions of a page. Add them with HTML link elements, HTTP headers or an XML sitemap (pick one). Each version must list itself and every other version with fully qualified URLs, and every link must be returned, or Google ignores it. Use ISO 639-1 language codes with optional ISO 3166-1 region codes (en-GB, not en-UK), and x-default for a fallback page.
Key Takeaways
- Three equivalent methods: HTML, HTTP headers or sitemap. Use one.
- Every version lists itself and all others.
- Missing return links make Google ignore annotations.
- Use en-GB, not en-UK; region codes alone are invalid.
- x-default covers users whose language you don’t target.
Example for English markets plus German and Dutch
<link rel="alternate" hreflang="en-US" href="https://example.com/us/" /><link rel="alternate" hreflang="en-GB" href="https://example.com/uk/" /><link rel="alternate" hreflang="en-CA" href="https://example.com/ca/" /><link rel="alternate" hreflang="en-AU" href="https://example.com/au/" /><link rel="alternate" hreflang="de-DE" href="https://example.com/de/" /><link rel="alternate" hreflang="nl-NL" href="https://example.com/nl/" /><link rel="alternate" hreflang="x-default" href="https://example.com/" />
The same set goes on every version of the page.
Rules Google lists
- Each language version lists itself and all others.
- Use fully qualified URLs, including https.
- Alternates can be on different domains.
- If two pages don’t both point to each other, the tags are ignored.
- Provide a generic language page (such as en) as a catch-all where useful.
- Localized pages are only treated as duplicates if the main content stays untranslated.
Common errors
| Error | Fix |
|---|---|
| Missing return links | Add the reciprocal annotation on every version |
| Region code without language (e.g. “gb”) | Always start with a language code: en-GB |
| Invalid region codes such as UK or EU | Use ISO 3166-1 codes: GB for the United Kingdom |
| Relative URLs | Use full https:// URLs |
| Hreflang URLs that redirect or are noindexed | Point to the final, indexable URL |
| Mixing methods inconsistently | Use one method and keep it complete |
Same language, different countries
US, UK, Canadian and Australian English pages can be near-identical. Hreflang helps Google show the right one, but each version should genuinely differ where it matters: prices, currency, spelling, contact details and local information.
Frequently asked questions
Does hreflang help rankings?
It helps Google show the right version to the right users; it isn’t a ranking boost.
Do I need hreflang for one English site serving several countries?
Only if you have separate versions for different countries.
Is en-UK a valid hreflang code?
No. Google says UK has no effect; use en-GB.
Expanding into other countries?
We plan language and country targeting, implement hreflang correctly and avoid duplicate-content problems across markets.
Sources
- Google Search Central: Tell Google about localized versions of your page
- Google Search Central: How to specify a canonical URL
Last reviewed October 14, 2026.
Table of Contents
Need Technical SEO Help?
We find what stops Google from crawling and indexing your important pages, and fix the cause.
Related Guides
Free SEO Audit
A manual on-page and technical SEO review of your website, with prioritized fixes.