The canonical tag tells Google which version of a page is the main one when several URLs share the same content. Used well, it consolidates signals; used badly, it can drop important pages from the index without anyone noticing.

AD2SPIDER checks the canonical of every page and cross-checks it with the rest of the crawl: whether it points to a URL that redirects or fails, whether it forms a chain, whether a page declares several different ones, whether it sits outside the head, carries a fragment or invalidating attributes, and whether the canonical URL gets internal links.

Canonical tags errors

They stop the page from working or being indexed properly. Fix them first.

Canonical points to a non-200 URL

Why it matters
The canonical URL redirects or errors: the signal is contradictory and Google will probably ignore it.
How to fix it
Point the canonical at the final URL returning 200.

Priority: highDocumented by GoogleDocumentation ↗

Canonical points to a non-indexable URL

Why it matters
The canonical URL returns 200 but is not eligible (noindex, another canonical…): you ask to index something that cannot be indexed.
How to fix it
Point the canonical at an indexable URL or remove the blocker on the target.

Priority: highDocumented by GoogleDocumentation ↗

Canonical tags warnings

Real problems worth fixing.

Conflicting canonicals

Why it matters
There are several canonicals with different targets: Google may ignore all of them.
How to fix it
Keep a single canonical (check SEO plugins and templates duplicating it).

Priority: highDocumented by GoogleDocumentation ↗

Canonical with fragment

Why it matters
The canonical contains '#'. Fragments are not part of the indexable URL.
How to fix it
Remove the fragment from the canonical.

Priority: mediumDocumented by GoogleDocumentation ↗

Canonical outside head

Why it matters
Google ignores rel=canonical outside <head>.
How to fix it
Move the canonical into the <head>.

Priority: highDocumented by GoogleDocumentation ↗

Invalid canonical

Why it matters
The canonical is not a valid HTTP(S) URL and will be ignored.
How to fix it
Fix the canonical href value.

Priority: mediumDocumented by GoogleDocumentation ↗

Canonical points to a URL blocked by robots.txt

Why it matters
Google cannot crawl the canonical to confirm the signal.
How to fix it
Allow crawling of the canonical URL or choose another.

Priority: highDocumented by GoogleDocumentation ↗

Canonical with invalidating attributes

Why it matters
A rel=canonical with hreflang, lang, media or type is not a valid canonical: Google ignores it.
How to fix it
Keep the canonical with rel and href only; alternates go in separate rel=alternate tags.

Priority: mediumDocumented by GoogleDocumentation ↗

Canonical chain

Why it matters
The canonical points to a URL that is itself canonicalised elsewhere: the signal weakens.
How to fix it
Point the canonical straight at the final URL.

Priority: mediumDocumented by GoogleDocumentation ↗

Unlinked canonical

Why it matters
The URL is only discovered because another page declares it canonical: no internal page links to it, weakening the signal.
How to fix it
Link to the canonical URL across the site (instead of the canonicalised variants).

Priority: lowDocumented by GoogleDocumentation ↗

Canonical tags opportunities

Improvements with impact, usually based on configurable thresholds.

No canonical

Why it matters
No canonical is declared. Google will choose one; a self-referencing canonical helps consolidate parameter variants.
How to fix it
Add <link rel="canonical"> with the preferred absolute URL.

Priority: lowDocumented by GoogleDocumentation ↗

Relative canonical

Why it matters
The canonical uses a relative path. It works, but Google recommends absolute URLs to avoid mistakes.
How to fix it
Use the absolute URL with scheme and domain.

Priority: lowDocumented by GoogleDocumentation ↗