Canonical Checker
This canonical checker fetches a URL the way a crawler does and finds every canonical it declares: the rel=canonical link in the head, any stray one in the body, and a canonical sent in the HTTP Link header.
Try it on or paste any public URL.
The URL this page asks Google to index
Checked:
, , .
None in the HTML and none in the HTTP Link header.
The URL you entered redirected
What the canonical URL returns
- Status
- Final URL
- Noindex
- robots.txt
- Its own canonical
The tag to use
Paste this into the page's head, replacing any canonical already there.
-
Fix:
That was one URL. Check the canonical on every page.
Crawl Cove runs of these checks on every page it crawls (), so a template that prints the wrong canonical shows up on every page that uses it, with the target of each canonical checked against the crawl.
Download Crawl Cove freeNote
It tells you whether the canonical is self-referencing, written as a full URL and unique, and when it points at another page it fetches that page too, to see whether it redirects, errors, is noindex, is blocked by robots.txt or names a different canonical of its own. It then checks the page's other signals against it: noindex, og:url and hreflang. No sign-up and nothing to install.
Use this tool often? Bookmark this page, so it is one click away next time.
Email me this result
Want a copy for your records or a client? Leave your email and we'll send you this result. It is written by a real person at Crawl Cove, not an automated blast, so it may take a little while to arrive. We'll only use your address to send it, unless you also tick the box below. Privacy policy.
Got it. We'll email your result to you. Nothing else lands in your inbox unless you ticked the tips box.
How to check a canonical tag
-
Paste the URL
Enter any public address, with or without https://. Parameter and tracking URLs are fine; checking one shows whether its canonical names the clean address.
-
Read the canonical summary
The top panel shows the URL the page asks Google to index, where each canonical was found (head, body or header) and how it relates to the page: itself, a different page, another domain, or only an http, www or trailing slash variant.
-
Check the target
When the canonical points elsewhere, the target is fetched as well. A redirect, an error, a noindex or a second canonical on the target each break the signal, and each is flagged with the URL to use instead.
-
Copy the fix
If anything needs changing, the result gives the exact link element to paste into the head, written as a full https URL with tracking parameters removed.
What a canonical tag is and why it matters
A canonical tag is a link element in the head of a page, written <link rel="canonical" href="https://example.com/page">, that tells search engines which URL is the main copy of the content. Most sites serve the same page at several addresses: with and without www, over http and https, with a trailing slash or without, and with tracking or filter parameters added. Without a canonical, Google picks one of them itself and splits links and signals across the rest. With one, you choose. Google treats the canonical as a strong hint rather than a rule, so it holds best when redirects, internal links and the sitemap all name the same URL.
What this canonical checker tests
The tag: whether a canonical exists, whether it sits in the head (Google ignores one in the body, including one pushed there because an image or other body element appeared in the head first), whether there is exactly one, whether the HTML and the Link header agree, and whether the href is a full https URL with no fragment and no tracking parameters. The target: whether it is this page, a variant that differs only by scheme, www, trailing slash, case or parameters, a different page, or another domain, and, when it is not this page, whether it answers 200 without redirecting, is free of noindex, is open to Googlebot in robots.txt and names itself as canonical. The signals: noindex on the page, og:url, and whether the hreflang set includes the canonical URL.
Canonical pointing to a redirect · Canonical pointing to a noindex page
How to read your canonical check result
Pass means the canonical does what it should. Improve means it works but sends a weaker signal than it could, such as a relative href, an og:url that names a different address, or a canonical that differs from the page only by a trailing slash. Fail means Google is likely to ignore the canonical or act on it in a way you did not intend: two canonicals that disagree, a canonical in the body, an http canonical on an https page, a target that redirects, 404s or is noindex, or two pages that name each other. Note marks something reported for information, such as a canonical that deliberately points at another page.
Self-referencing canonicals
A self-referencing canonical is a page naming its own URL. It is the right setting for every original page, because it protects the page when someone links to it with parameters attached, when a CMS serves it at a second path, or when a scraper copies it with the tag intact. If you checked a URL with tracking parameters and the canonical names the clean address, that also passes: the clean URL is the self-reference, and the parameter version is the duplicate.
Common canonical mistakes and how to fix them
Templates cause most of them. A theme and an SEO plugin both print a canonical and drift apart. A template echoes the current address, query string and all, into the canonical, so every tracking link becomes its own canonical. A page is moved and its old URL redirects, but other pages still canonicalise to the old one. A staging copy goes live with the staging host in every canonical, or with relative canonicals that resolve to whichever host served them. Paginated or filtered pages all point at page one, telling Google to drop the rest. And an https site keeps http:// in its canonicals after a migration. The checker names each of these, and the fix line says which URL to use.
Canonical tag mistakes: catching template bugs · Insecure canonical: http on an https page
Canonical, noindex or a 301 redirect?
Use a 301 when the old URL should stop existing for visitors as well as for search engines. Use a canonical when both URLs need to keep working, for example a product reachable from two categories or a page with sort and filter parameters. Use noindex when a page should stay out of search entirely, such as internal search results. Do not combine noindex with a canonical to another page: they ask for different things, and Google has said it may carry the noindex across to the target.
When Google picks a different canonical
Search Console sometimes reports that Google chose a different canonical from the one you declared. That happens when your other signals point elsewhere: internal links to a different version, a sitemap listing another URL, a redirect in the other direction, or two pages too different for Google to treat as duplicates. Fix what this checker flags first, then make links and the sitemap match the canonical, and request indexing again.
Duplicate, Google chose different canonical than user · Alternate page with proper canonical tag
Frequently asked questions
- Is this canonical checker free?
- Yes. It is free, needs no sign-up and no email, and there is no daily limit beyond a rate limit that stops one visitor sending hundreds of checks a minute.
- What is an example of a canonical tag?
- <link rel="canonical" href="https://example.com/blue-widgets"> placed inside the head of the page. For a PDF or another file without HTML, the same instruction goes in the response as a header: Link: <https://example.com/guide.pdf>; rel="canonical".
- Should every page have a canonical tag?
- Every indexable page should, and on an original page it should point at itself. It costs nothing and stops parameter, http, www and trailing slash copies from competing with the real URL.
- Does it check the canonical in the HTTP header?
- Yes. It reads the Link header as well as the HTML, shows where each canonical was found, and fails the check when the header and the HTML name different URLs.
- Can a canonical point to another domain?
- Yes, and that is the right set-up for content you syndicate to another site or copy from one. Anywhere else it asks Google to drop your page in favour of the other site, so the checker flags it for you to confirm.
- Does it see canonicals added by JavaScript?
- No. It reads the HTML the server sends, before any script runs. Google can pick up a canonical set by JavaScript after rendering, but it may index the page before that, and a script that changes an existing canonical sends a mixed signal. Put the canonical in the server HTML.
- How is this different from URL Inspection in Search Console?
- URL Inspection shows the canonical Google finally chose, but only for your own verified sites and only after Google has crawled the page. This checker works on any public URL, straight away, and shows why a declared canonical might not hold: a redirecting target, a conflict, or a signal that disagrees.
- Can I check a private or staging URL?
- No. The checker only requests public addresses on the standard web ports, and it refuses any redirect that leads to a private network address. To check a staging or intranet site, use a crawler that runs on your own computer, such as Crawl Cove.
- Can I share the result?
- Yes. After a check the page address includes the URL you checked, so copying it from the address bar gives a link that re-runs the same check. Results are cached for ten minutes, so re-check after that to see a change.
From one page to your whole site
This checks one URL. Crawl Cove reads the canonical of every page it crawls and flags missing and relative canonicals, canonicals to redirects or noindex pages, http canonicals on https pages and hreflang sets that disagree with them, across the whole site. See find duplicate pages or run a full site audit.
More free tools
More technical SEO tools →-
Website SEO Checker
Open tool → -
HTTP Header Checker
Open tool → -
Noindex Checker
Open tool →