hreflang, and whether you actually need it
You have or are considering multiple language or region versions and want to know how to signal them correctly.
Short answer
hreflang tells search engines that several URLs are the same content for different languages or regions, so the right version is shown to the right audience. It does not affect ranking and it does not consolidate signals like a canonical. It is only needed when you genuinely have multiple versions of the same content, which is fewer sites than implement it.
What it is for
Not ranking. Serving. If you have an English page and a Spanish page covering the same thing, hreflang tells the engine which to show to which searcher. Without it, the engine guesses, and it usually guesses from the language of the content, which is often correct anyway.
The reciprocity rule that breaks most implementations
Every version must reference every other version, including itself. If the English page lists Spanish but the Spanish page does not list English, the pair is invalid and is often ignored entirely. This is the single most common failure, and it happens as soon as one page is added without updating the others.
Language and region codes
A language code alone is valid and usually sufficient. A region without a language is not valid. Getting this wrong produces a tag that looks reasonable and is silently discarded, which is worse than not having one because it feels like the job is done.
x-default
The fallback for searchers who match none of your versions. Worth setting explicitly to whichever version is your genuine default, because otherwise the engine chooses and you have no say.
Where to put it
Response headers, HTML head, or the sitemap. The sitemap is usually easiest to maintain at scale because the reciprocity is generated rather than hand-written, and hand-written reciprocity across dozens of pages is where implementations rot.
Who actually needs it
Sites with genuinely parallel content across languages or regions. Not sites with one language. Not sites whose regional pages differ substantially, because those are different pages and should be treated as such. Not sites with three translated pages out of two hundred.
The cost of getting it wrong
A broken implementation is generally ignored rather than penalised, so the real cost is the maintenance and the false confidence. If you are not going to keep it correct as pages are added, not having it is a defensible choice.
Questions
- Do I need hreflang for UK and US English?
- Only if the pages genuinely differ in ways that matter, such as pricing, currency or legal terms. Two nearly identical pages split by region often create a duplicate problem you did not have.
- Does hreflang help me rank in a new country?
- No. It affects which existing version is served, not whether you rank at all. Ranking in a new market comes from relevance and links in that market.
- What if I get it wrong?
- Usually the tags are ignored rather than punished. The practical cost is the work, plus the belief that a solved problem is solved when it is not.
Measured, not asserted
ihatepdf.cv reached 100,542 users across international traffic with no hreflang at all, because it had one version of each page. The demand it saw was global and the content was single-language; adding parallel versions would have multiplied the maintenance without addressing what was actually limiting the site.
Free tool for this: Crawler View. No account, nothing uploaded.
Where this goes deeper
Every number on this page comes from one complete dataset: one product taken from zero to 100K+ users on search alone, with nothing spent on advertising. The full argument is Chapter 10 of the book. Five chapters are free to read.