What You Will Learn
- What hreflang signals and the difference between language and regional targeting
- The three implementation methods — HTML link, HTTP header, XML sitemap
- Why every hreflang tag must be reciprocal (confirmed by the target page)
- How to use x-default for users who do not match any specific locale
- The most common hreflang errors that cause it to be ignored by Google
- How to audit hreflang implementation across large international sites
- When separate country-code domains (ccTLDs) are more appropriate than hreflang
What is Hreflang
Hreflang is an HTML attribute that specifies alternate versions of a page for different languages or regions. When implemented correctly, Google uses hreflang signals to serve the appropriate language/regional version of a page to users — French speakers see the French version; German users see the German version; US users see the US English version rather than the UK English version.
Hreflang is a hint, not a directive. Google treats it as a signal alongside other factors (user location, interface language, search history) to determine which URL to serve. It does not guarantee that the specified version is always shown, but correct implementation significantly improves international search relevance.
Hreflang affects which URL ranks for a given user's search query — it helps Google understand that two URLs contain equivalent content for different audiences rather than treating them as duplicate content. It does not improve a page's ranking position.
When to Use Hreflang
Use hreflang when you have the same content available in multiple languages or for multiple regions. The key distinction: language targeting (French for France vs French for Canada vs French for Belgium) versus country targeting (UK English vs US English vs Australian English).
Do not implement hreflang if you have only a single language and a single target market — there is nothing to differentiate. Do not implement it for minor content differences (changing currency symbols, phone number formats) that do not meaningfully change the user experience — a UK vs US English page with only currency differences may be better served with a single page and JavaScript-rendered currency conversion.
| Scenario | Hreflang Needed? |
|---|---|
| English site targeting only UK users | No |
| English site with separate US and UK versions (/en-us/ and /en-gb/) | Yes — regional differentiation |
| Site with English and French translations (/en/ and /fr/) | Yes — language differentiation |
| Site translated into 10 languages | Yes — essential for preventing duplicate content across languages |
| Single-page app that uses JavaScript to switch displayed language | No — different language content on different URLs is required for hreflang |
HTML Implementation
The most common hreflang implementation uses <link rel="alternate" hreflang="..."> tags in the <head> of each page. Every page must include hreflang tags for every language/regional variant including itself (the self-referencing tag) and the x-default tag.
<!-- On the English (UK) version of the page -->
<link rel="alternate" hreflang="en-gb"
href="https://www.example.com/en-gb/about/">
<link rel="alternate" hreflang="en-us"
href="https://www.example.com/en-us/about/">
<link rel="alternate" hreflang="fr"
href="https://www.example.com/fr/about/">
<link rel="alternate" hreflang="de"
href="https://www.example.com/de/about/">
<link rel="alternate" hreflang="x-default"
href="https://www.example.com/about/">The same complete set of hreflang tags must appear on every URL listed — including the French and German pages. This is the reciprocal confirmation requirement: a URL is only trusted as a valid hreflang target if it also links back to the source page using hreflang.
Language code format
Use ISO 639-1 two-letter language codes (en, fr, de, zh). For regional variants, combine with ISO 3166-1 country codes: en-gb, en-us, zh-hans (Simplified Chinese), zh-hant (Traditional Chinese). The language code is required; the region code is optional.
XML Sitemap Implementation
For large international sites, including hreflang in every page's HTML <head> is impractical — a 50,000-page site with 10 language variants means 500,000 pages each containing 10 hreflang tags. The XML sitemap method consolidates all hreflang annotations in a single file.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
<loc>https://www.example.com/en-gb/about/</loc>
<xhtml:link rel="alternate" hreflang="en-gb"
href="https://www.example.com/en-gb/about/"/>
<xhtml:link rel="alternate" hreflang="en-us"
href="https://www.example.com/en-us/about/"/>
<xhtml:link rel="alternate" hreflang="fr"
href="https://www.example.com/fr/about/"/>
<xhtml:link rel="alternate" hreflang="x-default"
href="https://www.example.com/about/"/>
</url>
<!-- Repeat for every URL in every language -->
</urlset>The sitemap must include every URL in every language variant — each appearing as a separate <url> entry with its full hreflang annotation set. The total number of <url> entries equals pages × language variants.
The x-default Tag
hreflang="x-default" specifies which URL to show users who do not match any of the defined language or regional targets. It serves as the fallback for unmatched locales and for users with no location signal (such as searches from VPNs or with location detection disabled).
Common x-default destinations:
- A language-selection homepage that lets users choose their preferred language/region
- The site's primary or highest-traffic language version (usually English)
- A neutral English version not specifically targeted to any country
x-default is not optional — sites with hreflang that omit x-default risk having Google select an arbitrary URL as the default, which may not be the intended user experience for unmatched locales.
Common Hreflang Errors
- Missing reciprocal tags. The most common error. If page A points to page B with hreflang, page B must also point back to page A. Google verifies reciprocal confirmation — one-way hreflang annotations are ignored.
- Non-canonical URLs in hreflang. hreflang must reference canonical URLs. If a URL has a canonical pointing to a different URL, use the canonical URL in hreflang — not the canonicalised one.
- Incorrect language codes. Invalid ISO 639-1 codes cause hreflang to be ignored. Common mistakes:
en-uk(should been-gb),zh-cn(should bezh-hansorzh-cn— both are accepted). - Using hreflang on noindex pages. Pages blocked by robots.txt or with noindex directives cannot be verified by Googlebot — hreflang annotations on or pointing to such pages are ignored.
- Missing self-referencing tag. Each page must include a hreflang tag pointing to itself. Omitting the self-reference is a configuration error that can cause unpredictable serving behaviour.
- Partial implementation. Adding hreflang to new pages but not updating existing pages in the cluster leaves the existing pages without reciprocal confirmation — the entire cluster becomes unreliable.
Auditing Hreflang at Scale
Manual verification of hreflang is only feasible for small sites. At scale, use automated tools:
- Google Search Console — International Targeting report. Shows hreflang errors Google has detected across your site. Categories: Return tags missing (reciprocal issue), No return tag, Invalid language code.
- Screaming Frog SEO Spider. Crawls hreflang tags and cross-references them across the full site to identify missing reciprocal tags, non-canonical URLs, and missing x-default.
- JetOctopus / Sitebulb. Enterprise-level log file and crawl analysis with dedicated hreflang validation reports for large international sites.
Hreflang errors do not cause ranking drops — they cause wrong-version serving
A hreflang implementation error will not directly lower your rankings. The consequence is incorrect URL serving — German users see the English version; UK users see the US English version. This harms conversion rates and user experience rather than rankings directly. Treat hreflang as a UX and traffic quality issue, not a ranking issue.
Authentic Sources
When to use hreflang, separate URLs vs language parameters.
Using hreflang tags, sitemaps, and geotargeting correctly.
Official documentation of hreflang implementation errors and how to fix them.