Start hreflang troubleshooting with the page-to-language mapping, then verify codes, reciprocal annotations and final URLs. Valid tags do not prove indexing or guarantee that a particular regional audience will see a page. Google explicitly treats hreflang values as case-insensitive: EN-us is not invalid simply because of its capitalization.
Hreflang describes alternate language or regional versions of a page. It does not translate the content or act as a ranking switch. The checks below follow Google’s localized-version documentation and distinguish a malformed annotation from a valid code aimed at the wrong audience.
Build the mapping before debugging the tags
Group the versions of one product, article or tool. Record the intended language, optional region, final URL, response, canonical and alternate annotations. An English product should point to the equivalent French product, rather than the French homepage. If a translation does not exist, record that gap instead of filling it with an unrelated destination.
Translating navigation while leaving the main content in English does not create a complete French version. Google’s multilingual-site guidance explains that visible content determines language; lang attributes and hreflang annotations do not replace it. Provide accessible language-switch links, and avoid automatic location or language redirects that prevent users and crawlers from reaching other versions.
Separate code validity from targeting accuracy
| Value | Meaning or issue | Decision |
|---|---|---|
| en-US / EN-us | Equivalent capitalization for Google hreflang | Use conventional casing for consistent maintenance |
| es-ES | Spanish for Spain; a valid combination | Use es for an appropriate non-region-specific Spanish version |
| zh-TW | Chinese targeting Taiwan; not an invalid value | Use zh-Hant when the intended distinction is the traditional script |
| zh-Hans / zh-Hant | Simplified / traditional Han script | Script and geographic targeting are different dimensions |
| pt-BZ | Portuguese with the Belize region code; not Brazil | For Brazilian targeting, check the content and use pt-BR |
| eu | Basque language, not the European Union | Do not use it to mean Europe; en-EU does not provide supported EU targeting in Google |
| US / en_US | A region alone / an underscore-separated value | Supply a valid language and hyphen-separated optional region |
The IANA Language Subtag Registry identifies eu, pt, BR, BZ and the Hans/Hant scripts. Google’s supported hreflang combinations remain the relevant implementation rule. A code can exist while being wrong for your business target. A generic language such as en is also useful when a page is intended for speakers across regions; a country suffix is not universally required.
Check self-reference and each return link
Each version should list itself and its corresponding alternatives using fully qualified URLs. In this fictional HTML example, an English page, a French page and a language selector each carry the same alternate set in a valid head:
<link rel="alternate" hreflang="en" href="https://example.com/en/widget">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/widget">
<link rel="alternate" hreflang="x-default" href="https://example.com/choose/widget">
The English page has its own English canonical and the French page its own French canonical; the selector’s canonical follows its actual page purpose. x-default identifies a fallback for unmatched languages, often a selector or suitable default page. It is not a mandatory extra tag whose absence invalidates every multilingual site.
If A points to B but B does not point back, Google may ignore that relationship. Its guidance also says remaining bidirectional relationships can still be processed when a complete network cannot be maintained. One missing return link is not evidence that every hreflang annotation across the website has failed.

The local check requested three responses for each of two variants. All returned 200. Every response in the complete set listed en, fr and x-default; the other variant omitted en only from the French response. The checker compared those saved annotations. It did not emulate Google’s crawl or its decision about the relationship.
Resolve canonical conflicts according to the content
A common conflict is a genuine French translation that identifies itself as the French alternative but declares the English page canonical. Check whether a template incorrectly treats the translation as an English duplicate. Google’s canonicalization guidance calls for a canonical in the same language, or the best substitute language when none exists. Near-duplicate regional pages in one language need a considered canonical strategy; “every page must always self-canonicalize” is too broad.
Align alternate URLs, canonicals, internal links and sitemaps. Keep canonical and alternate annotations separate rather than combining their attributes on one link element. Google evaluates the canonical choice: observing a declaration does not establish that it was accepted.
Inspect the returned document and the implementation source
- Fetch the full response. Preserve status, redirect hops and final content. A 200 login, challenge or error page is not the expected translation. A working redirect does not establish that the old alternate URL has been corrected everywhere.
- Review access and indexing controls. Check for accidental robots blocks and noindex directives on intended public versions. Keep deliberate restrictions on private content.
- For HTML annotations, inspect the head. Compare source HTML and rendered DOM; identify whether the CMS, theme or plugin owns the output. Conflicting duplicates need a source-level fix.
- Choose a maintainable method. Google also supports HTTP Link headers and XML sitemaps. Headers are useful for non-HTML files such as PDFs. The three methods are equivalent for this purpose; maintaining all three provides no search benefit by itself.
URL Inspection helps inspect indexed information, live responses and Google-selected canonicals. It is not a hreflang-success score or a guaranteed country-routing preview. The International Targeting report has been deprecated; its old language-error interface is not a current troubleshooting step.
Do not remove every parameter or canonicalize pagination to page one
A query string does not automatically invalidate an alternate URL. A tracking-parameter duplicate can use the preferred clean URL consistently. A parameter that materially changes content needs a separate decision. Avoid a blanket redirect that strips meaningful options, locale choices or pagination.
Google’s pagination guidance gives each page a unique URL and its own canonical, rather than treating page two as a duplicate of page one. Hreflang alternatives should match equivalent content; different ordering across languages can make equal page numbers a poor mapping. The Search Console URL Parameters tool was retired in 2022, so instructions to select “Paginates” there are obsolete.
Verify the repair in stages
- Save the original mapping and responses, then fix the actual template, CMS field or sitemap generator.
- Refresh relevant caches and refetch affected versions. Recheck self-reference, return links, final destinations, canonicals and the language of the main content.
- Follow language-switch links on desktop and mobile. Confirm that they reach the corresponding content without redirecting back unexpectedly.
- Where you have access, review later crawl and indexed information in Search Console. Keep “annotation fixed,” “recrawled” and “regional impressions observed” as separate records.
For a page missing from the index, use the GSC indexing investigation first. Guangsuan’s site-wide SEO service coordinates technical work, content and backlink resources when the issue spans a broader project. The Chinese hreflang guide covers the same checks.