What Is an Hreflang Tag? Multilingual SEO Explained
A client running English, German, and French versions of an e-commerce site once asked me why German users kept landing on English product pages — and converting at roughly half the rate. The site had hreflang tags. Every single one of them was being ignored, because the German pages didn't link back to the English ones, and hreflang without reciprocal links is dead markup. Nobody had noticed for over a year, because hreflang fails without any visible error.
What is an hreflang tag? It's an HTML attribute (or HTTP header, or sitemap annotation) that tells search engines which language — and optionally which country — each version of a page targets, so they can serve the right variant to the right searcher. If you publish the same page in English and Spanish, hreflang is how Google knows to show the Spanish URL in Mexico and the English one in Canada.
What is an hreflang tag written like?
The most common implementation is a set of <link> elements in the <head> of every variant:
<link rel="alternate" hreflang="en-gb" href="https://example.com/uk/" /><link rel="alternate" hreflang="de" href="https://example.com/de/" /><link rel="alternate" hreflang="x-default" href="https://example.com/" />
The value combines a language code (ISO 639-1) with an optional region code (ISO 3166-1 Alpha 2): de means German speakers anywhere; de-at means German speakers in Austria specifically. The special value x-default marks the fallback page for users matching no listed variant — typically your language selector or your primary market's version.
For large sites, the same annotations can live in the XML sitemap instead, which keeps the HTML lighter and centralizes maintenance — a real advantage when 40 country variants would otherwise mean 40 link elements on every page.
The two rules that break everyone
Hreflang has exactly two non-negotiable requirements, and between them they account for most failed implementations I've audited:
- Return tags. References must be reciprocal. If page A lists page B as its German alternate, page B must list page A back. One-directional references get ignored entirely — this is the silent killer from my opening story, and Search Console's international targeting reporting has historically been too quiet about it.
- Self-reference. Every page must include an hreflang entry pointing to itself. The English page lists the German and French alternates and its own URL with
hreflang="en". Omit it and the whole cluster becomes unreliable.
Add the operational rule that every referenced URL must be the real, indexable, canonical version — pointing hreflang at a URL that redirects, 404s, or canonicalizes elsewhere breaks the chain. If a variant returns anything but a clean 200 status, its annotations do nothing.
Mistakes beyond the big two
A tour of the errors that show up in real hreflang audits:
- Invented codes.
en-ukis not a thing — the United Kingdom isgb.en-euisn't valid either; there's no region code for "Europe." Wrong codes are silently discarded. - Language and region reversed.
gb-eninstead ofen-gb. Language always comes first. - Region-only targeting. You can't write
hreflang="mx"; a language is mandatory. For Mexico, it'ses-mx. - Hreflang pointing at noindexed pages. If the German variant carries a noindex, listing it as an alternate is a contradiction Google resolves by ignoring you. Hreflang assumes all variants are indexable — which makes indexability a prerequisite, not a footnote.
- Assuming hreflang consolidates rankings. It doesn't. Hreflang is a swap instruction — it helps Google pick which variant to display. It won't make your Spanish page rank because your English page does; each variant still earns its own authority.
Does your site even need it?
A question worth asking before writing a single tag. You need hreflang when you have multiple pages with the same purpose in different languages, or same-language pages targeting different countries — the classic case being en-US, en-GB, and en-AU variants with different prices and spelling, where hreflang also quietly prevents these near-duplicates from competing with each other. You don't need it for a single-language site, for pages translated only partially, or for one global English site serving everyone. Hreflang solves a targeting problem; if you don't have the problem, the markup is pure maintenance overhead.
Also worth knowing: Google detects page language from content on its own, without hreflang. What it can't reliably infer is which of several similar variants belongs to which audience — especially same-language country versions, which look nearly identical to an algorithm. That's the specific ambiguity hreflang resolves, and it's why a French-only site gains nothing from the markup while a three-country English site gains a lot.
Keeping it verified over time
Hreflang decays. A developer removes a link element in a template refactor; a market launch adds Italian pages nobody annotates; a URL migration breaks half the return tags. Because nothing visibly errors, decay accumulates until someone wonders why Dutch users see the German site. Spot checks don't scale across thousands of URL pairs — validating reciprocity is exactly the kind of tedious cross-referencing that a site-wide technical audit should do for you on a schedule, alongside the status-code and canonical checks that hreflang depends on. For international sites, I treat hreflang validation as a monthly automated job, not a launch-day checkbox.
Frequently Asked Questions
Is hreflang a ranking factor?
No. Hreflang doesn't make pages rank higher — it helps Google choose which existing variant to display for a given user's language and location. Its indirect benefits are real, though: users land on the right version, engagement improves, and same-language country variants stop competing with each other as duplicates.
Where should hreflang tags be placed?
You have three valid options: link elements in the HTML head, HTTP headers (the only option for PDFs and other non-HTML files), or annotations in your XML sitemap. Use exactly one method consistently — mixing methods across pages invites conflicting signals. Sitemap annotation tends to scale best for sites with many country variants.
What does x-default mean in hreflang?
It designates the fallback URL for users whose language and region match none of your declared variants — for example, a Japanese user on a site offering only English, German, and French. It typically points to your language selector page or your primary market's version, and including it is strongly recommended.
Why is Google ignoring my hreflang tags?
The usual suspects, in order: missing return tags (variants must reference each other reciprocally), missing self-references, invalid language-region codes like en-uk, or annotations pointing at URLs that redirect, 404, or carry noindex. Since hreflang fails silently, an automated crawl that validates all pairs is the practical way to find the break.
Try WebsiteChecker.Tech Free
Run a free technical SEO audit on any website. Get a client-ready report in minutes.
Start Free Scan