Canonical Tag Checker
Check canonical tags, follow chains, and detect SEO issues
In 30 seconds
- Every indexable page should have exactly one canonical tag, usually pointing at itself.
- Point canonicals straight at the final URL, never at a redirect or an error page.
- Your links, sitemap and redirects should all agree with the canonical.
Which version of this page is the real one?
Enter a URL and the canonical checker reads its rel="canonical" tag, then follows it. If the canonical URL names a different canonical, it keeps going, up to five hops, and shows the whole chain with the status of each step. It reports:
- No canonical at all.
- More than one canonical tag, which can make search engines ignore them all.
- Circular references: A points to B, B points back to A.
- Canonicals that redirect or return an error.
- Chains with several hops instead of one.
- Cross-domain, HTTP or relative canonicals.
- A mismatch with
og:url, plus any AMP version the page links to.
Tick Render JavaScript to check the canonical after scripts run. Some frameworks and tag managers add or change it in the browser, and this shows you if that’s happening.
What a canonical tag is for
The same page often lives at several addresses: with and without www, with tracking parameters, with sort and filter options. The canonical tag tells search engines which one is the real one:
<link rel="canonical" href="https://example.com/running-shoes/" />Search engines then pile the signals, like links, onto that URL instead of splitting them between copies. Google treats it as a strong hint, not an order, so it works best when everything else agrees.
Reading the results
No canonical tag found
Without one, search engines pick for you, and they might pick the version with tracking parameters.
Quick fix
Add a self-referencing canonical (the page naming itself) to every page you want indexed.
Multiple canonical tags
Usually a theme and an SEO plugin both adding one, or a script adding a second. With conflicting canonicals, Google may ignore them all. Keep exactly one, in the <head>.
Circular reference
A says B is the real one, B says A is. The signals cancel out. Pick one and point both at it.
Canonical target redirects
Usually a missing trailing slash on a site that adds one, or http:// on a site that redirects to HTTPS. Point straight at the final URL.
Canonical target returns an error
Pointing at a 404 tells search engines the real version doesn’t exist. Often a leftover from a URL change or migration.
Chain with several hops
Each page should name the final canonical directly. Chains are slower to process and more likely to be ignored.
Cross-domain, HTTP or relative canonical
Cross-domain is right for syndicated content and a disaster if it’s a copy-paste from staging. HTTPS sites should use HTTPS canonicals. Relative URLs work, but absolute ones remove any doubt.
Canonical doesn’t match og:url
Social apps group shares by og:url. Make it the same as the canonical so every signal points at one address.
Canonical mistakes that hurt
- Every page canonicalized to the homepage by a template bug.
- Page 2, 3 and 4 of a list all canonicalized to page 1, hiding everything on the later pages.
- A canonical pointing at a URL that’s blocked in robots.txt or marked
noindex. - A sitemap that lists a different version of the URL from the canonical.
Watch out
If a page has moved for good, use a 301 redirect, not a canonical. Canonicals are for duplicates that still need to exist.
Quick answers
Should every page have a self-referencing canonical?
Every page you want indexed, yes. It protects against duplicates you don’t know you have.
Why did Google pick a different canonical?
Google weighs your tag against redirects, internal links, sitemaps and how similar the pages are. If they disagree, it may choose another URL. URL Inspection in Search Console shows which one it chose.