Canonical Checker - Verify rel=canonical

How the Canonical Checker Works

1. 01Paste the page address, tracking parameters and all. The messy version is the one a canonical exists to solve.
2. 02A ToolForte server requests it as ToolForteBot and records every redirect hop until a page actually answers.
3. 03The delivered HTML is parsed for the rel=canonical link and any rel=alternate hreflang links, and relative values are resolved to absolute addresses.
4. 04The requested address, the final address and the declared canonical are compared, and you get a named verdict plus any conflict between the canonical and the hreflang set.

Reading the verdict and knowing what to change

Self-referencing is the answer you want on any page that should rank under its own address, and it is what makes tracking parameters harmless. When the verdict says the canonical points elsewhere, the question is whether you meant it. Pointing a filtered listing at the unfiltered one, or a print view at the article, is correct and deliberate. Pointing a product page at its category, or every page at the homepage, is a template mistake that quietly removes those pages from the index. A cross domain canonical is legitimate only for syndicated content where another site is the original publisher, and it is otherwise one of the most damaging bugs on this list. The two near misses deserve more attention than they usually get. A canonical that differs only by protocol is normally an http value left in a template after a move to HTTPS. A canonical that differs only by a trailing slash means the template and the server disagree about the slash form, so the canonical is not self-referencing even though it looks right at a glance. Both send crawlers to an address that redirects back, which wastes crawl budget on large sites and leaves the wrong variant indexed on small ones. Fix them in the template, not page by page.

When to Use the Canonical Checker

Use it after any migration, replatform or template change, because canonicals are template output and they break in bulk. Use it when Search Console reports that Google chose a different canonical than the one you declared, since seeing the three addresses side by side usually explains why in seconds. Use it when a page has lost visibility with no content change, and when you have just added tracking parameters to a campaign and want to be sure they consolidate. Use it on multilingual sites whenever hreflang stops working, because a canonical that disagrees with the language set is the most common reason an entire hreflang cluster gets ignored.

Common Use Cases

• ·Explaining a Search Console message about Google choosing a different canonical than the one your page declares.
• ·Checking that campaign URLs with utm parameters consolidate back to the clean address instead of competing with it.
• ·Catching an http canonical left behind in a template after the site moved to HTTPS.
• ·Verifying that a multilingual page self-canonicalises and appears in its own hreflang set. → Hreflang Tag Generator
• ·Confirming after a replatform that product pages canonicalise to themselves rather than to their category.

Expert Tips

• ✻Test the ugliest version of a URL you can construct, with tracking parameters, a trailing slash and mixed case. A canonical that survives that is doing its job.
• ✻Never point a canonical at a URL that redirects. The redirect and the canonical then disagree about the destination, and search engines have to guess which one you meant.
• ✻Make internal links point at the canonical version. A canonical that every link on the site contradicts is a signal fighting the rest of your architecture.
• ✻Paginated listings should canonicalise to themselves, not to page one. Canonicalising page four to page one tells search engines the items on page four do not exist.

Frequently Asked Questions