Last updated:
Canonical Checker
This canonical checker reads a page's canonical tag, Link header and og:url, and for a live URL fetches the page it points to.
How to use the canonical checker
Enter an address under "Check a URL". Our server fetches the page as SchemaBizBot and returns it to your browser, where the checks run. The fetch summary shows the status, redirects, size and time, with a "Copy a link to this check" button. A link such as /seo/canonical-checker/?url=https://example.com/ runs a check when it opens.
For a page that isn't live yet, choose "Paste HTML". It's checked in your browser and nothing in it is fetched, so the canonical target isn't tested. A Link header or X-Robots-Tag arrives with the HTTP response, not the HTML, so only a URL check sees one. "Try an example page" loads a sample coffee pour-over guide.
The page opens on the Canonical & robots tab. Findings are labeled Error, Warning, Note or OK, and the tab's badge counts errors and warnings. A table lists the page's canonical, Link header, og:url, robots meta tags and X-Robots-Tag together. When a URL check finds a canonical naming another page, the checker fetches that target too. The other tabs cover the rest of the head, as does the meta tag checker.
What a canonical tag does, and what it doesn't
The same content often answers at several addresses: with a tracking parameter, sorted another way, or as a printable copy. A rel="canonical" link names the one you want treated as the main version.
It's a signal, not a directive. Google weighs it with other signals, such as permanent redirects and the addresses your internal links use, and Google may choose a different canonical. A canonical tag checker can't force that choice; it shows whether your signal is clear and names a page fit to be the main version.
Two ways to declare a canonical
The usual way is a <link> element in the head:
<link rel="canonical" href="https://example.com/guides/pour-over/"> The other is an HTTP Link header, which also works for files without an HTML head, such as a PDF:
Link: <https://example.com/guides/pour-over.pdf>; rel="canonical" Google recommends choosing one. Using both, its documentation says, is "more error prone", and it asks you not to give one page different canonical URLs through different methods.
The rules the checker tests
- Present. A page with no canonical is a warning; Google's guidance is to include a self-referential canonical on the canonical page.
- Absolute. A relative address such as
/guides/pour-over/is a warning. Google supports relative URLs but doesn't recommend them. - No fragment. A canonical ending in
#sectionis a warning. Google says not to specify a URL fragment as canonical. - In the head. A canonical outside
<head>is an error: Google only accepts the link in the head section. - One target. Several canonical links to different addresses are an error. The page makes two claims about its main version, the contradiction Google warns against.
- No extra attributes. A canonical link with
hreflang,lang,mediaortypeis a warning: Google doesn't use those links for canonicalization. - Header and HTML agree. A Link header naming a different address from the HTML is an error.
- Another page. A canonical naming a different page is a note: right on a duplicate, worth confirming anywhere else.
The canonical target
For a URL check, this canonical URL checker also fetches the address the canonical names, when it's another page, and reports:
- an error when the target fails to load;
- a warning when it redirects, so the canonical names an address one step short of the real one;
- an error when it's
noindex, so the page you named as the main version asks to stay out of Search; - a warning when it names yet another canonical, a chain from your page to the target to a third address.
Canonical with noindex, robots.txt and redirects
Marking duplicates noindex as well can look tidy, but Google doesn't recommend noindex for choosing a canonical within a site, because it blocks the page from Search. The checker warns when a page has both. Google also says not to use robots.txt for canonicalization. A permanent redirect is another way to signal the canonical, suited to an address nobody needs to visit.
The robots findings flag noindex or none in <meta name="robots">, <meta name="googlebot"> or X-Robots-Tag as a warning; a header rule for another crawler, such as otherbot: noindex, doesn't count. nofollow is a note, as are nosnippet and max-snippet, which link to the meta description checker.
Canonical and og:url
The Open Graph protocol defines og:url as "the canonical URL of your object", so it should match the canonical. This tab's table shows both, and the Open Graph checker warns when they differ.
Canonical and hreflang
With language versions, Google's guidance is to specify a canonical page in the same language, or the best substitute language if none exists. When the page has hreflang links, the Hreflang tab warns if its canonical points elsewhere, and its return-link check reports an alternate that names another page as canonical as an error. The hreflang checker opens on those checks.
Common canonical mistakes
- Every page names the home page. A canonical hard-coded in a shared template shows up as a note that the canonical names another page, on pages that aren't duplicates.
- The target moved. After a redesign, canonicals still name old addresses that redirect or fail; the target check reports both.
- The canonical lands in the body. An element that doesn't belong in the head, such as an
<img>, ends the head early when HTML is parsed, and later tags fall into the body. The All tags tab marks which ones. - A stale header. A server rule's Link header no longer matches the HTML: an error.
- A fragment from the address bar. A canonical copied with a
#section is a warning; name the clean address.
Frequently asked questions
FAQ
Should every page have a self-referencing canonical?
Google's documentation says to include a self-referential canonical on the canonical page, so each main version names its own address, and each duplicate names the main version. The checker reports a missing canonical as a warning.
Why does Google show a different canonical from the one I set?
Because rel="canonical" is a signal, not a directive, and Google may choose a different canonical. It also weighs signals such as permanent redirects and the addresses your internal links use, and it advises linking internally to the canonical URL. The checker can't see which address Google chose; it shows whether your own signals are well formed and agree.
Why is a canonical that redirects only a warning?
The target still leads to a page, so the signal isn't broken, but the canonical names one address and the redirect another. Pointing the canonical at the redirect's final address makes them agree. A target that fails to load or is noindex is an error: it can't be the main version in Search.
Does the canonical checker store anything?
Nothing you paste leaves your browser. For a URL check, the address goes to our server, which fetches the page as SchemaBizBot, along with its canonical target when that's another page and the first bytes of its social images. Like every tool on the site, the checker records what kind of check ran, such as the tab, what the canonical points at and the codes of the problems found, never a tag's text or the page's content. A URL check also records the checked page's address without its query string (see the privacy policy).