Hreflang annotations connect equivalent pages intended for different languages or regions. They help a search engine understand which version may suit a searcher, such as Australian English compared with British English. Hreflang is useful for genuine alternatives; it does not translate content or create a local business presence.
Match versions to real audiences
Google supports language and regional annotations in page markup, headers or sitemaps. They describe relationships between versions rather than guaranteeing that a chosen page will rank in a country. A useful implementation starts with the audience differences: language, currency, service availability and local terms. Canonical URL decisions must also make sense for those versions. Regional labels alone cannot turn otherwise unsuitable content into a useful local result, and separate suburban pages do not need country-level language annotations between them.
Check each alternate cluster
Make an inventory pairing every source page with its equivalent alternatives. Check that the URLs are fully qualified, accessible and intended for indexing. Validate supported language and optional region codes, self-references and reciprocal references. Avoid sending every article to a foreign homepage instead of its matching article. Review canonical annotations for contradictions, then sample more than one content template. If a version is removed, update the whole affected cluster rather than leaving references to a redirected or missing destination.
Keep regional alternatives paired at the content level during publishing. When an editor creates or removes one translated article, the related versions need review so the cluster does not drift out of agreement.
Localise substance before labels
Imagine a Perth software supplier serves Australia and New Zealand with separate pricing pages. Equivalent versions may warrant regional annotations when they reflect real currency, tax wording or service differences. A reader should still be able to choose another version without being forced through an unchangeable location redirect. For a business serving only Perth in English, a straightforward Australian page may be enough. Measure whether searchers reach an appropriate version and whether that page answers their needs, not just whether the tags pass validation.
A technical SEO review can validate the relationships between regional page versions.
Common questions
Does hreflang identify a page's language by itself?
Google determines language from content. Hreflang describes alternate versions, while the HTML language attribute also serves accessibility and browser needs.
Is hreflang a ranking boost?
It is a targeting and relationship annotation, not a promise of higher positions. The alternate pages still need useful content and sound technical access.
Terms in this guide
- Canonical URL — The preferred URL for a page when identical or substantially similar content is accessible through multiple addresses. A canonical link communicates a preference rather than forcing a redirect.
- Sitemap — A structured list of relevant site URLs. XML sitemaps support discovery by search engines; an HTML sitemap helps people navigate the site.
- Indexability — Whether a page is eligible to enter a search engine’s index. A crawlable page may still be excluded, for example because of a noindex directive or the engine’s own selection.
- Local SEO — Improving a business’s search presence for relevant local demand through accurate business information, useful local content, a sound website and a credible reputation.
Related SEO guides
Apply this to your website
Explore Technical SEO, SEO Audits for help planning and implementing the relevant changes, or discuss your website with Refined IT.