<b>Partial hreflang rollouts behave worse than no hreflang at all</b>

<b>Partial hreflang rollouts behave worse than no hreflang at all</b>

Hypothesis: annotating only part of a multilingual estate is not a safe incremental step — it can actively degrade the pages left out.

Methodology: we observed three estates rolling out hreflang section-by-section (blog first, then product, then support) and tracked the un-annotated sections during the transition.

Findings:

— Within annotated clusters, correct-locale swapping appeared as expected.

— Un-annotated equivalents that shared substantial copy with annotated pages saw increased cross-locale duplicate filtering. By cleanly disambiguating some clusters, you make the remaining ambiguous ones look comparatively more duplicative.

— Mixed clusters — where /en/ was annotated but /de/ wasn't yet — created one-directional references that read as broken reciprocity, the worst of both states.

Nuance: this is an argument for rolling out hreflang by complete cluster, not by site section. Annotate every alternate of a given page in the same deploy, even if you cover fewer pages per release.

Caveat: small estates rarely see this because their total duplicate surface is low; it bites at scale where near-duplicate localized templates are common.

Limitation: we couldn't fully separate the rollout effect from concurrent content changes on two of the three estates.

Conclusion: scope hreflang rollouts by cluster completeness, never by page type. A half-annotated estate sends contradictory signals on exactly the pages most prone to confusion.