Free · No signup

Canonical Tag Checker

Canonical tags are how you tell Google which version of a page is the real one. Get them wrong and you can cannibalize your own rankings or hand traffic to a competitor. Our checker parses your page, finds every canonical signal, and flags issues that confuse search engines, all in your browser, with no server fetch required.

How it works

A short, focused workflow — input, run, read the result.

  1. Paste your page URL

    Enter the URL you want to audit. The tool fetches the HTML, then runs 9 checks on the canonical signal.

  2. Read the issue list

    Each finding shows severity (error/warning/info), a plain-English explanation, and the exact line from your page.

  3. Fix the canonical

    Common fixes: add a self-referential canonical, consolidate cross-domain canonicals to your primary domain, or align canonical with og:url.

What is a canonical tag, and why does the signal matter to Google?

A canonical tag is the <link rel='canonical'> element that tells Google which URL is the master version of a page. It is the primary mechanism for preventing duplicate content at scale. Get it wrong and Google can ignore all of them, index the wrong URL, or hand your rankings to a competitor who set theirs correctly.

The canonical tag is a single line of HTML, but it is the line that decides which URL Google indexes when the same content is reachable from multiple places. The common cases: your site is reachable on http and https, with and without www, with tracking parameters appended, and via slightly different URL paths. Without a canonical, Google has to pick. With one, you pick for Google. The catch is that the tag is silently ignored if it is malformed, self-contradicting, or missing the absolute URL format.There are 9 issues that disqualify a canonical. Self-referential canonical pointing to a different URL. Multiple canonical tags on the same page. Canonical pointing to a redirected URL. Canonical pointing to a 404. Cross-domain canonical that looks like content theft. Non-HTTPS canonical on an HTTPS page. Mismatch between canonical and og:url. Canonical in the body, not the head. Canonical in an X-Robots-Tag header that contradicts the HTML one. Each is a real, common bug.Our checker fetches your page, parses every canonical signal (the link tag, the X-Robots-Tag header, the og:url), and runs 9 checks against the result. Each finding has a severity, a plain-English explanation, and the exact line from your page. Runs in the browser, no server-side fetch of your data.
9
Canonical checks the tool runs per page
1
Canonical tag per page is the Google best practice
30/hr
Free browser-based audits per IP

What this canonical tag checker checks

Every way a canonical signal can be wrong, ranked by how badly it tends to confuse Google.

  • Self-referential canonicalcanonical URL should match the page's own URL on every indexable page. The most common Google-recommended setup.
  • Absolute URL formatcanonical must be a full URL (https://example.com/page), not a relative path. Google ignores relative canonicals silently.
  • Multiple canonical tagsmore than one <link rel='canonical'> on a page makes Google ignore all of them. Catches CMS templates that emit duplicates.
  • Cross-domain canonicalcanonical pointing to a different domain. Legitimate for content syndication, often a sign of a bug or content theft.
  • Non-HTTPS canonicalcanonical using http:// on a page served over https. Google treats the signal as inconsistent and may rewrite it.
  • og:url alignmentog:url should match canonical. Mismatches confuse crawlers and split social signals between two URLs.
  • Canonical in <head>the link tag must be in the page <head>, not the body. Browsers and crawlers ignore canonicals outside the head.
  • X-Robots-Tag conflictsan X-Robotics-Tag header with noindex conflicting with a canonical indexable page. Google picks one, often the wrong one.

Who uses this canonical tag checker

Anyone who manages a site with duplicate-content risk, which is most sites over 50 pages.

In-house SEOs

You migrated 800 pages to a new CMS last month and want to confirm the canonical tags survived the cutover.

Audit the top 100 traffic pages, find the 5 to 10 with wrong or missing canonicals, and ship the fixes before Google re-crawls and picks the wrong version.

Technical SEOs

You're auditing a 5000-page ecommerce site where the category pages have multiple sort and filter URLs that all self-canonical.

Identify the 200 URLs that need a cross-canonical pointing to the master category, write the rewrite rules, and consolidate ranking signal.

Developers

You're building a CMS template and want to confirm the canonical your code emits matches what SEO expects.

Paste a sample URL from each template, see the exact canonical line the parser found, catch bugs in the head template before they ship to production.

Agencies

You onboard a new client whose site has 3 canonical tags on every page and an HTTP-only canonical in a 2018 migration that never finished.

Generate the issue list, prioritize the 5 most damaging findings, and ship a fix list the client can act on this sprint.

Ecommerce managers

Your product pages are reachable via 6 different URL paths and the canonical points to the wrong one.

Find the offending URLs, update the canonical to point at the master product page, and stop the duplicate content dilution across variants.

Content marketers

You syndicate blog posts to Medium and LinkedIn and the canonical on the syndicated copy points back to the wrong URL.

Verify the syndicated canonical points to the original, fix the medium import setup, and reclaim the ranking signal you were giving away.

Related glossary terms

Want a deeper dive? These glossary entries explain the concepts behind this tool.

Frequently Asked
Questions

Everything you need to know about canonical tag validation in 2026. From spotting multiple canonicals to fixing URL redirects and JavaScript overrides.

A canonical tag is an HTML <link rel="canonical"> element (or an HTTP header) that tells search engines which URL is the master version of a page when duplicate or near-duplicate content exists across multiple URLs. It is the primary mechanism for preventing duplicate content issues at scale.

Best practice: yes, on every indexable page. A self-referential canonical (where the canonical points to the page's own URL) reduces ambiguity, helps with parameter handling, and gives Google a definitive signal even when the URL has tracking parameters appended.

A canonical tag pointing to a different domain than the current page. This is sometimes legitimate (content syndication, E-E-A-T consolidation to a verified author profile) but is more often a sign of content theft, an old migration that wasn't completed, or accidental SEO harm. Worth investigating.

Yes, but search engines will ignore all of them and try to figure out the canonical themselves, which often leads to surprising results. Best practice: one canonical per page, period. If you have multiple, you've got a bug.

The audit runs entirely in your browser using a single fetch to /api/canonical-tag-check/check. We don't log URL contents, don't store responses, and don't train any AI on your data. Rate-limited to 30 checks/hour per IP.

Want this automated across your whole site?

SERPView monitors title tags, meta descriptions, and structured data for every URL — alerting you the moment something breaks or could be improved.

Get started free