Growth Marketing Glossary

Hreflang

href·langnoun (attribute)

Each version must name all the others — the reciprocity rule most international sites quietly fail.

en-usen-gbde-dex-defaulteach version names all the otherstelling search which language version belongs to whom
Schematic — versions naming each other, plus the fallback
Term
Hreflang
Since
Google, December 2011; x-default 2013
Hard rule
Annotations must be reciprocal
Without it
Wrong-country pages cannibalize

Forms & parts of speech

hreflang · noun
The language-version annotation.
"The Mexico launch flatlined because hreflang was one-way - Spain's pages kept winning Mexican queries."

Definition in plain terms

Hreflang is the annotation — in the HTML head, HTTP headers, or the sitemap — telling search engines which language or regional version of a page should serve which users: en-us for American English, de-de for Germany, es-mx versus es-es for the two Spanishes that read each other's prices wrong. Google introduced it in December 2011, added the x-default fallback in 2013, and INTERNATIONAL-SEO has revolved around it since — because without it, search picks a version by its own guesses, and the guesses cannibalize.

The mechanics

The grammar is small and strict: each annotation pairs a language (ISO 639-1) with an optional region (ISO 3166-1) — language-only targets a tongue everywhere (es), language-region targets a market (es-mx) — and x-default names the version for everyone unmatched, usually the country selector or the global English page. The rule that decides whether any of it works: reciprocity. Every version must annotate every other version INCLUDING itself; if page A names B but B doesn't name A back, the pair is invalid and search ignores it — which is why hreflang fails silently and at scale (industry crawls routinely find most implementations broken: missing return links, region codes that don't exist like 'en-uk' for 'en-gb', annotations pointing at redirected or non-CANONICAL-TAG URLs). The placement choice is operational: head tags for small sites, XML sitemaps for large ones (one file to govern instead of n-squared edits across templates), HTTP headers for PDFs. And the relationship with canonicals is where the two systems collide: hreflang must point at canonical URLs, each language version self-canonicalizes — cross-language canonicals tell Google the versions are duplicates, which un-does the entire annotation. The diagnostic loop: wrong-country impressions in Search Console by market, a crawl-based reciprocity audit, and the fix usually landing in the sitemap generator, not the pages.

When it matters

Hreflang matters the moment a site serves two markets sharing a language — UK and US, Spain and Mexico, Germany and Austria — where cannibalization is invisible to anyone reading 'we rank' without asking WHICH version ranks. It matters at migration time (annotations pointing through redirects rot), at scale (sitemap-managed or unmanageable), and not at all for single-language single-market sites adding it from cargo cult. The discipline is reciprocity audited by crawler rather than asserted, x-default chosen deliberately, canonicals kept self-referential, and Search Console's per-market reality read as the scoreboard.

Worked example. A SaaS company runs en-us, en-gb, de-de, and fr-fr storefronts and the German country manager keeps escalating the same mystery - German queries returning the US pricing page, trials signing up on the wrong currency and churning at twice the rate. The crawl audit finds textbook silent failure: the templates emit hreflang on the marketing pages but the pricing pages annotate one-way (US names DE; DE's template predates the tag and names nobody back), two region codes are invented (en-uk, and a de-at that points at a 404), and the CMS canonicalizes all pricing pages to the US version - the annotation and the canonical contradicting each other, with the canonical winning. The rebuild moves hreflang generation into the sitemap pipeline (one generator, every version, reciprocal by construction, x-default on the language selector), fixes self-canonicals, and adds a reciprocity check to CI. Six weeks later Search Console's market report shows German queries serving German pages at 94% (from 61%), and wrong-currency trial churn drops by a third. Nothing about the pages changed - only who got shown which one.
Failure modes to watch. One-way annotations invalidating silently - the reciprocity rule unaudited; invented region codes (en-uk) and annotations through redirects; cross-language canonicals contradicting the hreflang and winning; head-tag sprawl where the sitemap should govern; and 'we rank internationally' read without asking which version ranks where.

Synonyms & antonyms

Synonyms

hreflangrel-alternate-hreflanglanguage annotation

Antonyms

canonical tag (the duplicate signal)geo-IP redirects (the blunt cousin)

Origin & history

Hreflang arrived as Google's December 2011 rel-alternate-hreflang annotation for multilingual content, gained the x-default fallback in April 2013 (Google and Yandex jointly), and earned its reputation as international SEO's most-broken tag - a strict reciprocal grammar deployed mostly by templates that never learned the grammar.

Etymology: source.

Usage trends

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Common questions

What is hreflang?
The annotation — head tags, HTTP headers, or sitemap — telling search engines which language or regional version of a page serves which users, introduced by Google in December 2011.
Why do hreflang implementations fail?
Mostly the reciprocity rule — every version must name every other version back, or the pair is silently ignored; invented region codes, redirected URLs, and contradictory canonicals do the rest.
What is x-default?
The fallback annotation (2013) naming the version for users no other annotation matches — typically the country selector or global English page; choose it deliberately rather than letting search guess.

Related tools & calculators

Resources & people to follow

Curated, non-competitor resources verified per term.

Related training

Disciplines

Areas of marketing where hreflang is a core concern:

Sources

  1. trendsGoogle Trends — "hreflang"