Hreflang return-tag errors
The hreflang return-tag rule requires that every URL in a language cluster references every other URL, and that each referenced URL points back. A missing back-reference is a no-return-tag error, which invalidates that pairing and is reported in Search Console. This page explains reciprocity, self-referencing, single-method consistency, and how to find and fix return-tag problems.
What this means
hreflang annotations only work when they are reciprocal. If page A declares page B as its German alternate, then page B must declare page A as its alternate too — the return tag. Every URL in the cluster must list every alternate, including itself (self-reference) and x-default if used.
When a return tag is missing, the relationship is one-directional and unconfirmed. Search Console reports this as a no-return-tag (or no-return-link) error, and Google may disregard the annotation for that pair.
Common causes of return-tag errors
Frequent causes include: forgetting to add the reciprocal annotation on the alternate page, inconsistent URL forms between the outgoing and return references (http vs https, www vs non-www, trailing slash), pointing to a URL that redirects or 404s, and mixing declaration methods so the cluster is partly defined in HTML and partly in a sitemap.
Language and region code mismatches also break pairs — the value must be a valid ISO language code, optionally with a region, and both directions must use matching annotations.
- Missing reciprocal annotation on the alternate page
- Inconsistent URL form (protocol, host, trailing slash)
- Alternate URL redirects or 404s instead of returning 200
- Mixed declaration methods (HTML + sitemap) within one cluster
Diagnosing and fixing
Map the full cluster: list every locale URL and verify each one references all the others plus itself, using identical absolute URLs in both directions. Ensure each referenced URL returns 200 (no redirect or error), and that you use a single declaration method consistently.
Use a crawler or hreflang validator to surface non-reciprocal pairs, and check Search Console for hreflang errors. Fix by adding the missing return tags, normalizing URL forms, and removing references to non-200 URLs, then recrawl to confirm the errors clear.
How it appears in analytics and logs
A no-return-tag error means page A points to page B with hreflang, but B does not point back to A. Google then cannot confirm the relationship and may ignore the annotation for that pair, so the intended localized URL may not be served. It does not block crawling.
Diagnostic use case
Diagnose and fix hreflang clusters where annotations are not reciprocal, so language and region targeting works and Search Console stops reporting no-return-tag errors.
What WebmasterID can help detect
WebmasterID records which crawler fetched which localized URL and the response, helping you confirm that every variant in a cluster is reachable and returns 200 — a prerequisite for valid, reciprocal hreflang annotations.
Common mistakes
- Adding hreflang to page A but forgetting the reciprocal tag on page B.
- Using different URL forms (https vs http, www vs non-www) in the two directions.
- Referencing a localized URL that redirects or 404s instead of returning 200.
- Defining part of a cluster in HTML and part in a sitemap.
Privacy and accuracy notes
hreflang reciprocity concerns relationships between localized URLs, not visitors. Any region context is a coarse edge estimate, never an exact location. WebmasterID records crawler fetches of the variants as bot events only.
Frequently asked questions
- What is a no-return-tag hreflang error?
- It means one page references another as an hreflang alternate, but that other page does not reference back. The relationship is one-directional, so Google cannot confirm it and may ignore the annotation for that pair.
- How do I fix hreflang return-tag errors?
- Ensure every URL in the cluster references every alternate plus itself, using identical absolute URLs in both directions, all returning 200, declared with a single consistent method. Then recrawl to confirm the errors clear.
Related pages
- The hreflang x-default value
x-default is a special hreflang value that names the page to serve when no other language or region annotation matches the user. It is the fallback in an hreflang set — often a language selector, a global homepage, or a generic version. This page covers when x-default is appropriate, how it interacts with the rest of the cluster, and the return-tag and self-reference rules that keep it valid.
- Diagnosing hreflang errors
hreflang annotations tell search engines which language and regional URL to show to which users. They are easy to get subtly wrong: return tags that are not reciprocal, invalid language or region codes, hreflang pointing at non-canonical or redirecting URLs, or a missing self-reference. These errors cause search engines to ignore the cluster, so the wrong-language page can surface for users.
- Canonical tag best practices
The rel=canonical annotation tells search engines which URL is the preferred version of duplicate or near-duplicate content, consolidating signals onto one URL. It is a strong hint, not a directive — Google may choose a different canonical if other signals disagree. This page covers correct implementation: self-referencing canonicals, absolute URLs, consistency with sitemaps and internal links, and the mistakes that send conflicting signals.
- Web crawler reference
Identify which crawlers fetch each localized URL in your cluster.
Sources and verification notes
- Google Search Central — Localized versions (hreflang requirements)Reciprocity, self-reference, and single-method rules.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.