The self-referential tag everyone forgets
The single most common failure mode we encounter in hreflang audits isn't a typo — it's an omission. A page lists every other language variant but never references itself.
The spec is explicit: each URL in a cluster must include a tag pointing to itself. A page at /en-gb/shoes needs an en-gb entry in its own annotation set. Omit it, and Google's documentation states the annotations may be ignored entirely — not partially, entirely.
Why this happens:
— Teams build a template that loops over "alternate" locales and excludes the current one as redundant
— CMS plugins that inject tags server-side sometimes treat self-reference as a no-op
— The page looks correct because the cross-references all resolve
The fix is trivial once diagnosed: include the current URL in its own hreflang block. In a 6-locale cluster, every page carries 6 tags, not 5.
A caveat worth flagging: we cannot reliably quantify how often missing self-reference alone causes mis-serving, because it rarely appears in isolation — it usually co-occurs with return-tag gaps. What the data does suggest, from clusters we've corrected, is that adding self-reference resolves a meaningful share of "no return tags" warnings in Search Console, since the two are mechanically linked. Audit the self-tag first; it's the cheapest thing to verify and the most frequently broken.
Hreflang Lab
@HreflangLab
The self-referential tag everyone forgets
Этот пост опубликован в Telegram-канале Hreflang Lab. Подписаться можно по ссылке: @HreflangLab.