Home›Expertise›SEO›Hreflang deep dive

Hreflang deep dive

📖 9 min readUpdated 2026-04-19

Hreflang implementation is where most international SEO goes wrong. The rules are finicky, the errors are silent (Google just ignores broken hreflang without telling you), and the stakes are high. This page is the detailed rulebook: the 3 implementation methods, 8 core rules, common patterns, validation workflow, and a debugging checklist for when Google ignores your hreflang (which it silently does more often than you'd think).

The core rules at a glance

The three implementation methods

1. HTML head tags

Most common. Add to <head> of every version of a page:

<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="fr-fr" href="https://example.com/fr/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/" />

2. HTTP headers

For non-HTML files (PDFs, images):

Link: <https://example.com/doc.pdf>; rel="alternate"; hreflang="en-us",
      <https://example.com/uk/doc.pdf>; rel="alternate"; hreflang="en-gb"

3. XML sitemap

Best for large sites:

<url>
  <loc>https://example.com/us/page</loc>
  <xhtml:link rel="alternate" hreflang="en-us" href="https://example.com/us/page"/>
  <xhtml:link rel="alternate" hreflang="en-gb" href="https://example.com/uk/page"/>
  <xhtml:link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/page"/>
</url>

The core rules

1. Every version must link to every other version (including itself)

If page A links to pages B and C, then B must also link to A and C, and C must link to A and B. Non-reciprocation = Google ignores silently.

2. Self-reference is required

Page at URL X must include hreflang=".." href="X" in its hreflang cluster.

3. Use correct language + region codes

Language: ISO 639-1 (en, fr, de, es, it, pt, zh, ja, ko...)
Region: ISO 3166-1 alpha-2 (US, GB, DE, FR, ES, MX, BR...)
Format: language-REGION (e.g., en-US, en-GB)
Case: Google is lenient; en-us also works

4. Common code mistakes

❌ en-uk, invalid. Use en-gb.
❌ zh-cn, valid but zh-hans (simplified Chinese) is more modern.
❌ sp-es. "sp" isn't a language code. Use es-es.

5, x-default

Specifies the fallback version for users not matching any specific hreflang. Usually your default (US English).

<link rel="alternate" hreflang="x-default" href="https://example.com/" />

6. Canonical + hreflang

Each version should canonical to itself (not to another version). If your French page canonicals to your English page, you're telling Google "the English is the master", hreflang is overridden.

7. Noindex + hreflang

Never both on the same page. Conflicting signals.

8, hreflang only points to indexable 200-OK URLs

If a hreflang target is 404, 301, noindexed, or blocked. Google drops the cluster.

Common patterns

Same language, different regions

en-US → https://example.com/us/
en-GB → https://example.com/uk/
en-CA → https://example.com/ca/
en-AU → https://example.com/au/
x-default → https://example.com/us/

Language-only (no region)

If you don't differentiate by country:

en → https://example.com/
fr → https://example.com/fr/
de → https://example.com/de/

Be careful: "en" means "any English-speaking user." If you have US-specific content (prices in USD, US shipping), you want en-US not en.

Multiple languages per country

fr-CH → https://example.com/ch/fr/
de-CH → https://example.com/ch/de/
it-CH → https://example.com/ch/it/

Validation

Merkle hreflang tool (technicalseo.com/tools/hreflang/), checks reciprocation for specific URLs
GSC → Legacy tools → International Targeting, shows errors (though this report has been gradually removed)
Screaming Frog (Pro), crawls + audits hreflang
Sitebulb, excellent hreflang visualizations

Debugging checklist

Is every URL in a hreflang cluster 200 OK and indexable?
Does every URL reference itself?
Does every URL reference every other URL in the cluster?
Are language/region codes valid?
Is canonical self-referential (not pointing elsewhere)?
Is x-default included?
If using HTML head: is the tag actually in <head> (not in body)?
If using sitemap: is the sitemap itself valid + submitted?

When Google ignores your hreflang

Often silent. Search your pages in the markets they're supposed to serve. If the wrong version is ranking, hreflang is probably broken. Run through the debugging checklist.

What to do with this

Run one of your multi-market pages through Merkle's hreflang tool. Every error surfaced is a ranking leak. Fix reciprocation first (the most common issue), then self-references, then canonical conflicts.

Next: translation vs localization, why machine translation kills international SEO.