What Is Hreflang? International SEO Guide
Hreflang is an annotation telling Google which language and region each URL targets, so searchers get the right version. It applies to pages with fully or near-fully translated equivalents.
Explain It Like I'm 5
Hreflang is Google's tour-guide system for languages: this page is English, this one is Spanish, this one is Spanish for Mexico. Google then serves each searcher the version they can actually read. It is NOT a location redirect - locals can read any language they want.
Understanding Hreflang
Hreflang annotations declare language and optionally region (en, en-GB, es, es-MX) for a set of equivalent URLs. Google uses them to swap the served version to match the searcher's language preference: a German speaker searching in Germany can receive the de version of an English-ranked page.
The most misunderstood rule: hreflang is about language, not geo-redirecting. Google serves the version matching the searcher's language, regardless of location; it does not redirect by country. Region codes (en-GB) narrow language variants, not audience borders.
Implementation requires bidirectional completeness: every version must reference every other version, including itself, via one consistent method (HTML link tags, HTTP headers, or XML sitemap entries). Return links are mandatory; one-way annotations are ignored. Each URL in the cluster must also be canonical to itself, not cross-canonicalized.
Common failure modes: missing return tags, mixing methods inconsistently, including URLs that 404 or redirect, and using hreflang for near-duplicate content that is not actually translated. Google ignores broken clusters and falls back to default ranking behavior.
Types of Hreflang
Language-Only Annotation
Targeting a language globally.
Example: hreflang="es" for a Spanish version serving all Spanish speakers everywhere.
Language-Region Annotation
Targeting a regional variant of a language.
Example: hreflang="es-MX" distinguishing Mexican Spanish from es-ES and es-AR variants.
Why Hreflang Matters
For multilingual sites, hreflang is the difference between serving every searcher a readable page and cannibalizing your own variants in the wrong markets.
Best Practices
Annotate Fully Translated Equivalents Only
Hreflang clusters are for pages saying the same thing in different languages. Partially translated or merely localized pages do not qualify.
Keep Clusters Bidirectional and Complete
Every version lists every other version plus itself. One missing return tag invalidates the annotation Google can use.
Use One Method Consistently
HTML tags, HTTP headers, or sitemap: pick one. Mixing methods invites conflicts and errors.
Ensure Each URL Self-Canonicalizes
Cross-canonicalization inside a cluster breaks the structure. Each variant must stand as its own canonical.
Common Mistakes
Using hreflang as a geo-redirect
Fix: It signals language, not country. Searchers get versions by language preference; hreflang never forces location-based serving.
Incomplete return tags
Fix: A cluster missing one back-reference is a broken cluster. Google falls back to default behavior and your variants compete.
Annotating untranslated near-duplicates
Fix: Pages with the same template but untranslated content are not equivalents. Annotating them confuses serving.
Hreflang and WPLink
WPLink operates on single-domain content relationships and leaves international annotations to your platform. Clean hreflang clusters keep variant pages independent, exactly the structure internal linking needs.
Frequently Asked Questions
Related Articles
Ready to optimize your internal links?
Get started with WPLink today and see the difference.
Download WPLink