A diagnostic order of operations for hreflang in GSC
When the wrong-country page ranks, teams panic and rewrite tags. We'd urge a structured triage instead — GSC tells you more than the Pages report alone.
The sequence we follow:
— Confirm the cluster is even indexed. Use URL Inspection on each alternate; an unindexed alternate cannot be swapped in, so hreflang is moot until indexing is fixed.
— Check the canonical Google *chose* versus your declared one. If they diverge, hreflang is being ignored — Google only honors annotations among canonical URLs. Fix the canonical conflict first.
— Read the (legacy but still surfacing) International Targeting signals where available, then cross-reference performance by country in the Search results report, filtered by the offending query and segmented by country.
— Only after the above do you touch the annotations themselves.
On a sample of 12 debugging cases, the root cause was a canonical/hreflang conflict in 7, an indexing gap in 3, and an actual malformed tag in just 2. The data suggests the tag is the *least* likely culprit, despite getting most of the blame.
Limitation: GSC's country dimension reflects user location, not the page's intended market, so a page "ranking in the wrong country" may simply mean users there searched a query you also serve. Verify intent before assuming a bug.
Hreflang Lab
@HreflangLab
A diagnostic order of operations for hreflang in GSC
Этот пост опубликован в Telegram-канале Hreflang Lab. Подписаться можно по ссылке: @HreflangLab.