Menu
🆓 Free SEO Tool, No Account Required

Free Canonical Tag Checker

A page with two conflicting canonical tags gets treated the same as a page with none: Google ignores both and picks on its own. Check any URL for the canonical tag it's actually sending, in the HTML and the HTTP header, and find loops, chains, and duplicates before they split your rankings.

🔖 Audit Your Canonical Tag
Enter any URL. We'll fetch the page, locate the canonical tag (HTML & HTTP header), validate the destination, and detect any loops or chains.
Works with any publicly accessible URL. We fetch the full HTML to locate the canonical tag.

Free to use · No data stored · No account required

Fetching page and auditing canonical tag…

Why the Wrong Canonical Tag Can Tank Your Rankings

Google reads multiple versions of the same content as a quality problem, whatever's actually causing it: URL parameters, session IDs, sorting options, or a staging environment that got indexed by accident. The rel="canonical" tag is the one mechanism that lets you tell Google directly which version is the master and where to consolidate everything else.

Get it wrong and three problems compound on top of each other. Google starts cycling unpredictably between which version it shows in results. Backlinks pointing at different versions of the same page never aggregate into one authoritative URL. And crawlers burn budget on near-identical pages instead of finding whatever new content you actually want indexed.

What the Audit Actually Checks


How to Fix Canonical Tag Issues

Canonical errors range from trivially simple to structurally complex. Use this guide to diagnose the specific issue and apply the right fix, starting with the most critical.

1
Missing canonical: add a self-referencing declaration in <head>

Every indexable page should declare its own canonical URL. Add <link rel="canonical" href="https://yourdomain.com/page/"> with the full absolute URL, matching your preferred www/non-www format exactly. Leave it out and Google picks for you, frequently the wrong version.

2
Two canonical tags on one page: remove the extra one

This usually happens when a CMS plugin injects a canonical tag and a hardcoded template tag injects a second one independently. Google's stated behavior is to ignore both and decide on its own, so find the source of the duplicate, usually a plugin setting or a leftover hardcoded line, and remove it.

3
Canonical to a 404: restore the destination or update the tag

A canonical pointing at a dead page is worse than having none at all, since it actively misleads Google's consolidation logic. Restore the destination, or update the canonical to point at the best live replacement instead.

4
Canonical loop: pick one master URL and fix both pages

Page A points to B, B points back to A, and Google ends up ignoring both. Decide which one is the actual master, then update both tags to point there. The Redirect Checker can confirm neither page is also stuck in a redirect loop on top of this.

5
Relative canonical URL: convert it to absolute

Something like href="/page/" technically works, but CDNs and syndicated content can misinterpret a relative path. Use the full href="https://yourdomain.com/page/" instead to remove any ambiguity.

6
Canonical to a noindexed page: fix one side or the other

This is a direct contradiction: the source says consolidate here, the destination says don't index me. Google typically ignores it entirely. Either remove the noindex if the destination should be indexed, or repoint the canonical to a page that actually is. The Noindex Checker confirms whether the destination is blocked before you decide which side to fix.


Why This Stops Being a Page-by-Page Job at Any Real Scale

Checking canonicals one page at a time works fine until a site actually grows. Every new filter, sort option, or tracking parameter is another opportunity for competing versions to accumulate, often through entirely automated processes that no one approved or even noticed happening.

The errors that actually do damage are the quiet ones: a CMS upgrade that silently resets canonical settings sitewide, a new ecommerce filter generating thousands of parameter URLs with no canonical tag at all, a staging environment that got indexed with canonicals still pointing at itself instead of production. None of these throw an error. They just split authority across dozens of pages until someone happens to look.

Catching that requires watching how the canonical topology changes over time, not just checking it once.

Frequently Asked Questions

Google's guidance says it ignores both and decides on its own. This commonly happens by accident, when a CMS plugin injects one canonical tag and a hardcoded theme template injects a second one, neither aware the other exists.
It's an HTML element in the page's head telling search engines which version of a URL is the preferred one. When multiple URLs serve similar content, due to parameters, session IDs, or pagination, it consolidates ranking signals onto the designated master page.
Search engines typically ignore the hint entirely, which leaves the page competing with duplicate versions without a clear signal and can cause Google to index the wrong one.
Page A's canonical points to Page B, and Page B's points back to Page A. Search engines can't determine which is the true master and may ignore all canonical hints on both, splitting ranking signals across them.
Not necessarily. Self-referencing is the best-practice default, but a canonical pointing elsewhere is also valid when the page deliberately defers authority to a different master, like a paginated page pointing back to the root. Either way, the destination needs to be live, indexable, and the actual definitive version.
Technically yes, Google supports relative canonicals like href="/page/", but absolute URLs are safer since CDNs and syndicated content can misinterpret a relative path depending on context.
A 301 is a server-level instruction: the old URL disappears and everyone gets forwarded to the new one. A canonical is softer; both URLs stay accessible, but you're telling search engines which to prefer for indexing. Use a 301 to retire a URL permanently, and a canonical when you need multiple variants to stay reachable, for tracking parameters or A/B testing, while consolidating ranking signals on one of them.

Stop Letting Google Guess Which Page Wins.

Canonical errors don't announce themselves. They show up after a CMS update, a new plugin, or a staging environment that got indexed by mistake, and by the time you notice, authority's already split across pages that shouldn't be competing.

Automated Canonical Monitoring: an alert when a CMS update or plugin changes canonical tags sitewide.
Duplicate Content Heatmap: finds pages with high similarity that lack proper canonicalization.
Bulk Audit Reports: check thousands of URLs at once against the correct authority URL.
Cross-Domain Tracking: manage canonicals across multiple brands or subdomains from one dashboard.

✓ 30-day Premium Trial  ·  ✓ No credit card required  ·  ✓ Full canonical monitoring access

🚨
Canonical Change Alerts
Instant notification the moment a monitored page's canonical tag changes, triggered automatically on every crawl cycle.
📋
Bulk Canonical Auditor
Audit canonical tags across thousands of URLs at once. Identify missing, broken, and looped canonicals at scale.
🔥
Duplicate Content Finder
Automatically detect pages with high content similarity that are competing without clear canonical signals, before they damage your rankings.