Hreflang is not set-and-forget: monitoring annotation decay

Hreflang is not set-and-forget: monitoring annotation decay

A correctly deployed hreflang setup degrades over time on any active estate. The interesting question is what specifically rots, so you know what to monitor.

Methodology: we tracked annotation health on five estates over 12 months without deliberate hreflang changes, logging when entries broke and why.

The decay vectors, by what we observed:

— Page retirement. A locale page is unpublished or 404s, but its alternates still point to it. Now every page in the cluster has a broken return tag pointing at a dead URL.

— URL changes from CMS slug edits. Someone renames /de/produkt to /de/produkte; the other locales still reference the old slug.

— New locale launches that aren't retro-added to existing clusters' annotations, creating one-way references.

— Canonical regressions from unrelated template deploys (see the canonical-conflict failure mode), which break clusters as collateral.

Nuance: none of these throw an immediate alert; they surface in Search Console's International Targeting report on a lag of days to weeks.

Caveat: the report itself lags crawl, so 'zero errors today' can mean 'not re-validated yet,' not 'healthy.'

Limitation: five estates, and the teams' editorial velocity varied, which affects decay rate.

Conclusion: treat hreflang as a living system. Build an automated reciprocity check against your live sitemap on a schedule — don't wait for the lagging report to tell you a cluster broke three weeks ago.