Guides
Hreflang 'No Return Tags' Error: What It Means & How to Fix
On this page
The hreflang “no return tags” error means one of your pages points to a language/region alternate, but that alternate doesn’t point back — and hreflang only works when the links are reciprocal. Think of it as a handshake: if page A says “my Spanish version is page B,” then page B must say “my English version is page A.” If B doesn’t return the reference, Google throws “no return tags” and may ignore your hreflang entirely. Here’s how to fix it.
Why hreflang has to be reciprocal
Hreflang tells Google which language or regional version of a page to show which users. To trust that relationship, Google requires confirmation from both sides. If only page A claims page B as an alternate, but page B never confirms it, Google can’t be sure the relationship is real (anyone could claim any page as their “alternate”). So it requires the return link as proof.
“No return tags” is Google saying: “Page A references this URL as an alternate, but that URL doesn’t reference page A back.” The relationship is one-directional, so it’s invalid.
What causes the “no return tags” error?
The common reasons a return link is missing or mismatched:
- You added hreflang to some pages but not their counterparts. The English page lists alternates; the Spanish page has no hreflang at all.
- The URLs don’t match exactly. A return tag pointing to
http://vshttps://,wwwvs non-www, or with/without a trailing slash won’t be recognized as the same URL. Hreflang matching is strict. - Missing self-reference. Each page in the set should also reference itself with its own hreflang. Omitting the self-reference breaks the set.
- Inconsistent language/region codes between pages (e.g.
enon one side,en-USon the other). - A page was added, moved, or deleted and its counterparts weren’t updated.
- Redirects or noindex on an alternate, so Google can’t confirm the return tag.
How to fix hreflang “no return tags”
- Make every relationship bidirectional. For each alternate a page declares, ensure that alternate declares this page back. If English → Spanish, then Spanish → English, always.
- Include a self-referencing hreflang on every page in the cluster — each page lists all versions including itself.
- Use identical, absolute, exact URLs on both sides — same protocol, same www/non-www, same trailing slash. Any mismatch breaks the pairing.
- Keep language/region codes consistent across the whole set (valid ISO codes, same granularity).
- Put the tags in one place consistently — either in the HTML
<head>, HTTP headers, or the XML sitemap — and don’t half-implement across methods. - Update the whole set when any page changes. Add, move or delete a page, and every counterpart’s hreflang must be updated too.
- Re-validate in Search Console (or with an hreflang testing tool) after fixing.
The mental model that prevents 90% of these errors: treat all language versions of a page as one group that must always reference each other identically, self included.
Does this hurt SEO?
Directly, only for international sites. Broken hreflang means Google may show the wrong-language version to users (hurting experience and conversions) or ignore your hreflang entirely — but it won’t tank your rankings site-wide. Still, if you’ve invested in multiple language versions, “no return tags” means that investment isn’t fully working, so it’s worth fixing. It’s part of the same technical-hygiene layer as canonicals and indexing directives — see noindex vs robots.txt disallow and duplicate without user-selected canonical if you’re cleaning up several Search Console warnings at once.
The bottom line
Hreflang “no return tags” is a broken handshake: your pages don’t mutually confirm each other as language alternates. Fix it by making every relationship reciprocal, adding self-references, and using byte-identical absolute URLs and consistent codes across the whole set. Get the group referencing itself cleanly and the error clears.
If clear technical answers help, I send them occasionally — subscribe below for those plus the free GEO Starter Checklist.
Related indexing issues: hreflang problems often surface alongside canonical ones — see ‘Duplicate, Google chose a different canonical’ and ‘Duplicate without user-selected canonical’ if your language variants are being merged.
Frequently asked questions
What does the hreflang "no return tags" error mean?
It means one of your pages references another URL as a language or region alternate, but that alternate does not reference the original page back. Hreflang must be reciprocal — both pages have to confirm the relationship — so a one-directional link is invalid and triggers this error.
How do I fix hreflang no return tags?
Make every hreflang relationship bidirectional (if A links to B, B must link to A), add a self-referencing hreflang on every page in the set, and use identical absolute URLs on both sides — same protocol, www and trailing slash — with consistent language/region codes. Update the whole set whenever any page changes.
Why does hreflang need return tags?
Google requires confirmation from both pages to trust that they are genuinely language alternates of each other. Without a return tag, only one side claims the relationship, which Google cannot verify, so it treats the annotation as invalid.
Does a hreflang error affect rankings?
It will not tank your rankings site-wide, but it can make Google show the wrong-language version to users or ignore your hreflang entirely, hurting international user experience and conversions. For multilingual sites it is worth fixing so your language targeting actually works.