🔗

Canonical Tag Checker

Paste your page HTML source to detect canonical link tags, identify canonical URL, and flag common canonical issues.

About Canonical Tag Checker — Canonical URL Checker Online

A canonical tag (<link rel="canonical" href="...">) in a page's HTML head tells search engines which URL is the authoritative version of the page. When the same or similar content is accessible at multiple URLs — through HTTP and HTTPS variants, www and non-www, URL parameters, pagination, or print versions — search engines may split the page's ranking signals across those variants rather than consolidating them. A correct canonical tag prevents this by explicitly designating the preferred URL. This tool reads the HTML source you paste, detects any canonical tags, and flags the most common problems.

Canonical issues are among the most common causes of unexplained ranking underperformance. An e-commerce product page accessible at four parameter variations (?color=red, ?size=large, the base URL, and a paginated variant) without a canonical pointing to the base URL is effectively splitting its ranking signals four ways. A blog post that exists at both http:// and https:// without a canonical may have its authority divided between the two. A developer checking their site's canonical configuration after a CMS migration, after implementing URL parameters, or after setting up HTTPS for the first time will find this tool useful for spotting issues before they compound.

How to Use Canonical Tag Checker

  1. Open the page you want to check in your browser.
  2. Press Ctrl+U (or Cmd+U on Mac) to view the page source, or right-click and select "View Page Source."
  3. Select all (Ctrl+A) and copy the full HTML source.
  4. Paste it into the Page HTML Source text area above.
  5. Optionally enter the Page URL — this lets the checker determine whether the canonical is self-referencing or pointing to a different page. Click Check Canonical to see the results.

Common Canonical Issues Explained

Each issue type has a different cause and a different fix — understanding why each one matters helps you prioritize which to address first.

  • Missing canonical: The page has no <link rel="canonical"> tag at all. This isn't necessarily a problem if the page is the only version of its content and has no parameter variants — but without a canonical, search engines may index URL parameter variations (?utm_source=email, ?ref=social) as separate pages, diluting the ranking signals of the base URL. Best practice is to include a self-referencing canonical on every indexable page.
  • Multiple canonical tags: When more than one <link rel="canonical"> tag exists in the head, search engines ignore all of them or pick one arbitrarily. This often happens when a CMS inserts a default canonical and a plugin or theme also inserts one. The fix is to identify which system is inserting duplicates and remove one.
  • Relative canonical URL: Canonical URLs should be absolute and include the protocol and domain (e.g., https://example.com/page). A relative canonical like /page is technically valid per the spec but creates ambiguity when the same page is accessible via HTTP and HTTPS — the relative URL could be interpreted as either protocol. Use absolute URLs to eliminate any ambiguity.
  • Canonical pointing to a different page: If the canonical URL doesn't match the page URL you entered, the page is explicitly passing its ranking signals to a different URL. This is intentional in consolidation scenarios (pointing multiple variant URLs to a single canonical) but is a problem if it happens on a page that should be canonicalizing to itself. Check whether the target URL is correct and intentional.
  • Canonical with HTTP on an HTTPS site: If your site is HTTPS but the canonical points to the HTTP version of the URL, search engines may treat the HTTP URL as the canonical version — undoing the HTTPS migration. All canonical URLs on HTTPS sites should use the https:// scheme.

Tips for Canonical Tag Implementation

Getting canonical tags right involves consistent implementation rules across your entire site, not just individual page checks.

  • Implement canonicals at the CMS level, not manually: Manually adding canonical tags to individual pages is error-prone and doesn't scale. Most CMS platforms (WordPress, Shopify, Webflow, etc.) have canonical tag settings or plugins that generate them automatically from the page URL. Set this up site-wide rather than page by page.
  • Verify after CMS migrations and platform changes: Canonical tags are often lost or broken during site migrations, theme updates, or plugin changes. After any major platform change, audit a sample of pages (homepage, key landing pages, product pages, blog posts) to confirm canonical tags are still correctly set and pointing to the right URLs.
  • Check paginated pages separately: For paginated content (/page/1, /page/2, etc.), each page should have its own canonical pointing to itself — not to page 1. Pointing all paginated pages to page 1 tells search engines all the content on page 2+ should be consolidated under page 1, which removes the paginated pages from the index. Use separate self-referencing canonicals on paginated pages.

Why Use a Canonical Tag Checker Online

Checking canonical tags manually means reading through page source HTML and finding the relevant line in the head section — which is fine for one page but slow for a site audit. This tool extracts the canonical tag, displays the canonical URL clearly, and flags the most common problems in a readable format. It's faster than searching through raw HTML and surfaces issues like multiple canonicals or HTTP canonicals on HTTPS pages that are easy to miss when reading source manually.

SEO consultants auditing client sites benefit from a quick per-page canonical check that produces a clear result they can document. Developers verifying that a new CMS configuration correctly generates canonical tags benefit from a tool that confirms the tag is present and correctly formed. Content teams who maintain pages manually and may not have access to SEO auditing software benefit from a free, immediate check that requires only page source — which any browser can provide.

Frequently Asked Questions about Canonical Tag Checker

Best practice is to include a self-referencing canonical on every indexable page. This explicitly signals the preferred URL and prevents issues with URL parameter variations (?utm_source=, ?ref=, ?sessionid=) being treated as separate pages by search engines. Pages you don't want indexed at all (noindex pages) don't need canonical tags — noindex and canonical serve different purposes and shouldn't be combined on the same page.

A redirect (301) moves users and search engines from one URL to another — anyone who requests the old URL gets sent to the new one. A canonical tag is a hint to search engines about which URL to treat as authoritative, but it doesn't redirect users or affect what URL appears in the browser. Use redirects when you're retiring a URL permanently and want all traffic to go to the new one. Use canonical tags when multiple URLs need to remain accessible (for different reasons) but you want ranking signals consolidated on one of them.

No. Google treats canonical tags as hints rather than directives. If Google determines that the canonicalized URL is unlikely to be the true canonical (e.g., the target URL doesn't link back to the source, the content is very different, or the canonicalized page has significantly lower authority), it may ignore the tag and choose its own canonical. To make canonicals more reliable, ensure that the canonical URL is the one that's linked to from sitemaps, internal links, and external backlinks — consistency across these signals reinforces the canonical tag.

Yes. Cross-domain canonicals are valid and are commonly used for content syndication — if your content is republished on another site, the republished version should have a canonical pointing back to the original. Google supports cross-domain canonicals. The publisher receiving the syndicated content needs to set the canonical to the original source URL; the original source doesn't need to do anything. Cross-domain canonicals pass ranking signals to the target domain just like same-domain ones.

Yes, completely free. No account, no sign-up, and no usage limits. The checker runs entirely in your browser using JavaScript — no HTML is sent to any server. You can check as many pages as you need.