Call or WhatsApp us anytime

+1 (437) 967-2770

Hreflang Errors in Search Console: 8 Common Issues and Exact Fixes

Hreflang errors cover showing 8 common issues and exact fixes

Google Search Console no longer has a dedicated hreflang error report, because the International Targeting report that showed those errors has been deprecated. Hreflang errors still happen, and they still stop the right language version from appearing, but they now have to be found with a site crawler, the URL Inspection tool and the Page indexing report.

Google confirms on its International Targeting deprecation notice that it continues to support hreflang. This guide lists the eight hreflang errors that appear most often, how each one shows up today, and the exact fix for each.

★

Key Takeaways

  • Search Console no longer has a hreflang error report, because the International Targeting report was deprecated; Google still supports hreflang.
  • Missing return links are the most damaging error, because Google ignores hreflang pairs that do not point to each other.
  • Valid codes use ISO 639-1 languages and ISO 3166-1 Alpha 2 regions, so en-UK must be en-GB and es-419 is not supported.
  • Translated pages need self-referencing canonicals; a canonical pointing to another language conflicts with hreflang.
  • Hreflang URLs must be fully qualified, return 200 and be indexable, with tags placed in the head or the XML sitemap.
  • The Hreflang Debug Path runs crawl, group, inspect, fix at the source and validate.

Where Do Hreflang Errors Show Up Now?

Hreflang errors now show up as symptoms in Search Console and as direct findings in third-party crawlers. Search Console no longer lists them by name, so the work is to connect the symptom to its cause.

  • Performance report: searchers in one country land on the wrong language version, visible when filtering by country and page folder.
  • Page indexing report: translated pages marked as “Alternate page with proper canonical tag” or “Duplicate, Google chose different canonical than user”, which often points to canonical and hreflang conflicts.
  • URL Inspection: shows the canonical Google selected for a specific page and whether that page is indexed.
  • Crawlers: tools such as Screaming Frog report hreflang issues directly, including missing return links and invalid codes.

What Are the 8 Most Common Hreflang Errors?

The most common hreflang errors are missing return links, missing self-references, invalid codes, conflicts with canonicals, links to broken or redirected URLs, relative URLs, tags outside the head and a missing x-default. The table summarises each error and its fix.

ErrorWhat goes wrongExact fix
1. Missing return linksPage A lists page B, but B does not list AAdd the reciprocal annotation on every alternate
2. Missing self-referenceA page lists its alternates but not itselfInclude each page in its own hreflang set
3. Invalid codesCodes such as en-UK, es-419 or EUUse ISO 639-1 and ISO 3166-1 Alpha 2, such as en-GB
4. Canonical conflictTranslated page canonicalized to another languageSelf-referencing canonical on every version
5. Non-200 alternatesHreflang points to redirects, 404s or noindex pagesPoint only to final, indexable 200 URLs
6. Relative URLs/es/page/ instead of the full addressUse fully qualified URLs with https://
7. Tags outside the headTags injected into the body or after invalid head HTMLOutput tags in a valid head, or use the sitemap method
8. Missing x-defaultNo fallback for unmatched languagesAdd x-default pointing to a selector or global page

1. Missing return links

This is the most damaging error, because Google ignores hreflang pairs that are not confirmed in both directions. Google’s documentation on localized versions of a page states that the tags are ignored when two pages don’t both point to each other. It usually happens when a page is translated into only some languages, or when one version is edited and its tags are not updated. Fix: make sure every page in a set lists every other page in that set.

2. Missing self-reference

Each page must include itself in its hreflang list, as well as its alternates. Google’s documentation requires the page’s own language and URL in the set. Fix: add a line for the current page, for example the Spanish page listing its own URL with hreflang=”es”.

3. Invalid language or region codes

Hreflang only accepts ISO 639-1 language codes with optional ISO 3166-1 Alpha 2 region codes. The most common mistake is en-UK, which should be en-GB. Google also notes that es-419 is not supported and that codes such as EU or UN have no effect. Chinese script variants use zh-Hans and zh-Hant. Fix: replace every invalid code and recheck with a generator or crawler.

Table of invalid hreflang codes such as en-UK and es-419 with the correct values
Replace invalid hreflang values with valid ISO codes.

4. Canonical tags pointing to another language

A canonical tag that points a translated page to the English original tells Google the translation is a duplicate, which conflicts with hreflang listing it as an alternate. The translated page may then drop out of the index. Fix: give every language version a self-referencing canonical, and make sure hreflang lists only canonical URLs.

5. Hreflang pointing to redirected, broken or noindex URLs

Alternates must be live, indexable pages that return a 200 status. Links to redirected URLs, 404 pages or pages marked noindex break the set. This often appears after slugs are translated or changed without updating the annotations. Fix: crawl the site, then update each hreflang URL to its final destination or remove the dead alternate.

6. Relative or incomplete URLs

Hreflang URLs must be fully qualified, including the protocol and domain. A value such as /es/servicios/ is not valid. Mixing http and https, or www and non-www, creates the same kind of mismatch. Fix: use complete URLs that exactly match each page’s canonical.

7. Tags placed outside the head

