When is hreflang worth the complexity vs just one page?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 4
When you have more than one version of a page for different languages or regions; searchers landing on the wrong one is the clearest sign, but you can also set it up from the start when you launch equivalent versions. Hreflang does not make a page rank; it tells Google which of your existing versions to show to which audience. If you have one page in one language for everyone, there is nothing for hreflang to choose between, and adding versions just to use it creates work without a reason.
Deciding
| Your situation | Hreflang? |
|---|---|
| One language, one market, one page per topic | No |
| Translated versions of your pages, such as English and German | Yes, so each language reaches its own speakers |
| The same language for several countries, with real differences: prices, currency, delivery, legal terms | Yes, with a version per country that differs |
| The same language for several countries, with identical content | No; one page serves them all |
| A language selector or a global page for visitors whose language you do not serve | Yes, marked as x-default |
What it takes to maintain
Google’s documentation on localized versions sets out the requirements. Each version lists itself and every other version, with the right language or language-and-region code, and the references have to go both ways. Every time you add, remove or move a version, every other version in the group has to be updated. On a site with a handful of versions per page this is manageable; on a large catalog in many markets it needs to be generated from your system, in the page head, the HTTP headers or the sitemap, not maintained by hand.
Before adding versions to justify hreflang
Ask whether a separate version would serve its audience better than the one page you have. A translation for a language you sell in, yes. A copy of an English page with “colour” instead of “color” for another English-speaking market, probably not: Google’s documentation notes that localized versions are only treated as duplicates when the main content stays untranslated, and near-identical same-language pages add maintenance without giving anyone something new. For regions that share a language, the separate-pages question is answered in whether similar-language regions get separate pages or one. Add hreflang when you have versions to route between, and not before.
Add a comment