Canonical Checker

How the Canonical Tag Affects Duplicate Content and Rankings

The canonical tag tells Google which URL is the main version of a page when several URLs show the same or similar content. It is the main defense against duplicate content, which spreads ranking signals across copies and leaves none of them strong enough to rank well. When your product appears at three URLs because of filters, tracking parameters, or a trailing slash, a canonical pointing them all to one address consolidates the signals onto that page. Set it wrong and you can hide your best page from search or hand the top spot to a copy you never meant to promote.

A healthy page carries a self-referencing canonical, meaning the tag on the final URL points to that same final URL. This tool reads the canonical after following any redirect, then tells you whether it matches, differs, or is missing, and whether the page declares more than one canonical, which cancels the signal. Common faults are a canonical that still points to an http or non-www version after a migration, a template that hardcodes one canonical across every page, and pages with two conflicting tags. Consistency in protocol, host, and trailing slash is what keeps the tag doing its job.

How to Fix Canonicals on Shopify, WordPress, and Custom Sites

Shopify

Shopify adds canonical tags automatically, and the well-known quirk is that a product reachable at both /products/handle and /collections/name/products/handle canonicalizes to the clean /products/handle version, which is correct. Problems appear when an app or theme edit overrides that, or when filtered and sorted collection URLs pick up their own canonicals. Check a filtered or paginated URL here, and if the canonical does not point to the clean version, review the theme.liquid canonical logic or the app that changed it.

WordPress

Yoast and Rank Math set a self-referencing canonical on every page by default, which suits most sites. Trouble starts when two SEO plugins run at once, or when a page-builder caches an old canonical, leaving two tags on the page. Confirm each key page shows one canonical that matches its live URL, and pay attention to category, tag, and paginated archive URLs, which often need a deliberate canonical or a noindex.

Custom sites

Output one self-referencing canonical in the head of every page, built from the final, normalized URL with a fixed protocol, host, and trailing-slash rule. Redirect the non-canonical variants rather than relying on the tag alone, since a canonical is a hint and a redirect is a directive. Paste a set of URLs, including parameter and slash variants, into this tool to confirm they all resolve to and declare the one address you want indexed.

Review canonicals after any migration or URL change, because a stale tag pointing at an old domain keeps your new pages out of the results without any obvious warning.

When Duplicate URLs Appear, and How Canonicals Fix Them

Duplicate URLs rarely come from copied writing. They come from the many addresses a site hands out for the same page. Tracking parameters like utm tags, sort and filter options on a category, a printer-friendly version, pagination, and the choice between a trailing slash or none can all produce several URLs that serve one page. Left alone, Google may index the wrong one, split your links across copies, or waste crawl budget visiting all of them.

A canonical tag consolidates that mess by naming the one version you want indexed. Point every variant at the clean URL, and the ranking signals gather onto that page instead of scattering. The canonical is a strong hint, not an absolute command, so pair it with consistency: link internally to the canonical version, redirect the variants you never want served, and keep protocol, host, and slash rules identical across the site. When the hint and your other signals agree, Google follows the canonical almost every time.

Common Canonical Tag Mistakes That Hurt Rankings

The most damaging mistake is a canonical that points every page at the home page or at one hub URL, which tells Google to ignore all those pages. Nearly as harmful is a mismatched protocol or host left over from a migration, where pages on https still declare an http or non-www canonical. A page with two conflicting canonical tags is a third trap, since Google may honor neither. And a canonical that points at a URL which itself redirects sends a muddy signal that is easy to miss.

Check a representative set of URLs here, including parameter and slash variants, and confirm each one declares a single, self-referencing canonical that matches its final address. Fixing these keeps your strongest page in the index and stops copies from stealing the spot you worked to earn.

Canonical Versus Noindex Versus Redirect

These three tools solve related but different problems, and mixing them up causes trouble. Use a canonical when two URLs show the same content and you want the signals combined onto one, while keeping both reachable, such as a product available under several category paths. Use noindex when a page should stay live for visitors but never appear in search, like an internal search results page or a thin tag archive. Use a redirect when a URL should no longer exist at all and its visitors and signals belong on another page.

Avoid combining a canonical and a noindex on the same page, since the two send Google mixed instructions. For URL parameters, a self-referencing canonical on the clean version usually handles filters and tracking tags, and you can confirm the behavior by pasting parameter variants here. Review your canonicals after any migration, redesign, or move to https, because a tag left pointing at the old host or protocol is a silent way to keep your new pages out of the index. A quick check across a handful of representative URLs catches these before they cost you rankings.