Hreflang Tags Not Working: Common Mistakes and Fixes

When hreflang tags are set up incorrectly, search engines ignore them, leading to incorrect regional targeting and duplicate content issues. Below are the most common technical errors that cause hreflang validation failures and how to fix them.

1. Missing Self-Referencing Tags

Every localized page must include a self-referencing hreflang tag that points to its own URL. If Page A points to Page B, Page A must also point to Page A. Without this, search engines will ignore the entire set of hreflang attributes.

The Fix: Ensure the page's own URL is included in the hreflang block. For example, on the English page (https://example.com/en/), the code must look like this:

<link rel="alternate" hreflang="en" href="https://example.com/en/" />
<link rel="alternate" hreflang="es" href="https://example.com/es/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

2. No Reciprocal (Return) Tags

Hreflang requires a two-way confirmation. If the English page (/en/) points to the Spanish page (/es/), the Spanish page must point back to the English page. If this reciprocal relationship is broken, Google will discard the annotations.

The Fix: Ensure that the exact same set of hreflang tags is placed on every single alternate version of the page. The code block on /en/ and /es/ must be identical.

3. Invalid ISO Language or Region Codes

Search engines only recognize specific formats for hreflang values. The language code must use the ISO 639-1 format, and the optional region code must use the ISO 3166-1 Alpha 2 format. The language code must always come first.

Common mistakes include:

• Using en-UK instead of the correct en-GB (United Kingdom).
• Using en-US in the wrong order, such as us-en.
• Using regional codes without a language code (e.g., hreflang="us" is invalid; it must be en-us or es-us).

The Fix: Audit your codes. Use lowercase for the language (e.g., es) and uppercase for the optional region (e.g., ES), separated by a hyphen: es-ES.

4. Pointing to Non-Canonical, Redirected, or Broken URLs

Hreflang tags must only point to indexable, canonical URLs that return a 200 OK HTTP status code. If a tag points to a URL that redirects, returns a 404 error, or contains a noindex tag, search engines will ignore the instruction.

The Fix: Check that the URLs in your hreflang tags exactly match the canonical URLs of the target pages. If https://example.com/es/ canonicalizes to https://example.com/es (without the trailing slash), your hreflang tag must use the non-slashed version.

5. Conflicting Implementation Methods

Hreflang tags can be implemented using three methods: HTML header tags, HTTP headers (for non-HTML files like PDFs), or XML sitemaps. If you use multiple methods and they contain conflicting data, search engines may ignore all of them.

The Fix: Choose one implementation method and stick to it. If you manage hreflang via an XML sitemap, remove any legacy hreflang tags from your site's HTML head.

Quick Hreflang Debugging Checklist

• Does every alternate page contain a self-referencing tag?
• Do all targeted pages link back to each other reciprocally?
• Are the language codes ISO 639-1 and region codes ISO 3166-1 Alpha 2?
• Do all referenced URLs return a 200 OK status code?
• Are you pointing exclusively to canonical URLs?

Need this done fast? order a fix on Kwork.