When a hreflang target redirects or returns 404, identify the intended language page before replacing the URL. A redirect may lead to the correct replacement, a different product or a generic homepage. Reaching 200 is only the start of the check; the final content and return relationship must also fit.
Ahrefs’ “Hreflang to broken page” issue flags targets that do not return 200. That is a tool’s issue definition, not proof that Google discarded every language relationship or that the entire page must be rewritten.
Record the declared URL and the final result separately
For one logical product, article or service, collect the actual language/region variants. Keep the source URL, hreflang code, declared target, first status, redirect hops, final URL, final status, visible content, canonical, indexing controls and return annotations.
Fetch an ordinary page response and read the body, rather than relying only on a HEAD request or a tool label. Record the request time and access conditions. A login page or empty response can return 200 without providing the intended translation.
| Observed result | What to check | Appropriate next action |
|---|---|---|
| 301/308 to the correct equivalent | Language, product/version and final preferred URL | Keep the useful old redirect; update controlled alternate references |
| Redirect to a homepage or different item | Whether a real counterpart still exists | Restore or identify the correct counterpart; do not blindly copy the final URL |
| 404/410 | Typo, path encoding, removal decision and any equivalent replacement | Correct the error, restore the intended page or remove an unavailable alternate as appropriate |
| 403 or login | Access policy and whether the crawler/request was blocked | Investigate access; one failed request does not prove permanent deletion |
| 429, 5xx or timeout | Rate limit, service incident and reproducibility | Record and investigate/retry appropriately; do not treat a transient failure as a retired language |
Google’s HTTP-status guidance distinguishes successful responses, redirects, client errors and overload/server failures. A successful response does not guarantee indexing. Separately, Google’s redirect guidance explains permanent and temporary moves; do not change a deliberate redirect’s meaning merely to satisfy an audit counter.
A small example: keep the redirect, repair the annotation
Fictional example on example.com: the English product is at /en/model-a/. Its French counterpart moved from /fr/old-a/ to /fr/model-a/, and the old address now returns a deliberate 301 to the new one.

After confirming that the new French URL is the correct live counterpart, change the hreflang reference to https://example.com/fr/model-a/. Check that the French page returns the appropriate reference to https://example.com/en/model-a/ and that the implemented sets include the necessary self-references. Update other affected language members and controlled internal links or sitemap entries. Retain the old redirect for existing visitors and links.
If the French content no longer exists and there is no useful equivalent, do not substitute the English homepage just to obtain 200. Decide whether to restore the French page or remove the unavailable alternate from the affected sets.
Read the hreflang rules with their exceptions
Google’s localized-version guidance treats HTML tags, HTTP Link headers and sitemap annotations as equivalent implementations. Use the method actually deployed. If more than one method exists, compare their output; a missing head tag is not proof that sitemap-based annotations are absent.
- Use fully qualified URLs, including scheme and host.
- Specify the page itself and its corresponding alternatives, with return relationships. Google also documents that where full sets are difficult to maintain, it can process reciprocal subsets; newly expanded languages should link bidirectionally with the originating or dominant languages. A missing pair does not justify declaring every relationship invalid.
- Check supported language, optional region and applicable script values. For example, en-GB targets English in the UK; en-UK is not the supported equivalent. zh-TW indicates a region, while zh-Hant explicitly indicates a script; they are not interchangeable business targeting decisions.
- Consider x-default for an appropriate unmatched-language fallback. Its absence does not establish that unmatched users cannot receive a result.
Google may discover language variants even without annotations. Correct markup helps state the relationship explicitly; it is not a mechanism that guarantees a particular result for every user.
Check canonical and content without forcing every variant into one URL
Canonicalization concerns duplicate or very similar pages. Do not collapse complete translations into one source-language homepage simply because they cover the same product. Equally, a same-language regional setup with a preferred duplicate URL needs an intentional canonical and hreflang arrangement, not an automatic “every URL must self-canonicalize” rule.
Confirm visible language and market-specific facts, not only the folder name. A tag cannot correct an untranslated body, incompatible product configuration or wrong regional terms.
Recheck the affected group after publishing
- Save the original mapping and document why each target changes.
- Fix the responsible template, plugin setting, sitemap or header source, rather than patching one generated copy.
- Check every affected member and return reference, including cached public responses.
- Verify the language switch and relevant internal paths on desktop and mobile.
- Use URL Inspection where authorized to distinguish live accessibility from the stored indexing record. Keep later search observations separate from the technical repair.
For plugin selection and unpublished-translation behavior, see the WordPress multilingual checklist (Chinese). For broader visibility problems, use the ranking diagnosis; Guangsuan’s SEO service covers the content and technical work needed around the actual site.