Hreflang link elements are only read in the head section. Tags injected into the body by scripts, or placed after an element that closes the head early, such as an image or iframe in the head, are not read. Fix: output tags in a valid head, or move annotations to the XML sitemap, which Google supports as an equivalent method.

8. Missing or misused x-default

x-default tells Google which page to show when no language version matches the searcher. Without it, unmatched visitors may land on any version. A common misuse is pointing x-default at a page that is not part of the set. Fix: point x-default to a language selector or the main global page, and include it on every page in the set.

How Do You Find Hreflang Errors Step by Step?

Crawl first to find errors at scale, inspect key pages in Search Console to confirm how Google sees them, then fix the template rather than individual pages. The Hreflang Debug Path below keeps the process in order.

  1. Crawl: run a crawler with hreflang checks across every language folder.
  2. Group: sort issues by type, since most come from one template or plugin setting.
  3. Inspect: check a sample of affected pages with URL Inspection to see Google’s selected canonical.
  4. Fix at the source: correct the plugin setting, template or sitemap generator.
  5. Validate: recrawl, then confirm traffic by country and folder over the following weeks.
Hreflang Debug Path: crawl, group, inspect, fix at the source and validate
The Hreflang Debug Path fixes errors at their source.

Screaming Frog reports 14 hreflang issue types, from missing return links to mismatches with the HTML lang attribute, and it is one of several crawlers compared in this guide to multilingual SEO tools. For small sets of URLs, Aleyda Solis’s free generator creates correct tags for up to 50 URLs.

Aleyda Solis hreflang tags generator for multi-language and multi-country websites
Aleyda Solis Hreflang Tags Generator page, captured November 2026.

Indexing problems on translated pages can also be checked quickly with a free Google index checker before running a full crawl.

Why Do Hreflang Errors Keep Coming Back?

Hreflang errors return because sites change: new pages are published in one language, slugs change, and plugins are updated or replaced. Each change can break reciprocity across the whole set.

A pattern observed across client work is that most hreflang problems trace back to one of three moments: a site migration, a switch of translation plugin, or a content team publishing pages in the main language without planning the translations. Adding a hreflang crawl to the release checklist for each of these moments prevents most repeat errors. The wider set of checks belongs in every technical SEO checklist.

Does Google use hreflang to detect a page’s language?

No. Google states that it does not use hreflang or the HTML lang attribute to detect a page’s language. It reads the visible content. Hreflang only tells Google which pages are alternates, so a page with English menus and Spanish body text still sends a mixed signal however correct its tags are. The full setup for each language version is explained in the multilingual SEO handbook.

Sites with recurring hreflang problems across several markets may need a full audit of templates, plugins and sitemaps, which professional technical SEO services cover.

Frequently Asked Questions About Hreflang Errors

Where can I see hreflang errors in Google Search Console?

Search Console no longer shows hreflang errors directly, because the International Targeting report was deprecated. Use the URL Inspection tool to check how Google indexes a page and which canonical it chose, the Page indexing report for canonical issues, and a crawler such as Screaming Frog to list hreflang errors.

What does “no return tags” mean in hreflang?

No return tags means page A lists page B as an alternate, but page B does not list page A. Google requires annotations in both directions and ignores pairs that are not confirmed. Fix it by making every page in a language set list every other page in that set, including itself.

Is en-UK a valid hreflang code?

No. The correct region code for the United Kingdom is GB, so the valid value is en-GB. Hreflang uses ISO 639-1 language codes and ISO 3166-1 Alpha 2 region codes. Other invalid values include es-419 for Latin American Spanish and EU, which Google says are not supported.

Can hreflang errors hurt rankings?

Hreflang errors do not cause a penalty, but they can stop Google from showing the right language version to the right searchers. Visitors may land on the wrong language and leave, and translated pages may compete with each other or drop out of the index when canonicals conflict with hreflang.

Should hreflang go in the HTML head or the XML sitemap?

Both work, and Google treats HTML link elements, HTTP headers and XML sitemaps as equivalent methods. Sitemaps are easier to manage on large sites because all annotations live in one file. Use one method consistently, since mixing methods makes errors harder to find and fix.

For help fixing hreflang across several markets and building authority for each version, Stay Digital Marketers is one resource that supports brands with guest posting, press release distribution, SaaS backlinks, niche edits, multilingual backlinks, Wikipedia page creation, Google Knowledge Panel creation and complete SEO services.

Stay Digital Marketers

Grow Your Brand on Google, in AI Answers and on Autopilot

SEO, Link Building and AI Automation by Stay Digital Marketers

Get Your Growth Plan โ†’
cropped Filza Taj Founnder Stay Digital Marketers Author Image 189x189

Filza Taj

Administrator

Filza Taj is an MPhil in Human Resources-turned SEO Specialist, Content Strategist, and Digital Marketing Consultant with over 5 years of experience helping businesses in 30+ countries grow online. As the Founder of Stay Digital Marketers (staydigitalmarketers.com), she delivers results-driven solutions in link building, guest posting, PR distribution, niche edits, multilingual backlinks, and content marketing. She publishes daily SEO insights and actionable strategies to help brands strengthen their online presence, attract the right audience, and convert clicks into loyal customers. Filza@staydigitalmarketers.com

Leave A Comment

Your email address will not be published. Required fields are marked *