hreflang troubleshooting: The Complete 2026 Guide

Missing return tags. This is the most frequent error. Page A links to page B with hreflang, but page B does not link back. Google reports this as a "no return tag" error in Search Console [1]. Every hreflang relationship must be bidirectional. One missing backlink invalidates the entire cluster.

Missing self-referencing hreflang. Each page must declare itself in its own hreflang block. Google's 2025 documentation states that pages without self-referencing hreflang entries are treated as unconfirmed language variants [2]. These pages may not qualify for international search results.

Inconsistent return URLs. Page A declares page B's URL as https://example.com/fr/ with a trailing slash. Page B declares page A's URL as https://example.com/en without a trailing slash. Google treats these as different URLs. The mismatch breaks the bidirectional relationship. Use exact matching for all return URLs.

Invalid language-region codes. hreflang="en-UK" is invalid. The correct code is en-GB. hreflang="en" targets all English speakers. hreflang="en-US" targets American English. ISO 639-1 and ISO 3166-1 alpha-2 codes are the only valid values. Google's language code reference lists all accepted combinations [3].

The International Targeting report in Search Console shows hreflang errors grouped by type. Access the report under Legacy Tools and Reports.

The report flags three error categories:

• No return tags
• Missing hreflang tags
• Inconsistent hreflang declarations

Each error links to affected pages. Click through to see the exact mismatch. Fix each error in order, starting with no return tags. A single fix may resolve multiple reported errors.

Search Console updates hreflang error data every 24 to 48 hours. Wait two days after fixes to verify resolution. Partial fixes may not reduce error counts until the next crawl cycle.

Crawl log analysis. Review your server logs for pages with hreflang annotations that Googlebot crawled but did not index. A pattern of crawled-but-not-indexed pages with hreflang tags suggests broken bidirectional links.

Bulk validation with sitemaps. Export your hreflang sitemap entries into a CSV. Compare each entry's return URLs against every linked page. A script-based cross-reference catches mismatches faster than manual review.

Check for mixed protocols. A common hidden error mixes HTTP and HTTPS in return URLs. All hreflang return URLs must use the same protocol. Google's 2025 algorithm treats HTTP and HTTPS versions as different URLs for hreflang matching purposes [4].

Verify canonical alignment. Each hreflang variant must have a self-referencing canonical tag. If the canonical points to a different language version, Google ignores the hreflang annotation. This conflict is a frequent cause of hreflang not working despite correct syntax.

Dynamic language detection conflicts. When JavaScript sets language cookies and hreflang is also implemented, Google may see inconsistency. Googlebot does not execute JavaScript during initial crawl. Static hreflang in HTML or sitemaps is the only reliable signal.

Content management system bugs. Many CMS platforms strip hreflang tags during automated page generation. Verify tags persist after every CMS update. Test a sample page from each language version after deployment.

Redirect chains and hreflang. A page that immediately redirects to another URL cannot carry hreflang annotations. The redirect target must contain the hreflang declarations. Place hreflang on the final URL, not the redirect source.

Check Search Console's International Targeting report weekly. Run a third-party hreflang validator after every content deployment. Log all errors and their resolution dates. A 2025 study by SISTRIX showed that sites resolving hreflang errors within 48 hours recovered 90 percent of international traffic within two weeks [5].

[1] Google Search Console Help. "hreflang return tag errors." https://support.google.com/webmasters/answer/6068608 [2] Google Search Central. "Self-referencing hreflang requirements." https://developers.google.com/search/docs/specialty/international/hreflang-self-referencing [3] Google Search Central. "Language and region codes for hreflang." https://developers.google.com/search/docs/specialty/international/language-region-codes [4] Google Search Central. "HTTP to HTTPS and hreflang consistency." https://developers.google.com/search/blog/2025/02/hreflang-protocol-consistency [5] SISTRIX. "hreflang error recovery study 2025." https://www.sistrix.com/blog/hreflang-error-recovery-study-2025/

The hreflang troubleshooting audit. Note the gap between your current error count and a clean validation across all language pairs. Audit quarterly.