TL;DR

Hreflang tells Google 'this page is for French speakers, that one is for Spanish speakers in Mexico.' Without it, Google may show the wrong language version to international visitors, hurting both UX and rankings.

Key Points

✓

Hreflang is relevant for sites with content in multiple languages or region-specific versions of the same language (e.g., en-US vs en-GB)

✓

Hreflang must be bidirectional — every page must link to all its alternate versions, and each alternate must link back

✓

Implementation can be done via HTML `<link>` tags, HTTP headers, or XML sitemap

✓

Hreflang does not affect ranking strength — it only affects which version Google serves to different users

When to Implement Hreflang

Hreflang is necessary when your site serves similar content in multiple languages or regional variants^[1]. A global SaaS company with US English, UK English, French, and German versions of their site needs hreflang to prevent French users from being served the German page. Without it, Google consolidates the pages as duplicate content and may serve the wrong version. Note that hreflang is for language/regional targeting — not for every country. If you only have one English version for global use, hreflang is not needed. It's also not needed for pages that are truly unique per region with different content and different topics — those are separate pages, not alternate versions of the same page.

Implementing Hreflang Correctly

The most common hreflang implementation uses `` tags in the `` of each page^[1]^[2]. For a page with US English, UK English, and French versions, each version includes three link tags pointing to all three versions (including itself). The format: ``, ``, ``. Each version must include all the same alternate tags. The self-referencing tag (pointing to the current page) is required. Language codes follow BCP 47 format (e.g., 'fr' for French, 'fr-CA' for Canadian French). For large sites, XML sitemap implementation is more maintainable than per-page `` tags.

Common Hreflang Errors

Hreflang implementation errors are very common and prevent the feature from working correctly^[1]^[2]. The most frequent mistake is broken bidirectionality: if page A lists page B as an alternate but page B doesn't list page A, Google ignores the entire hreflang cluster. Return links must be complete. Using the wrong language code format (e.g., 'en_US' with underscore instead of 'en-us' with hyphen) prevents recognition. Pointing hreflang to redirected URLs or non-canonical URLs causes confusion. Using hreflang with noindex pages is contradictory. Check for these issues using Google Search Console's International Targeting report or specialized hreflang validation tools like hreflang.org. For enterprise sites, auditing hreflang across thousands of pages requires automated crawling.

SOURCES

Google Search Central — Localized Versions of Your Pages (hreflang)

Ahrefs — Hreflang: The Easy Guide for Beginners

Last updated: June 9, 2026

Related Terms

Canonical URL

An HTML tag that tells search engines which version of a page is the preferred, authoritative URL when multiple URLs serve the same or very similar content.

Duplicate Content

Substantively identical or very similar content that appears on multiple URLs, either within the same site or across different sites, which can confuse search engines about which version to index and rank.

Crawlability

The ability of search engine bots to access, navigate, and read the pages on your website without encountering technical barriers.

XML Sitemap

A file (typically in XML format) that lists all the important URLs on a website, helping search engines discover and crawl content more efficiently.

Put it into practice

Skribra automates your SEO content pipeline — from keyword research to published articles — so you can apply these concepts at scale.

Try Skribra Free