Check explainer · v1

Canonical conflicts: chains, shared targets and dead ends

Automated

Last reviewed

A canonical tag that points somewhere real is a hint; one that points at a dead URL, at another hop, or claims a target several pages share is a conflict — the crawl chases every canonical to its end.

How this check works

Canonical targets are followed across the crawl matrix. A tag pointing at a dead URL fails; a chain (this page → A → B) fails at the middle hop; several pages claiming the same canonical target fail as a shared claim — the check probes untracked targets and fails the page when the probe cannot reach them.

What does a failure look like?

A deleted product leaving a canonical at the 404; A points to B while B points to C after a partial migration; ten filter variants all marking the same unfiltered URL without consolidating — each conflict named with the URL the tag resolves to.

How to fix it, step by step

  1. Point the canonical at the final URL in one hop — never at another URL that itself canonicalizes elsewhere.
  2. Repoint canonicals away from dead targets during deletions, in the same change that removes the page.
  3. When many pages share a target intentionally, consolidate them with redirects or noindex instead of stacking canonicals.

What does a pass or fail look like?

Good

Every canonical resolves in a single hop to a live URL with exactly one claimant.

Fail

A category page canonicalizes to a URL that was deleted last month — the hint points nowhere and the crawl says so.

Frequently asked questions

How is a canonical chain a failure if each tag is valid?

Because each hop forces crawlers to fetch again and splits the signal across more URLs. A canonical is supposed to name the final URL; pointing at another alias is a half-finished consolidation.

Can several pages share one canonical tag?

They can point at the same target, but then that target is doing consolidation work the crawl flags: if the pages should exist separately, a shared canonical will not save them — and if they should not, redirects or removals are the honest fix.

Does the crawl check canonical tags on every page?

It reads them on every analyzed page and resolves each one: tracked pages directly, and untracked targets by probing them once. What it does not judge is whether the chosen target is the best one — only that the tag resolves cleanly.

This rule is one of the checks the audit runs. Run the full site audit

Free preview; no account needed.

Visdenda check explainers · one page per published ruleCanonical conflicts · v1