Hreflang is a small piece of metadata that tells search engines 'this page exists in N language and region versions; serve the right version to the right user.' It does not boost rankings or move ranking signals between pages — it only controls which of your equivalent pages appears in the SERP for a given user's language and country. It is essential for any site targeting multiple countries or languages, and it is famously easy to break. This guide covers what hreflang is, when you actually need it, the three valid implementation methods, and the common mistakes that cause Google to ignore it.
Hreflang is an HTML attribute (or HTTP header, or XML sitemap entry) that tells search engines which language and regional version of a page to serve to which audience. It does not change rankings; it changes which version of a multi-region or multi-language page Google shows to a given user. Critical for any site with content for multiple countries or languages. Implementation is finicky — bidirectional links, exact ISO codes, and an x-default fallback are mandatory.
Hreflang is a small piece of metadata that tells search engines 'this page exists in N language and region versions; serve the right version to the right user.' It does not boost rankings or move ranking signals between pages — it only controls which of your equivalent pages appears in the SERP for a given user's language and country. It is essential for any site targeting multiple countries or languages, and it is famously easy to break. This guide covers what hreflang is, when you actually need it, the three valid implementation methods, and the common mistakes that cause Google to ignore it.
Hreflang annotates a set of pages as language and region equivalents of one another. When a Spanish-speaking user in Mexico searches a query that matches your content, Google can choose your Mexican-Spanish page over your Spanish-from-Spain page even though both pages cover the same topic. Without hreflang, Google guesses based on TLD, server location, and content language signals — and often guesses wrong.
Hreflang is necessary when you have substantively similar content in multiple languages or regional variants of a language (en-US vs en-GB vs en-CA, es-ES vs es-MX, fr-FR vs fr-CA). It is not necessary if you have only a single language version, or if your regional variants serve genuinely different content (different products, different services, different legal entities).
It is also necessary when you have country-specific TLDs or subdirectories that target different markets with the same language — e.g., example.com/us/ and example.com/uk/ both in English.
Hreflang can be declared in three ways. Pick one and stick with it; mixing methods on the same page often produces conflicts.
Every hreflang relationship must be reciprocal. If page A says 'B is my Spanish version,' page B must say 'A is my English version.' Google ignores hreflang annotations that are not reciprocally confirmed by the other page in the cluster. This is the single most common bug — usually because a page was added in one language without updating the other versions.
Every cluster should include an x-default entry pointing at the page to serve when no language or region matches the user. ISO codes must be exact: language codes are two-letter ISO 639-1 (en, es, fr, de), region codes are two-letter ISO 3166-1 alpha-2 (US, GB, CA, MX), and they're combined with a hyphen (en-US, es-MX). Common errors: en-UK (should be en-GB), zh-CN-Simplified (should be zh-Hans), or using a country name instead of code.
Search Console's International Targeting report flags reciprocity errors and invalid codes for the URLs Google has crawled. Third-party crawlers (Screaming Frog, Sitebulb, Ahrefs) can crawl your full hreflang implementation and surface inconsistencies. Run a full audit after every site migration and after every new language launch.
Toronto SEO works with ambitious businesses across the GTA on the exact playbooks taught in this hub. Get a free, senior-led audit of where your SEO program stands today.