Should you remove hreflang from noindex or redirecting pages?

Why does Google ignore these pages in hreflang?

Google's logic is simple: hreflang is meant to indicate indexable alternatives for the same content in different languages or regions. If a page is noindex, it shouldn’t appear in the SERPs — so why should Google consider it a valid alternative?

Similarly for redirects. A page that redirects is not a final destination. Google follows the redirection and evaluates the destination page, not the intermediate URL. Including these URLs in your hreflang annotations is like giving instructions about pages that don’t really exist.

What does it change for understanding international signals?

In a clean hreflang cluster, each URL must be indexable, accessible with a HTTP 200 status, and point reciprocally to its alternatives. If one of the URLs in the cluster is noindex or redirects, the cluster becomes shaky — Google may decide to ignore all annotations or keep only the valid URLs.

This also means that if you have set a language version to noindex because it is unfinished but left it in the hreflang "for later", Google will never see it as an alternative. You’re creating confusion for nothing.

How does Google handle incomplete hreflang clusters?

When Google encounters a cluster where some pages are noindex or redirecting, it mentally reconstructs a "clean" cluster by excluding those URLs. The risk is that it no longer understands the intended structure — especially if multiple pages in the cluster are invalid.

In the worst-case scenario, Google might consider that the hreflang is poorly implemented and completely ignore your annotations, relying on its own signals (server geolocation, content language, ccTLD). You then lose control over geographical and linguistic targeting.

• Noindex or redirecting pages are excluded from the hreflang cluster — Google ignores them in the chain of alternatives.
• A hreflang cluster must only consist of indexable pages with HTTP 200 status — any invalid URL weakens understanding.
• Google may ignore all annotations if the cluster is too degraded — it's better to have a clean hreflang than a polluted one.
• Redirects are followed, but the intermediate URL doesn't count — only the final destination can be considered.
• Regularly cleaning your hreflang annotations is essential — especially after migrations, site merges, or page deletions.

Is this rule consistent with real-world observations?

Totally. In practice, we regularly see sites with hreflang clusters polluted by noindex URLs or orphaned redirects. The result: Google serves the wrong language version, or worse, completely ignores hreflang and relies on IP geolocation.

What’s less documented is Google's tolerance: how many invalid URLs in a cluster does Google tolerate? Mueller doesn’t specify. On sites with 50+ languages, we’ve observed that if 2-3 URLs out of 50 are noindex, Google continues to process the cluster — but with sporadic errors. [To be verified]: the exact threshold of acceptable degradation.

What nuances should be added to this statement?

First point: Google "ignores" these pages, but it does not penalize the rest of the cluster — at least theoretically. In practice, a poorly structured cluster can lead to a loss of trust in your annotations, and Google may choose to rely on its internal signals rather than your hreflang.

Second nuance: temporary redirects (302) versus permanent (301). Mueller does not differentiate, but in practice, a 301 is more likely to be "understood" by Google as a true redirect, while a 302 can create ambiguity. In both cases, the source URL is ignored in hreflang.

In what cases does this rule pose problems in practice?

Classic case: e-commerce sites with deindexed category pages to avoid cannibalization, yet left in hreflang "just in case". Problem: Google never sees them as valid alternatives, and users land on the wrong language.

Another scenario: poorly managed international site migrations. You redirect old URLs → new URLs, but leave the old ones in hreflang for months. Google follows the redirect but does not consider the old URL in the cluster — and if the new is not in hreflang, the link is broken.

What should be done concretely to clean up hreflang?

First action: crawl all your URLs present in your hreflang annotations (HTML tags, HTTP headers, XML sitemap) and check their HTTP response code. Any URL in 301, 302, 404, 410, or with a noindex tag must be removed.

Then, check the reciprocity of annotations. If the FR page points to the EN page via hreflang, the EN page must point back to the FR page. If either one is invalid, the cluster is broken. Use a script or a tool (Screaming Frog, OnCrawl, Botify) to detect asymmetries.

What errors should absolutely be avoided in managing hreflang?

Error #1: leaving noindex URLs in hreflang "just in case". This serves no purpose — Google ignores them. If a page isn't ready, don't put it in the cluster. Wait until it's indexable.

Error #2: failing to update hreflang after a redirect. You redirect /fr/ancien-produit → /fr/nouveau-produit, but leave /fr/ancien-produit in hreflang. Google follows the redirect but does not consider the old URL — and if the new one is not annotated, you lose the link.

How to ensure that implementation remains clean over the long term?

Set up automated monitoring. Crawl your hreflang pages every week and alert if any error URLs appear. You can also cross-reference your server logs with your annotations: if Googlebot crawls a hreflang URL that returns a 301 or a noindex, you have a problem.

Another good practice: document your hreflang management rules in an internal runbook. When a developer deletes a page or implements a redirect, they need to know that they must also update hreflang. Otherwise, you’re accumulating invisible technical debt.

This type of audit and maintenance can quickly become time-consuming on complex multi-language sites. Hiring an SEO agency specializing in international SEO allows you to benefit from advanced monitoring tools and tailor-made support to ensure the consistency of your hreflang annotations over time.

• Crawl all the URLs present in your hreflang annotations and check their HTTP code and indexability
• Immediately remove any URL in noindex, 301, 302, 404, or 410 from the hreflang cluster
• Check the reciprocity of annotations: each page must point to its alternatives and be pointed back
• Implement automated monitoring to detect errors as soon as they appear
• Document hreflang management rules in an internal runbook for technical teams
• Audit hreflang after each migration, redesign, or deletion of important pages