Canonical tag checker: find the contradictions before the tag
Six checks, five documented bad practices and the template bugs that repeat across thousands of URLs.
·3 min read
A canonical tag checker answers one question: does this page tell search engines which URL should represent it, and does it do so consistently. The tag itself is simple. The failures are usually contradictions, such as a canonical pointing one way, the sitemap another, and an internal link a third.
What the tag does
rel="canonical" is a hint that a duplicate or similar page should consolidate around a different URL. Google ranks the methods by strength: redirects first, rel="canonical" annotations second, sitemap inclusion third. They stack, so using two consistent signals is stronger than one.
| Signal | Strength | Typical use |
|---|---|---|
| 301 or 308 redirect | Strongest | Retiring a duplicate for good |
rel="canonical" link element |
Strong | Variants that must stay reachable |
rel="canonical" HTTP header |
Strong | Non-HTML files such as PDFs |
| Sitemap inclusion | Weak | Declaring preferred URLs at scale |
The checks that find real problems
- Does the canonical resolve? A tag pointing at a 404 or a redirect wastes the hint.
- Is it absolute? Google supports relative paths but recommends absolute ones, because a test environment with the same relative path can cause trouble later.
- Does the page canonicalise to itself? The canonical page should carry a self-referential tag.
- Do the signals agree? Sitemap, canonical and internal links should name the same URL.
- Is it in the
<head>? A link element outside the head is not accepted. - Did JavaScript change it? Google advises declaring the canonical in the source and not letting scripts alter it.
The contradictions that cause the most damage
The documented bad practices are worth memorising because each is common.
- Different URLs in different signals. One URL in the sitemap, another in the tag. Google may pick neither.
- Using robots.txt for canonicalisation. A disallowed URL can still be indexed without its content.
- Using the URL removal tool. It hides every version, not just the duplicate.
- Using
noindexto pick a canonical. It blocks the page from Search entirely, which is not the goal. - Using a fragment. Google generally does not support URL fragments.
Where a checker earns its place
A single-page check catches the obvious. The expensive problems appear across a site: a paginated category where page two canonicalises to page one, an ecommerce filter that canonicalises every colour to the parent product, or an international cluster where the canonical points at the wrong language.
For the third case, Google's guidance is specific: if hreflang is in use, the canonical should be a page in the same language, or the best available substitute.
Checking one URL
seogeoaeo.ai's indexing checker reports canonical and indexation signals for a URL, which is the right starting point before a crawl. Use it on one page per template, then fix the pattern.
One practical note on scope: a checker sees the page as it is served, not as a search engine later renders it. If a script rewrites the canonical after load, the tool may report the source version while Google sees the modified one. That is one more reason to declare the canonical in the head and leave it alone.
FAQ
Is a canonical tag required?
No. Google says sites generally do fine without specifying one, and it will identify a canonical itself. The tag matters when you have a preference it might not guess.
Should the canonical page link to itself?
Yes. A self-referential canonical is a documented best practice, and it makes the intent explicit.
Can a canonical tag be ignored?
Yes. It is a hint. Google weighs it against redirects, sitemaps, internal links and content similarity.
A short working order
Confirm the canonical resolves and is absolute, make it self-referential on the target, then check that sitemap and internal links agree. Fix those three before adding any new tag.