<b>noindex inside an hreflang cluster poisons it</b>

<b>noindex inside an hreflang cluster poisons it</b>

A contradiction that quietly degrades clusters: including a <code>noindex</code> page as an alternate. The two directives express opposite intents, and the conflict propagates.

The logic of the failure:

— hreflang says "this is a valid, serveable alternate — index it and show it to the right users."

— <code>noindex</code> says "do not index this page at all."

A page that is both an hreflang alternate and noindexed is contradictory. Google resolves it by honoring noindex — the page drops from the index — but the <i>other</i> cluster members still point to it. Their annotations now reference a non-indexable URL, which can weaken reciprocity confirmation for the whole set, not just the noindexed page.

Where this happens in the wild:

— Staging or thin locale pages left in the cluster's alternate list while noindexed "until they're ready."

— Faceted or paginated variants that are noindexed but still emit the cluster's shared hreflang block from a global template.

— A locale being sunset: someone adds noindex but forgets to remove it from the other pages' alternate lists.

The rule: if a page shouldn't be indexed, it shouldn't be in the hreflang cluster — remove it from every other page's alternate list at the same time you noindex it. The two changes are one operation.

Caveat: the cluster won't always collapse — Google may tolerate one bad node — but you've introduced a contradiction that makes the cluster's state ambiguous, and ambiguity is exactly what you're trying to eliminate with hreflang.