<b>noindex vs hreflang: why they cancel each other out</b>

<b>noindex vs hreflang: why they cancel each other out</b>

A frequent self-inflicted wound: pages that carry both hreflang annotations and a noindex directive. They are logically incompatible, and the interaction surprises teams.

The mechanics:

— hreflang only operates between indexable pages. If a page in the set is noindexed, Google drops it from the cluster — and crucially, a noindexed page cannot supply the return tag the others need, so it can degrade reciprocity for the whole set.
— A common origin is staging or thin localized pages set to noindex 'temporarily' while still declared as hreflang alternates. The cluster then references a ghost.

What the data suggests:

— Either a locale is real and indexable and belongs in hreflang, or it is not ready and should be removed from the annotations entirely — not noindexed while still referenced.
— Half-finished translations are better left out of the cluster than included-but-noindexed.

The comparison that matters: removing a not-ready locale from hreflang is clean; keeping it in with noindex is a contradiction Google resolves by ignoring the relationship.

Our rule: hreflang sets contain only indexable, self-canonical, 200-status pages. Anything else, exclude it. Caveat — there is no penalty for the mismatch, only lost functionality, which makes it easy to overlook in audits that check noindex and hreflang separately.

—
Продолжение про 301 redirect mapping — @MigrationHelpdesk