Key takeaways
- Hreflang errors are common: an Ahrefs study of 374,756 domains found 67% had at least one issue, most often a missing x-default.
- Annotations must be reciprocal. If page A points to page B and B does not point back, Google ignores the pair.
- Each page should list itself as well as every alternate version.
- HTML link elements, HTTP headers and XML sitemaps all work; choose the one your CMS can keep accurate.
- Search Console no longer has an International Targeting report, so validate hreflang with crawls and URL Inspection.
| Question | Short answer |
|---|---|
| What are the most common hreflang errors and how do you prevent them? | Small mistakes that cause Google to ignore the annotations. |
| Which implementation method works best for enterprise sites? | The one your systems can keep correct. |
| How do you manage hreflang across thousands of pages? | Automate it from a single mapping source. |
| How do you use x-default to handle unmapped users? | Point x-default at the page for visitors who match none of your listed languages or regions. |
Hreflang annotations tell Google which language or regional version of a page to show each user. For sites running across countries and languages, correct hreflang keeps a French speaker in Canada from landing on the page meant for France, or a UK visitor from seeing US pricing. This Emulent guide covers when you need hreflang, the errors that break it and how to manage it at scale.
When does your site need hreflang tags?
When you have several versions of similar content for different languages or regions.
- The same content translated into multiple languages, such as English, French and German product pages.
- Regional variants in one language, such as US, UK and Australian pages with different pricing, spelling or shipping.
- Language and region combinations, such as fr-FR, fr-CA and fr-BE.
If you serve one version to everyone, or publish in only one language, hreflang adds nothing. Note that hreflang helps Google choose which version to show; it does not raise rankings by itself.
What are the most common hreflang errors and how do you prevent them?
Small mistakes that cause Google to ignore the annotations. Google’s localized versions guide says that if two pages do not both point to each other, the tags will be ignored. The Ahrefs hreflang study found missing x-default on 56.3% of domains, missing self-references on 18% and links to redirected or broken pages on 16.9%.
- Missing return tags between alternates.
- Missing self-referencing entries.
- Invalid codes. Use ISO 639-1 language codes (en, fr, de) with optional ISO 3166-1 Alpha-2 regions (US, GB, CA). “en-UK” is a common error; the correct code is en-GB.
- Hreflang pointing to non-canonical, redirected or broken URLs.
- Conflicting annotations when more than one method is used and they disagree.
Which implementation method works best for enterprise sites?
The one your systems can keep correct. All three are valid, and Google treats them the same.
- HTML link elements in the head: the most common choice, workable for a handful of variants but heavy on pages with many alternates.
- HTTP headers: needed for non-HTML files such as PDFs, and useful where templates are hard to change.
- XML sitemaps with xhtml:link entries: keeps annotations out of templates and centralizes management, which suits sites with many variants.
As a rule of thumb, sitemaps tend to scale better once you pass about five variants, while HTML is simpler for fewer. If you use more than one method, make sure they match exactly. On WordPress, Emulent manages hreflang through multilingual plugin mappings.
How do you manage hreflang across thousands of pages?
Automate it from a single mapping source. A site with 10,000 pages in 8 languages has 80,000 URLs to cross-reference.
- Keep a mapping table in the CMS that links each page to its alternates and generates annotations automatically.
- Run a scheduled crawl that checks reciprocity, codes, canonical alignment and status codes.
- Decide how to handle missing translations: leave that language out of the set, or point to the closest available version only when it truly serves those users.
- Connect publishing and localization workflows so new, removed and moved pages update the mapping.
A strong content strategy for each market keeps localized pages useful rather than thin translations.
How do you use x-default to handle unmapped users?
Point x-default at the page for visitors who match none of your listed languages or regions.
- Use a language selector page or your most broadly useful version as the x-default target.
- Add x-default to each hreflang set. Google recommends it rather than requiring it, but its absence was the most common gap in the Ahrefs study.
- Do not rely on x-default in place of real targeting; if you serve Spanish speakers, add an “es” entry.
How can the Emulent team help?
Emulent implements and audits hreflang for international sites as part of enterprise SEO work, building the mapping, automating validation and fixing errors. A caveat: hreflang is a signal Google may still override, so check which versions rank in each market after changes. Contact the Emulent team to review your international setup.