hreflang is an HTML link attribute that tells search engines which language and region a page targets. It enables Google to serve the correct locale variant to users in different countries.

How do I implement hreflang correctly?

Add a tag for every locale variant — including a self-referential tag — and an x-default fallback. All pages in the cluster must cross-reference each other.

What is the difference between hreflang and the lang HTML attribute?

The lang attribute tells the browser what language the current page is in, affecting rendering and screen readers. hreflang is a search-engine signal pointing to alternate language or region versions across URLs.

What happens if hreflang tags are inconsistent?

Google ignores the entire cluster when reciprocal links are missing or URLs return errors. A page declaring hreflang to a target must have that target declare hreflang back — otherwise the signal is disregarded.

Glossary

hreflang

The multilingual SEO attribute

By Buğra SözeriPublished May 14, 2026Updated May 31, 2026

hreflang is an HTML attribute (used in <link> tags and HTTP headers) that tells search engines which language and optionally which regional variant a page targets. Required for sites with multiple language versions; ignored by browsers but essential for SEO.

Value format: a BCP 47 language tag — en, tr, en-GB, en-US, x-default (the fallback for unmatched locales). Each language version of a page should include hreflang tags pointing to every other version, including itself.

Example for a Turkish + English page pair:

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

Without hreflang, Google may surface the wrong language version to users in a given region. With it, the right version goes to the right reader. Convertitive’s i18n roadmap (Wave 4) involves wiring hreflang across every translated page.

The three biggest hreflang implementation mistakes: first, asymmetric references — page A links to page B with hreflang, but page B doesn’t link back. Google requires bidirectional declarations and will silently ignore one-sided tags. Second, pointing hreflang at non-canonical URLs (redirects, parameter variants, trailing-slash mismatches), which Google treats as broken. Third, using a region code (en-MX) without that locale’s page actually existing — the “return tag” on the target side must match exactly. Search Console’s International Targeting report flags these explicitly; check it after every locale rollout.

Region vs language — and the x-default fallback: hreflang supports language alone (en), language + region (en-GB, en-US), and a special x-default value for the URL to serve when no other locale matches. Use x-default for the version a user from an unmapped country (say, Brazil with no pt-BR translation) should see — typically your primary English version. Do not confuse hreflang with the deprecated “international targeting” setting in Search Console (deprecated 2022) or with lang attribute on the <html> element, which informs accessibility and language detection but not search routing. See Convertitive’s methodology overview for how the translation registry generates these tags. Reference: Google Search Central — Localized versions.

Worked example: cluster of three locales

A site with English, Turkish, and Spanish versions of the same article needs every page in the cluster to declare all three alternates plus an x-default. For the English page /en/article, the head includes four <link rel="alternate"> tags: hreflang="en" pointing at itself, hreflang="tr" at /tr/article, hreflang="es" at /es/articulo, and hreflang="x-default" at the English URL. The Turkish and Spanish pages mirror the same set. Total tags across the cluster: 12 (3 pages × 4 tags each). Any missing reciprocal is an “orphan” in Search Console and Google falls back to its own language detection — usually badly.

Why it matters for revenue, not just SEO

For e-commerce and SaaS pricing pages, hreflang governs whether a visitor in Germany sees EUR pricing or USD pricing in the SERP snippet. A 15-20% conversion-rate uplift after fixing hreflang is common in case studies, because the wrong-locale page bounces before the conversion event. The fix is structural: generate hreflang from a single source-of-truth translation registry (see Convertitive’s src/lib/i18n/translations.ts) rather than hand-writing tags per page, which is where 90% of asymmetry bugs originate. For canonical specification details see the IETF BCP 47 language-tag spec that hreflang values must conform to.

Frequently asked questions

What is hreflang?: hreflang is an HTML link attribute that tells search engines which language and region a page targets. It enables Google to serve the correct locale variant to users in different countries.
How do I implement hreflang correctly?: Add a <link rel="alternate" hreflang="en-US" href="https://example.com/en-us/page/"> tag for every locale variant — including a self-referential tag — and an x-default fallback. All pages in the cluster must cross-reference each other.
What is the difference between hreflang and the lang HTML attribute?: The lang attribute tells the browser what language the current page is in, affecting rendering and screen readers. hreflang is a search-engine signal pointing to alternate language or region versions across URLs.
What happens if hreflang tags are inconsistent?: Google ignores the entire cluster when reciprocal links are missing or URLs return errors. A page declaring hreflang to a target must have that target declare hreflang back — otherwise the signal is disregarded.

Published May 14, 2026 · Last reviewed May 31, 2026

hreflang

Worked example: cluster of three locales

Why it matters for revenue, not just SEO

Frequently asked questions

Related