Return-tag reciprocity: the bidirectional requirement people break

Return-tag reciprocity: the bidirectional requirement people break

Finding: "no return tags" is among the most reported hreflang errors in Search Console, and it stems from a property teams routinely under-appreciate — hreflang must be reciprocal.

The constraint. If page A declares page B as its fr alternate, page B must declare page A back. The confirmation has to be mutual or Google discards the link as unverified. One-directional annotations are treated as unreliable, on the reasonable assumption that a real cluster confirms itself from both ends.

Where reciprocity quietly breaks:

— Pages added to a cluster on one side but not back-referenced from the others
— A URL changes (slug edit, trailing slash) on one page but the alternates still point to the old address, so the return tag no longer matches
— Protocol or www/non-www mismatch makes A's reference to B and B's reference to A technically different URLs
— Mixed implementation: some pages declare via HTML, others via sitemap, and the sets drift apart

The fix: generate the cluster from a single source of truth so every member references every other member and itself, with byte-identical URLs.

Limitation we'll flag honestly: Search Console's return-tag report can lag, and a fixed cluster may show the warning for days after correction. We've seen warnings persist past a fix and clear on the next recrawl. Don't re-engineer a cluster that's already correct just because the report is stale — confirm against the live source first.