Hreflang Troubleshooting: 10 Common Mistakes (And How to Fix Them in 2026)

The most frequently reported hreflang error. Every language variant must link back to every other variant. If page A links to page B but page B does not link back to page A, the entire cluster is invalidated.

Fix: Generate a complete bidirectional mapping. For each URL in a hreflang set, verify that every other URL in the set references it. Use a script or hreflang audit tool to detect orphan references.

Using en-uk instead of en-GB, zh-cn where the script is implied, or three-letter ISO 639-2 codes like eng. None of these are recognized.

Fix: Use only ISO 639-1 two-letter language codes and ISO 3166-1 alpha-2 region codes. Reference the IANA Language Subtag Registry before adding a new locale.

Every page must include a hreflang entry pointing to its own URL. Without it, search engines may disregard the entire set.

Fix: Add <link rel="alternate" hreflang="en" href="https://example.com/en/" /> to the same URL it describes. Yes, it references itself, and yes, it is required.

When a page's hreflang annotation points to URL X, but the canonical tag on URL X points to a different page, search engines follow the canonical and ignore the hreflang signal.

Fix: Ensure every URL referenced in a hreflang entry has a self-referencing canonical pointing to itself. Cross-canonical setups between language variants defeat hreflang entirely.

Using HTML tags on some pages and XML sitemap annotations on others without ensuring they match. Conflicting signals cause search engines to discard all hreflang annotations.

Fix: Choose one primary delivery method and apply it universally. If you need a secondary method, run a diff to confirm every annotation is identical.

A page with a noindex robots meta tag cannot serve as a hreflang target. If page A references page B and page B is noindexed, page B is ignored and the cluster is broken.

Fix: Remove noindex from all pages referenced in hreflang annotations. Use index, follow on every variant.

Missing x-default entirely, or using x-default on a URL that redirects rather than showing content.

Fix: Add x-default pointing to a stable, indexable page that serves as the fallback. A language selector page or the primary market homepage works well.

Tracking parameters, session IDs, or fragment identifiers in hreflang href values. Google treats https://example.com/en/?utm_source=twitter as a different URL than https://example.com/en/.

Fix: Strip all tracking parameters and fragments from hreflang href values. Use clean, canonical URLs exclusively.

Implementing hreflang on the root product pages but not on paginated category pages or filtered search results. Users landing on those pages see no language alternative.

Fix: Extend hreflang to every URL that has language-specific variants. This includes paginated pages, search results, and filter pages.

Many CMS hreflang plugins auto-generate tags based on URL patterns but produce incorrect mappings when custom post types or taxonomies are added.

Fix: Audit plugin-generated hreflang tags manually after any content structure change. Use a crawl-based tool that validates each tag pair, not just counts how many tags exist.

Run a full hreflang audit at least once per quarter and after every site migration, CMS update, or new language launch. The Screaming Frog SEO Spider, Merkle's Hreflang Tool, and Google Search Console's International Targeting report are the three tools to rotate through for coverage. Fix return tag errors first they are the most common and the most damaging.

References

1. Google Search Central. "Hreflang tag errors." developers.google.com/search/docs/specialty/international/hreflang-errors. 2026.
2. Merkle. "Hreflang Tags: Common Errors and How to Fix Them." merkle.com/digital-marketing/resources/hreflang-common-errors. 2025.
3. Screaming Frog. "Hreflang Configuration and Validation." screamingfrog.co.uk/seo-spider/hreflang/. 2025.
4. Aleyda Solis. "International SEO Troubleshooting." aleydasolis.com/international-seo-troubleshooting/. 2025.