Hreflang identifies alternative versions of content intended for different languages or regions. It helps supporting search engines understand that relationship when selecting a suitable result.
It does not translate the page or create a localisation strategy. The underlying versions still need accurate content and a useful experience for their intended audiences.
When does a website need it?
Investigate hreflang when equivalent pages exist for different languages or regional audiences. The need follows the actual content structure.
A single English-language website does not automatically require international markup merely because visitors can arrive from overseas.
Language versus region
Language and region describe different dimensions. English content for two markets may share a language while differing in services, currency or availability.
Use appropriate supported codes and verify the implementation against current documentation. Avoid assuming ordinary country abbreviations are always the correct values.
What counts as an equivalent page?
Alternatives should represent corresponding content. A product page should connect with the relevant product alternative, rather than every language version pointing to a homepage.
This mapping requires editorial understanding. A translated navigation label does not establish that the destination offers an equivalent answer.
How does canonicalisation fit in?
Canonical and hreflang signals serve different purposes and should be coherent. One addresses representative URLs; the other describes language or regional alternatives.
An international implementation should be reviewed as a whole. Conflicting signals can make the intended structure harder to understand.
What should be tested?
Check the complete set of alternatives, their accessibility and the relationships declared between them. Include self-references and reciprocal relationships where required by the implementation.
Test more than one template. Products, articles and service pages may have different coverage across markets.
How should a business maintain it?
Connect localisation publishing with the generation of alternate relationships. When a page is added, removed or moved, review the corresponding alternatives.
Assign ownership for incomplete translations and market-specific differences. A technically tidy declaration cannot repair content that sends the reader to an unsuitable offer.
Further reading
For reference, see the supporting documentation. Explore related explanations of Canonical URL, Technical SEO, XML sitemap.
A practical example
Illustrative example: a company maintains corresponding service pages for English and French readers. It maps each page to its relevant alternative and checks that both remain accessible. A service unavailable in one market is handled deliberately rather than linked to an unrelated page.
Why it matters
Hreflang supports a coherent international website. Accurate page mapping and maintained local content are more valuable than adding language tags indiscriminately.
