Sitemap hreflang done halfway is worse than none
The XML sitemap method is excellent for large multilingual sites — and the most common way we see it fail is partial implementation.
Methodology: the sitemap approach requires that every URL in a cluster appear with the complete set of xhtml:link alternates, including its own self-reference, inside its own <url> entry. It's verbose by design — an N-locale cluster repeats the full alternate block N times.
The failure patterns:
— Listing alternates only on the "main" language URL and omitting the reciprocal blocks on the others — this breaks return-tag confirmation
— Generating the sitemap from one language's database and silently dropping locales that lack a translation, leaving asymmetric clusters
— Mixing methods: hreflang in the sitemap for some pages and in HTML head for others, with the two sources disagreeing
The fix: one generator, one source of truth, producing symmetric blocks per URL. Pick HTML head or sitemap and don't split the cluster across both.
An under-appreciated advantage worth noting: the sitemap method keeps page weight down and is far easier to audit programmatically than scattered <head> tags — you can diff the alternate sets across entries in one pass.
Limitation: a sitemap hreflang is only as fresh as your last submission and recrawl. If URLs change faster than the sitemap regenerates, the annotations go stale. For volatile catalogs, weigh that latency against the verbosity savings.
Hreflang Lab
@HreflangLab
Sitemap hreflang done halfway is worse than none
Этот пост опубликован в Telegram-канале Hreflang Lab. Подписаться можно по ссылке: @HreflangLab.