Hreflang is an HTML attribute that specifies both the language and any optional geographic restrictions for a webpage, helping search engines understand its intended audience.
Web developers or digital marketers working on multilingual websites often consult this information alongside technical standards to ensure proper global indexing of their content.
External context
Using hreflang allows site owners to clearly communicate the linguistic and regional focus of their website to search engine crawlers. This is crucial because it helps guarantee that users are directed to the most relevant version of a page based on both their location and preferred language settings.
Hreflang Wikipedia contributors, “Hreflang”, en.wikipedia.orgLicence01What it is and how it works
hreflang is an HTML link element added to the section of a webpage. Each hreflang tag includes a language code (like 'en' for English) and optionally a region code (like 'US' for United States). When a user searches in a specific language or from a specific country, search engines use these tags to serve the most appropriate page version. For example, a French page might use hreflang="fr" and a Canadian French page might use hreflang="fr-CA". The tags also require a self-referencing hreflang to confirm the page's own targeting. This system prevents duplicate content issues by clarifying which page is intended for which audience.
hreflang is a way to tell search engines which language and region a webpage is for, so users get the right version of the page.
02What to do about it
Implement hreflang tags on all language and regional variations of your pages. Start by identifying all target languages and regions. Add hreflang tags to the of each page, ensuring each page references all other language versions, including itself. Use the format hreflang="language-region" (e.g., hreflang="es-ES" for Spanish in Spain). Validate your implementation using Google Search Console's International Targeting report or third-party tools like Aleyda Solis' hreflang validator. Update tags whenever you add or remove language versions. Ensure consistency across all pages and avoid using hreflang on pages with no alternative versions.
03How it is measured or noticed
To verify hreflang implementation, check the HTML source of your pages for correct tags. Use Google Search Console's International Targeting report to see which hreflang issues are detected. Third-party tools like Screaming Frog or Ahrefs can crawl your site and flag missing or incorrect tags. Monitor search performance in Google Analytics by language and region to confirm users are being directed to the right pages. Pay attention to the 'hreflang' column in Google Search Console's coverage report, which shows detected hreflang issues.
04Common mistakes
- Failing to include a self-referencing hreflang tag on each page
- Using incorrect language or region codes (e.g., 'en' instead of 'en-US')
- Not referencing all language versions on every page
- Implementing hreflang on pages without alternative versions
- Using conflicting or contradictory hreflang tags across pages
05Limits
hreflang only applies to content that has legitimate language or regional variations. It does not replace proper content localization or translation. Hreflang does not affect how search engines crawl or index pages; it only influences which version is shown in results. It is not a substitute for using canonical tags, which prevent duplicate content issues. Hreflang does not guarantee a page will appear in search results for a specific language or region, as other factors like content quality and relevance still matter. It is also not applicable to subdomains or subdirectories unless explicitly configured.
06Worked example
If you have a page in English for the US market, a page in English for the UK market, and a page in French for France, your hreflang tags would look like this: <link rel="alternate" hreflang="en-US" href="https://example.com/us-en">, <link rel="alternate" hreflang="en-GB" href="https://example.com/uk-en">, and <link rel="alternate" hreflang="fr-FR" href="https://example.com/fr-fr">. Each page must include all three tags, including its own.
The entry above is written by GetLoopLoop. What follows is what independent catalogues hold about the same term — none of it is the source of this page.
- Also called
- international seo tagging
- Kind of thing
- meta element
The same term on Wikipedia
Catalogued in 6 languagesFrequently asked questions
How does hreflang differ from the canonical tag?
hreflang tells search engines which language or regional version of a page to serve, while canonical indicates the preferred version when duplicate content exists. They serve different purposes and can be used together on the same page.
When should I skip hreflang implementation?
Skip it when you have only one language version of your content, or when regional variations are identical except for currency or contact details. It adds complexity without benefit if no genuine language or locale alternatives exist.
What happens if I use incorrect language codes in hreflang tags?
Search engines may ignore the tags entirely or serve the wrong version to users. Invalid codes like "en-uk" instead of "en-gb" are a common cause of hreflang errors reported in Search Console.
Does hreflang still work with Google's current algorithms?
Yes, Google continues to use hreflang as a strong signal for language and regional targeting. It remains the standard method for multi-language sites, though it works alongside other signals like server location and content language.
How long does it take for hreflang changes to affect search results?
Changes typically appear within a few days to a couple of weeks after Google recrawls the pages. Monitor the International Targeting report in Search Console for errors and the Performance report for country-specific impression shifts.
Should I implement hreflang in HTML, HTTP headers, or XML sitemaps?
All three methods work; choose one per URL set to avoid conflicts. HTML is most common and easiest to debug. Sitemaps scale better for large sites. HTTP headers are necessary for non-HTML files like PDFs.
Asked out loud
spoken, not typedThe same term in the words somebody uses speaking to an assistant rather than typing into a box — written from the situation, which is why each one carries the situation it came from.
Check the page source for link rel="alternate" tags pointing to each language version with correct codes like hreflang="es-es" and a matching return tag on the Spanish page. Run the URL through Search Console's URL Inspection tool to see if Google reads them without errors.
Add hreflang="fr-fr" for France and hreflang="fr-ca" for Canada on each version, plus an x-default pointing to your global page. Without the specific regional codes, Google treats all French content as one cluster.
The migration likely broke return tags or left orphan hreflang references to old URLs. Verify every German page has a self-referencing tag and bidirectional links to its English and French counterparts, then resubmit the sitemap.