How hreflang actually works, the four mistakes that break it on most sites, and a safe implementation sequence for multi-market websites.
Hreflang is a signal that tells search engines which language and country version of a page to show each user. It does not improve rankings. It routes the rankings you already have to the right audience, which is why getting it wrong is so expensive: the authority is real, it is just being spent on the wrong version of the page in the wrong market.
It is also the most commonly broken tag we find in audits of multi-market sites. Here is how it works, where it goes wrong, and the order to implement it in.
What does hreflang actually do?
Each hreflang annotation pairs a URL with a language, and optionally a region: en-gb for English in the United Kingdom, es-es for Spanish in Spain, en for English anywhere. When Google has indexed several versions of a page, the annotations tell it which one belongs in front of which searcher. Without them, Google guesses, and its guesses across similar-language markets are poor. UK pages outranking your Australian pages in Sydney is the classic symptom.
The four mistakes that break hreflang on most sites
- Missing return links. Hreflang only counts when it is reciprocal. If the UK page points to the Australian page but the Australian page does not point back, the pair is ignored. This single error accounts for most broken implementations.
- Annotations pointing at redirected or non-canonical URLs. Every hreflang target must be the final, canonical, indexable URL. Pointing at a redirect quietly voids the annotation.
- Wrong codes. The language comes first and uses ISO 639-1, the region second using ISO 3166-1. en-uk is invalid: the United Kingdom is gb. Invalid codes fail silently.
- No x-default. The x-default annotation catches searchers who match none of your specified markets. Without it, an arbitrary version competes for everyone else.
Where should hreflang live?
Three valid homes: the page head, the HTTP header, or the XML sitemap. Pick one and use it consistently, because mixed implementations are hard to debug. For sites with many markets, the sitemap is usually the pragmatic choice: it keeps page weight down and puts the whole map in one auditable file. For a handful of markets, head tags are simpler to deploy and inspect.
A safe implementation sequence
- First, map the cluster. List every page that exists in more than one market version and the canonical URL of each version. Most hreflang projects fail at this inventory stage, not in the markup.
- Second, generate annotations from the map, not by hand. Every page in a cluster carries the full set: itself, every sibling, and x-default. Hand-written tags drift out of sync the first time a URL changes.
- Third, validate before deploy. Check reciprocity, response codes and canonical alignment for every pair.
- Fourth, watch Search Console per market. The result you are looking for is each country's impressions consolidating onto its own version. That shift, not a rankings jump, is what success looks like.
Frequently asked questions
Does hreflang improve rankings?
No. It assigns the right version of a page to the right market. The commercial gain comes from users landing on the version built for them: right currency, right proof, right language. Conversion improves even where rankings do not move.
Do I need hreflang for UK and US English?
If both versions exist, yes. Same-language markets are exactly where Google most often shows the wrong version, because the content looks interchangeable to an algorithm and is not interchangeable to a buyer.
Can hreflang fix duplicate content between country sites?
It is the correct tool for legitimate market variants of the same page. Paired with consistent canonicals inside each market, it tells Google the duplication is deliberate and how to route it.
Should hreflang decisions come before or after market strategy?
After. Hreflang implements a market structure; it cannot rescue a wrong one. The strategic decisions, which markets, which languages, which URL structure, are covered in our international SEO guide, and the language-level detail for Spain in our multilingual SEO for Spain guide. For the technical foundations underneath all of this, see our technical SEO service.
