The tags have to be mutual, and a one way declaration is ignored. Wrenbury Ropes makes climbing and sailing rope in Cheshire and runs three English versions of its shop, for Britain, Ireland and the United States. From March 2025 the Irish and American pages pointed at the British ones and the British pages pointed at nothing, and eleven months of tags that did nothing, with no error anywhere.
Nothing broke. Every page loaded, every tag validated, and the arrangement was simply discarded, because a declaration that is not returned is treated as a claim somebody made about a page that has not agreed to it.
The arithmetic of a set
Every page in a set lists every page in the set, itself included. The self reference is the part that gets left out and it is not optional: a page that names the other two and not itself is an incomplete set, and incomplete sets are dropped.
Hreflang
Three versions that only work when all three turn
Each wheel has to name the other two and itself, and a wheel that names nobody stops the whole train rather than only itself.
- en-GB
- en-IE
- en-US
- en-GBNamed the other two from February 2026. Before that it named nobody.
- en-IENamed Britain and itself from March 2025, and was ignored for eleven months.
- en-USSame declaration, same silence, and a shop in Cork quoting pounds.
The train also carries x-default, which is not a wheel: it names who gets served when a visitor is in none of the three, and at Wrenbury that is the British shop.
Three versions means three tags on each of three pages, which is nine, and a shop with 400 products in three regions is maintaining 3,600 declarations. That number is the argument for generating them rather than writing them, and it is the reason this is a template job and never an editorial one.
Reading a code
en-GB, en-IE and en-US are three regions of one language, which is the case that makes hreflang worth having at all for a firm that has not translated anything. The pages differ in price, in delivery and in one spelling, and without the tags the engine picks one of the three for everybody and usually picks the one with the most links.
Region codes
Valid regional tags against the mistake that gets discarded
The second part of an hreflang tag is a country code, not a colloquial name, and one wrong code drops the tag outright.
English regional tag check
- Yesen-GB (Britain)Official country code for the United Kingdom.Yes
- Yesen-IE (Ireland)Routes Irish visitors to euro pricing and local shipping.Yes
- Yesen-US (United States)Routes US visitors to dollar pricing and spelling.Yes
- Yesx-default (Unlisted regions)Deliberate fallback for visitors outside GB, IE, and US.Yes
- Noen-UK (Invalid code)Not a valid ISO country code; ignored with no partial match.No
Without valid tags and x-default, search engines pick whichever regional page holds the most links for every country.
The region code is a country, not a language, and it comes second. en-UK is wrong and is the commonest error in the whole subject, because the country code for Britain is GB and UK is not a code at all. A wrong code is not a partial match; the tag is discarded.
x-default names the page for everybody the set does not cover. Wrenbury's x-default points at the British shop, which is a decision about who gets served when a visitor is in Portugal, and it is better made deliberately than by whichever version happens to win.
Where this stalls: the fault with no report
Nothing anywhere says that a set is incomplete. The pages are valid, the tags are well formed, the site works, and there is no line in any report reading these declarations were ignored. Wrenbury found it because somebody in Cork mentioned being sent to a page quoting pounds, which is a customer complaint rather than a diagnostic.
Silent failure
Why missing return links never trigger an error report
Pages load and tags validate on the surface, while incomplete sets are quietly discarded underneath for months.
- Every URL returns 200 OKRegional shops load cleanly for visitors and crawlers.
- Syntax passes HTML checksOne-way declarations look valid in page source.
- Unconfirmed claims ignoredWithout mutual return links, the whole set is dropped.
- Wrong currency servedShoppers in Cork land on British pages quoting pounds.
- Months pass unnoticedOnly a customer complaint exposes the slow country drift.
A hard error gets fixed in a fortnight; a silent discard ran for eleven months while everyone assumed hreflang was working.
The stall is worse than an error would be. An error gets fixed in a fortnight; a silent discard runs for eleven months while everybody involved believes the arrangement is working, and the only evidence is a slow drift of the wrong version appearing in the wrong country.
Where to put them
Put them in the head or in the sitemap, and never in both. The head is simpler to reason about and costs bytes on every page; the sitemap keeps the pages clean and puts all 3,600 declarations in one file that a template generates. Both work, and a site with tags in both places has two sources of truth that will disagree within a quarter.
Implementation
Put declarations in the page head or the sitemap, never both
Maintaining hreflang in two places guarantees they will drift apart within a quarter.
- Small site, simple templatesEmit tags in the HTML headEasy to inspect per page, at the cost of extra bytes on every response.
- Generate from one template source
- Keep sitemaps free of duplicate tags
- Large catalogue (3,600 tags)Generate them in one XML sitemapKeeps HTML clean and turns nine head tags per product into three rows.
- Output all region links in one file
- Strip head tags so one source of truth remains
Wrenbury moved all 3,600 declarations to a generated sitemap in one afternoon, removing every hreflang tag from page HTML.
Wrenbury moved to the sitemap in February 2026, which took an afternoon and turned nine declarations per product into three rows in a generated file. The pages themselves now carry none.
What it is and is not for
Hreflang picks which version to show, and does not make either rank. It is a swap rather than a lift: the set is already competing as one thing, and the tags decide which member of the set is put in front of which visitor. A firm expecting three versions to rank three times has misread what the arrangement does, and it is closer to naming the real version of a duplicated page than to anything that adds.
Role and checks
Hreflang swaps which version appears; it adds no ranking power
Think of hreflang as routing the right member of one competing set rather than creating three separate chances to rank.
- What it changesMatches the right regional page to each country.
- Swaps en-GB, en-IE, and en-US per country
- Checked in Screaming Frog missing return links
- Tracked by country in Search Console Performance
- What it never addsDoes not multiply ranking strength or authority.
- Does not make three versions rank three times
- Adds no link equity across regions
- No Search Console targeting report since 2022
What hreflang changes vs what stays fixed
With Search Console's international targeting report retired in 2022, Screaming Frog catches missing return tags while country filters show the result.
Screaming Frog SEO Spider reports hreflang declarations per address and flags the ones without a return tag, free up to a few hundred addresses, and it replaced reading the head of each page in three regions by hand. Its missing return links report is the whole diagnosis and it takes four minutes.
Search Console removed its international targeting report in 2022, so as of 2026 there is no first party report for this, which is worth knowing before hunting for one. It remains free and it is where the consequences show up, in the queries and countries tabs of the performance report, one country at a time.
Which of the three versions is fetched at all is what to let bots see, and what to keep out, the file carrying the declarations is listing what you want indexed, and the whole arrangement is part of the layer that decides whether any of the rest counts.