Check a page's canonical tag
Type a page address. We follow its redirects, read rel=canonical from the HTML and the Link header, and say whether it points at the final page, another page, or sends mixed signals. Free, no account.
How the check works
- The address is parsed first: http and https only, ports 80 and 443 only, no usernames, no IP addresses and no internal names such as localhost. Anything else is refused before any request.
- The name is resolved and every address it points to must be public. Private, loopback, link-local (cloud metadata included), multicast and reserved addresses are refused, and the connection goes to the address that was checked.
- We request the address and follow its redirects by hand, up to 4, re-checking every hop. The canonical is read on the page where the chain ends.
- We read rel=canonical from the head, from the body (where it does not count) and from the HTTP Link header, plus og:url, the robots meta tag and the X-Robots-Tag header.
- If the canonical names a different address, that address gets one request through the same guard, so you can see whether it answers or redirects again.
What gets flagged
- Missing: no canonical at all.
- Conflicting: two or more different canonicals, or the Link header and the HTML disagreeing.
- Near-misses: a canonical that differs from the page only by http and https, www, a trailing slash or a query string.
- Redirect clashes: a canonical that points back at the address that redirected, or at an address that redirects or errors.
- Mixed signals: noindex together with a canonical, and og:url naming a different address.
- Placement: a canonical in the body, which Google ignores.
Self or other: which is right?
A page that should be found in search usually points the canonical at itself. A page that is a copy, such as a print version, a filtered list or the same service page under two paths, points at the one you want to rank. A canonical is a strong hint, not an order; search engines can still choose another address.
Web designers rebuilding a site often find old canonicals still pointing at a staging domain. To find businesses whose sites may need that kind of cleanup, search 67Leads by trade and city.
Get 67 leads free No card. Search free with contacts masked.
Redirect checkerOpen Graph checkerHreflang checkerSitemap validatorMeta tag checker
Questions
A link tag in the head, <link rel="canonical" href="...">, that names the preferred address for a page when the same content can be reached at more than one address.
It is a common, safe default. It tells search engines which of the address forms (http or https, www or not, with or without tracking parameters) is the one you mean.
Google advises against it: noindex says leave this page out, while a canonical to another page says merge it into that one. Choose the signal that matches what you want.
For a page you want found, yes. A canonical that names the address which redirects to this page points search engines back into the redirect.
Something such as a page builder or a script placed the tag after the head ended, or an element that only belongs in the body appeared earlier and closed the head. Google only reads canonicals in the head.
More free tools
Local business counterNo-website business finderLead list previewCold email template generatorAI crawler checkerllms.txt generatorllms.txt checkerLocal business schema generatorFAQ schema generatorrobots.txt generatorMeta tag checkerSchema markup checkerNAICS code lookupSIC code lookupSSL certificate checkerRedirect checkerBroken link checkerPage weight checkerLead list column mapperMerge tag checkerOpen Graph checkerSitemap validatorHTTP headers checkerHeading structure checkerImage alt text checkerHreflang checkerDNS lookupAll Website checks toolsAll tools