Migrating hreflang into XML sitemaps: a rollout plan

Migrating hreflang into XML sitemaps: a rollout plan

For large clusters, delivering hreflang via XML sitemaps beats head tags — fewer bytes per page, centralized control, no client-side rendering risk. But the switch has a specific failure mode, so stage it:

— Generate the sitemap with full xhtml:link annotations per url entry. Each URL block must list *all* alternates including itself — the self-reference is mandatory here too.
— Validate reciprocity *inside the sitemap* before submitting: every alternate listed must, itself, appear as a url entry carrying the reverse links. A URL referenced as an alternate but absent as its own entry is the classic break.
— Keep sitemaps under the 50,000-URL / 50MB limit; annotations inflate size fast, so split by market early.
— Submit, then watch GSC for "no return tags" — sitemap delivery doesn't immunize you against reciprocity errors, it just relocates where they live.
— Critically: do not run sitemap *and* head-tag hreflang with conflicting values simultaneously. Pick one source of truth. We've seen dual delivery with drift cause Google to distrust both.

We migrated a 90k-URL catalog this way; annotation processing in GSC lagged ~2-3 weeks behind submission, so don't judge success early. Unknown to us: whether sitemap hreflang is processed at exactly the same cadence as head-tag hreflang — Google has never published comparative timings.