What breaks when you canonical to a page that itself canonicals elsewhere?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 51
What breaks is the clarity of your instruction. Page A names B as canonical, B names C, and Google is left with two hints that disagree about which URL should represent the content. A canonical is a hint that Google weighs, not a forwarding rule, so a chain of them does not reliably resolve to C the way a chain of redirects resolves to its last URL. Google may settle on A, B, C, or a version you never declared.
Why chains behave differently from redirect hops
Google documents how its crawlers handle redirect chains, with a default limit on the number of hops they follow, in its HTTP status code documentation. Its canonicalization guidance makes no matching statement about canonical tags that point at other canonical tags. A canonical is read as part of canonicalization, where Google compares several signals for a group of duplicates and picks one URL to show. B pointing onward to C does not tell Google that A’s signals should travel through B; it tells Google that you have described B as both the main version and a copy.
The practical result is that the consolidation you set up may not happen where you expected. Links and other signals pointing at A, B, and C can end up attributed to whichever URL Google selects, and that may be one you meant to retire.
How to find chains on your own site
- Crawl the site with any crawler that reports the canonical URL of each page.
- For every page whose canonical points elsewhere, open the target and read its canonical.
- Flag any target whose canonical is not itself. Those are your chains.
- For important pages, inspect the URL in Search Console and compare your declared canonical with the Google-selected canonical in the indexed data. If they differ, Google has already made its own call.
The fix
Point every canonical straight at the final URL, the page whose own canonical references itself. If A, B, and C are all versions of the same content, A and B should both name C directly. Then make the rest of the site agree: internal links, sitemap entries, and any redirects should all lead to C. Google’s guidance on consolidating duplicate URLs asks for exactly that consistency, warning against naming different canonicals for the same page through different methods.
If Google keeps choosing another URL after the chain is gone, the remaining conflicts are the ones listed in why Google picks a different canonical than the one you set. And if B exists only because of an old move, redirect B to C instead of keeping it as a live page with a canonical: a redirect also takes visitors to the right place, which a canonical does not do.
Add a comment