Hreflang tags

Hreflang tags tell search engines which language or region version of your content to show in which country. They're easy to understand in theory, legendary for being broken in practice. Getting hreflang right on a multi-region site can mean the difference between your US visitors seeing US dollar prices and seeing the wrong currency. This page walks through what hreflang does, the three ways to implement it, the common mistakes that silently break it, and when you actually need it.

The mental model

Hreflang is about showing the right version to the right user. Without it, Google guesses based on a handful of signals (domain, content language, user location) and gets it wrong regularly. With it, you're telling Google directly: "I have a UK English version, a US English version, a French version. Send UK users to UK, US users to US, French users to French."

Think of it as a switchboard. Every hreflang-declared URL knows about every sibling.

A quick example

You have three versions of a product page:

• example.com/us/product. US English
• example.com/uk/product. UK English
• example.com/fr/product. French for France

Hreflang lets you tell Google: show the US version to US searchers, UK to UK, French to French. Without hreflang, Google often shows the wrong one.

The three implementation methods

HTML head tags (most common)

<link rel="alternate" hreflang="en-us" href="https://example.com/us/product" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/product" />
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/product" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/product" />

HTTP headers (for non-HTML files)

Link: <https://example.com/us/product>; rel="alternate"; hreflang="en-us"

XML sitemap

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

Valid language and region codes

• Language only. en, fr, es, de (ISO 639-1)
• Language + region. en-us, en-gb, en-au, fr-ca (ISO 3166-1 alpha-2 for region)
• Special case. x-default for users whose locale doesn't match any specific hreflang

The x-default fallback

The x-default tag specifies a fallback for users whose language and region don't match any of your specific hreflang values. Usually your US English or generic international-English version. Include it on every page.

Common mistakes that silently break hreflang

The implementation nightmare

For a site with 10 languages times 20 countries, that's 200 page variations. Every page needs 200 hreflang references to be complete. Managing that in head tags becomes unmaintainable fast.

For large multi-region sites, the XML sitemap approach is the sanity-preserving choice. You can generate hreflang in a programmatic, testable way, and you only manage one file per locale set.

Testing hreflang

• Google Search Console International Targeting report. Shows hreflang errors for your site.
• Merkle hreflang tool. Checks reciprocation for specific URLs.
• Screaming Frog Pro. Has an hreflang audit feature.
• Sitebulb. Excellent hreflang visualization.

When not to use hreflang

• You only have one language and one region. Skip it.
• Your "translated" pages are just minor copy variations of the same content. Consider consolidating instead.
• Your content strategy targets one global audience in one language. Keep it simple.

What to do with this

If you operate in multiple countries and don't have hreflang set up, this is a high-ROI project. US visitors buying from your UK site in pounds is a conversion disaster you can fix with a weekend of work. If you do have hreflang, audit it with Merkle's tool for reciprocation errors. Those are the quiet bugs that keep your implementation at 70% effectiveness.

Next: page speed, the technical lever that pays off in rankings and conversions simultaneously.

What they do

Suppose you have three versions of a page:

• example.com/us/product. US English
• example.com/uk/product. UK English
• example.com/fr/product. French for France

Hreflang tells Google: show the US version to users in the US, UK version to UK users, French version to French users. Without hreflang, Google guesses (often wrongly).

The syntax

Each page references every version (including itself). Three implementations, pick one:

1. HTML head tags (most common)

<link rel="alternate" hreflang="en-us" href="https://example.com/us/product" />
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/product" />
<link rel="alternate" hreflang="fr-fr" href="https://example.com/fr/product" />
<link rel="alternate" hreflang="x-default" href="https://example.com/us/product" />

2. HTTP headers (for non-HTML files)

Link: <https://example.com/us/product>; rel="alternate"; hreflang="en-us"

3. XML sitemap

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

Valid language/region codes

• Language only: en, fr, es, de (ISO 639-1)
• Language-region: en-us, en-gb, en-au, fr-ca (ISO 3166-1 alpha-2 for region)
• Special: x-default (the fallback for unmatched users)

x-default

The x-default tag specifies a fallback version for users whose language/region doesn't match any specific hreflang. Usually your US English or international-English version.

Common mistakes

• Non-reciprocal references. If page A links to page B with hreflang, page B must link back to A. One-way hreflang is silently ignored.
• Missing self-reference. Every page must include itself in its hreflang set.
• Wrong region codes. "en-uk" is invalid, use "en-gb". "es-mx" is valid (Mexico); "es-es" is Spain.
• Using language tag for region intent. hreflang="en" means "any English", you can't say "English except UK."
• Canonical conflict. If your French page canonicals to the English page, your hreflang is undermined.
• Noindex on a language version. Again, conflicts.

The implementation nightmare

For a site with 10 languages × 20 countries = 200 page variations, every page needs 200 hreflang references. This gets unmaintainable fast in head tags. For large sites, XML sitemap hreflang is the sanity-preserving choice.

Testing

• Google Search Console → International Targeting report, shows errors
• Merkle hreflang tool, checks reciprocation for specific URLs
• Screaming Frog, has an hreflang audit in the Pro version
• Sitebulb, excellent hreflang visualization

When NOT to use hreflang

• If you only have one language/region, you don't need hreflang
• If your "translated" pages are just minor copy variations on the same content, consider if they need to exist at all
• If your content strategy targets one global audience in English, keep it simple