# Fix Duplicate Content Fast With a Canonical Checker
You've got pages that shouldn't compete with each other, but Google's treating them like separate documents. Right now, your ranking signals are scattered across versions of the same content instead of stacking on one page.
This is exactly what canonical tags fix—and most sites either aren't using them correctly or have no idea if they're working. You need to verify they're in place and pointing the right direction.
What Is a Canonical Checker?
Canonical Checker is a free browser-based tool that reads the rel=canonical tag on a page and tells you what it's pointing to. No login required, no software to install—just paste your URL and it runs the check instantly.
When you submit a page, the tool scans the HTML head and extracts any self-referential or cross-domain canonical tags. It shows you the exact target URL, whether it's an absolute URL (which it should be), and whether the tag exists at all. You get the raw output: the canonical URL, the page you checked, and whether they match.
Why It Matters for SEO
Canonical tags tell Google which version of a page should get the ranking credit when duplicates exist. Without them, Google chooses—and it doesn't always choose the one you want. I've audited sites losing 40% of expected traffic because their canonicals pointed the wrong direction or didn't exist on critical pages.
Here's what actually happens: when you have 5 versions of the same product page (HTTP, HTTPS, www, non-www, and with parameters), Google crawls all of them but only ranks one. Each version dilutes the ranking signal on the others. Canonical tags consolidate that authority into a single URL. Sites with proper canonicals typically see ranking recovery within 2-4 weeks because Google recrawls most sites every 3-7 days and picks up the tag immediately.
The real issue is that many sites have some canonicals but they're broken. I found one e-commerce site where 200+ product pages had self-referential canonicals on the HTTPS version but the actual canonical tag pointed to the HTTP version. Google had to guess. Their organic traffic flatlined.
How to Use It
- Go to https://scrawl.tools/tools/canonical-checker — no account setup needed
- Enter the full URL of any page you want to check (include the protocol: https://)
- Review the result — it'll show you what the canonical points to, or tell you if no tag exists
Run this on your homepage, main product pages, blog posts, and any page you think might have duplicates. If you're managing a site with 500+ pages, check at least 30-50 across different sections to find patterns.
What the Results Tell You
The tool returns four pieces of information. First, it shows the canonical URL it found (if one exists). Second, it displays the page you checked. Third, it tells you whether they're identical—this matters because a page can point to itself (self-referential, which is fine) or point elsewhere (consolidating to a preferred version). Fourth, it flags whether the tag is missing entirely.
If the canonical is missing, that page isn't giving Google clear direction. If it's present but points to a dead page, you're wasting the signal. If it points to a completely different domain, make sure that's intentional—cross-domain canonicals work but can confuse crawlers if they're wrong.
You'll also see the exact HTML structure of the tag:
<link rel="canonical" href="https://example.com/product/blue-shoes/" />That's what you're looking for. If you see anything else—like a broken href, a relative URL instead of absolute, or a protocol mismatch (HTTP pointing to HTTPS or vice versa)—it's broken.
3 Mistakes Most People Make
Mistake 1: Self-referential canonicals everywhere. Sites often add canonicals to every page pointing to itself. That's not wrong, but it's wasteful—you only need canonicals on pages that have actual duplicates. If a page is truly unique, skip it and save crawl budget. I've seen sites with 10,000 unnecessary self-referential canonicals that Google has to process.
Mistake 2: Canonicalizing from HTTPS to HTTP. This is backward. Always point the canonical from non-preferred versions to the preferred version. If you're on HTTPS (which you should be), your canonicals should point to HTTPS pages. Pointing HTTPS → HTTP tells Google "rank the insecure version"—it doesn't make sense and won't stick.
Mistake 3: Not checking after migrations. You moved to a new domain, updated your CMS, or switched platforms. You need to verify every canonical still works. Canonical checkers catch broken or outdated tags that point to pages that no longer exist. I audited a site 6 months post-migration and found 800 pages with canonicals pointing to the old domain that had been shut down. Those signals were completely wasted.
Most people also miss verifying canonicals on paginated content and filtered results. A product filter page (example.com/shoes?color=blue&size=10) should canonical to the unfiltered version (example.com/shoes) to avoid treating every filter combination as separate content. Check a few of these with the Canonical Checker and you'll spot the pattern immediately.
Related Tools
If you've got canonicals working but suspect other crawl issues, run the XML Sitemap Validator to confirm Google knows which pages exist. If some pages redirect before reaching the canonical, use the Redirect Chain Checker to catch those problems first.
Go to https://scrawl.tools/tools/canonical-checker now and check 10 random pages from your site. You'll usually find at least one broken canonical or missing tag within the first few checks—that's the reality on most sites.