Hreflang return link failures by platform
| Platform | Alternates followed | No return link | Sites | Sites with a broken pair |
|---|---|---|---|---|
| Shopify | 2,762 | 2.4% | 1,311 | 2.9% |
| WordPress | 1,512 | 9.0% | 788 | 9.5% |
| Wix | 69 | 5.8% | 35 | 5.7% |
| Other or custom | 5,803 | 14.5% | 2,451 | 18.0% |
| All | 10,167 | 10.3% | 4,596 | 12.1% |
Source: PageSpeed Matters, Oct 2026. Up to 3 alternates checked per homepage; Wix figures rest on 35 sites.
Summary
Hreflang only works in pairs. If your English page names a French version, the French page has to name the English one back. Google's documentation is clear that when two pages do not point to each other, it may ignore the tags, so a broken return link quietly undoes the setup for that pair.
We tested this on multilingual sites that rank in Google's top 20 for US searches. We followed 10,167 hreflang alternates on 4,596 ranking sites: 10.3% of the alternate pages don't point back to the original, and 12.1% of sites have at least one broken return link. Shopify stores almost never get it wrong; custom builds get it wrong most.
What we measured
We started from the domains ranking in Google's top 20 for 10,019 US searches, and followed hreflang alternates on 4,596 of the sites with hreflang on the homepage. For each homepage we fetched up to 3 of its alternates and checked whether each alternate lists the original homepage in its own hreflang tags. The data was collected in October 2026.
Matching is strict on scheme, path and query, but ignores www, host case and trailing slashes, so small formatting differences do not count as failures. Because we only checked homepages and up to 3 alternates each, this is a homepage-level sample, not a full site audit. A site with a clean homepage can still have broken pairs deeper in.
One in ten alternates doesn't link back
Of the 10,167 hreflang alternate pages we followed, 10.3% don't point back to the original page. Under Google's rules, each of those breaks the pair.
At site level, 12.1% of the 4,596 multilingual sites have at least one broken return link. A smaller share of failures happen before the return check even starts: 1.6% of alternates don't return a 200 at all, so the alternate URL is redirected, missing or erroring.
In some cases the return link is not wrong but absent. 177 of the 10,167 alternates (1.7%) carry no hreflang tags at all. That likely means a language version was added to the homepage's list but the template for that version never got its own tags.
12.1%
Share of the 4,596 multilingual ranking sites with at least one hreflang alternate that does not link back to the original page.
Shopify sites almost always close the loop
Platform makes a large difference. Only 2.4% of 2,762 Shopify alternates fail the return check, and 2.9% of 1,311 Shopify sites have a broken pair. On WordPress, 9.0% of alternates fail and 9.5% of 788 sites have a broken pair. On custom or other platforms the rates are highest: 14.5% of alternates and 18.0% of 2,451 sites.
The likely reason is who writes the tags. Shopify generates hreflang for every language and market version from one setup, so each version lists the others by default. On WordPress the tags depend on a translation or SEO plugin, and on custom builds each template has to get them right on its own.
Publishers break pairs most
Publishers and how-to sites break hreflang pairs most often: 13.1% of 2,525 alternates fail, and 16.6% of 1,083 sites have at least one broken pair. Local and professional service sites follow at 13.2% of sites, then online stores and product sites at 10.4%. Software and marketing sites do best, with 8.1% of 2,084 alternates failing and 8.9% of sites affected.
Publishers may struggle because their language editions are often run as separate editorial sites, with their own templates and teams, rather than as translations of one site.
Cross-domain alternates fail slightly more often
Alternates on a separate domain or subdomain fail the return check slightly more often than same-host language folders: 10.9% of 2,364 against 10.1% of 7,803. They also return a non-200 status more often, 2.2% against 1.4%.
The gap is small, but the direction makes sense. A separate domain is often a separate deployment, so its templates, redirects and hreflang setup can drift from the main site without anyone noticing.
What this means for your site
Treat hreflang as a set that every version has to repeat. Open each language version of your homepage and key templates, and check that:
- Every alternate URL returns a 200 directly, with no redirect.
- Every alternate lists every other version, including the one you started from, with the exact same URL, protocol and path.
- Each version also lists itself.
On a custom build, generate hreflang from one shared list of locales and URLs, so adding a version updates every page at once. If language editions live on separate domains, include them in the same check after every release. Most site crawlers can report missing hreflang return tags across the whole site, well beyond the homepage sample we tested.
Sources
- PageSpeed Matters analysis of Google top 20 results for 10,019 US searches, October 2026
- Google Search Central, localized versions of your pages: https://developers.google.com/search/docs/specialty/international/localized-versions
Frequently asked questions
What is an hreflang return link error?
It is when page A lists page B as a language alternate, but page B does not list page A back. Google expects the tags to point both ways and may ignore a pair that does not.
How common are hreflang return link errors?
We followed 10,167 alternates on 4,596 ranking sites. 10.3% of the alternate pages did not point back to the original, and 12.1% of sites had at least one broken return link.
Which platforms have the fewest hreflang errors?
Shopify. Only 2.9% of 1,311 Shopify sites had a broken pair, against 9.5% of 788 WordPress sites and 18.0% of 2,451 sites on custom or other platforms.
Broken hreflang pairs usually trace back to one template or one missing locale, and fixing them lets each language version show to the right searchers. Need help with this? See our technical SEO services.