A canonical points to a page that points elsewhere
In the reportCanonical chain
canonical_chain · Review item
This appears when a page names another page as its canonical, and that page names yet another address as its own canonical. The two declarations form a chain. Check which address you intend as the main one, then point the pages straight at it.
Severity: Medium. Review the declared addresses and choose the intended main page; this observed chain is a review item, not proof of an indexing failure.
Why it matters
A canonical is a strong signal for which address should be shown. The canonical link standard asks not to name, as a canonical, an address that itself declares a canonical to another address, and lets search engines ignore canonicals declared improperly.
What to do
- Look at the finding: it shows the named page, the canonical it declares and the pages that name it.
- Check that the onward address works and is the one you intend as the main one; if it is, change the canonicals on those pages to it.
- Or, if the named page is the right one, let it name itself.
When to leave it as it is: A short-lived chain during a planned move may be intentional. Review it again when the move is complete.
What we read
We group admitted source pages by the single other address on your site that they declare as canonical. The target must have an observed direct HTTP 200 response and one complete canonical declaration pointing to a different address. An observed two-page return is handled as a loop.
The target observation comes from the retained crawl or the existing bounded canonical-target probes. We reuse any retained observation of its next address to test for a return; this rule adds no fetch for that next address. An unread next address does not erase the target’s proven onward declaration, but it leaves the loop check inconclusive.
Example & evidence
Illustrative example — two canonical tags in a row, not a live audit.
https://bakery.example/cakes/chocolate-cake/print/ declares:
<link rel="canonical" href="https://bakery.example/cakes/chocolate-cake/">and https://bakery.example/cakes/chocolate-cake/ answers 200 with:
<link rel="canonical" href="https://bakery.example/shop/chocolate-cake/">The named page points onward, so it is reported with the canonical it declares and the print page that names it.
A possible correction: if https://bakery.example/shop/chocolate-cake/ works and is the intended main version, let the print page name it directly.
Confirm & check again
Check for yourself: Open the address named in the canonical and read its own canonical. If it names a third address, check that address too before choosing the main version.
Check again: Full audit — Run a new site audit. The finding keeps the same target URL when its source pages change. It can close after a sufficient clean recheck of that target, or after a complete recheck proves that its previous source pages no longer name it. An unread target, an incomplete canonical declaration or unread previous source pages cannot prove a fix. A chain at another target URL is a separate finding; dismissal remains a separate judgment.
Limits & sources
Only observed server declarations are read. A cycle of three or more pages appears as chains, not a detected cycle. The onward address may be unread, broken or unsuitable for indexing; this finding does not establish its quality or Google’s chosen canonical. Noindex and robots restrictions have separate checks and do not erase an observed chain.
Confidence: High The target’s own onward canonical is directly observed. Its destination’s suitability and the search engine’s choice remain separate questions.
Sources
- Google, How to specify a canonical URL with rel="canonical" and other methods — calls rel="canonical" a strong signal that the named URL should become canonical. Checked 25 September 2026.
- IETF, The Canonical Link Relation (RFC 6596) — asks not to name as canonical an address that declares a canonical to another address. Checked 25 September 2026.
Editorial review: 2 November 2026