SEO Tools·4 min read

Canonical Tags Explained: Which Duplicate URL Wins

Most explanations of canonical tags skip the part that matters: Google finds your pages through every URL variant that exists, not just the tidy ones you publish. Tracking parameters, session IDs, uppercase paths and print views all create addresses that serve identical content. The rel=canonical tag is how you tell Google which variant is the real one, so ranking signals pool on a single URL instead of splitting four ways. This guide covers the tag itself, a worked example, and the judgment calls around it.

Open the free Canonical Tag Generator All insights

Three URLs, one product page: how duplicates happen

Nobody creates duplicates on purpose.

An online store publishes a product at example.com/mugs/blue-mug. The email platform appends ?ref=newsletter to every link it sends. The category filter produces /mugs/blue-mug?color=blue&sort=price. Three addresses, identical content, and Google may crawl and index all of them. A review site links to one variant, a forum links to another, and the value that should lift one strong page is scattered across three weak ones.

This is the everyday case for canonicalization. It isn't about penalties, since duplicate content rarely triggers those. It's about consolidation: getting every signal pointed at the address you actually want in search results.

Canonical tags explained in a single line of HTML

The whole mechanism.

A canonical is one link element in the head of a page: <link rel="canonical" href="https://example.com/mugs/blue-mug" />. It says: whatever URL you loaded this document from, the version that counts lives at this address. Google folds the variants into that URL, shows it in results, and credits it with the links the variants earned.

It's a hint, not a directive. Google weighs the tag alongside internal links, sitemap entries and redirects, and it can override a canonical that contradicts everything else, like a tag pointing at a page that redirects away. Keep the signals in agreement and the tag is respected almost every time.

A worked example from messy URL to clean tag

Input, clean-up, output, placement.

Say a crawl report flags https://example.com/mugs/blue-mug?color=blue&ref=email as indexed. Paste it into the Canonical Tag Generator and click Inspect canonical. The tool fetches the page and shows the canonical it declares today, or reports that none was found. Either way, the URL is added to the Canonical URLs list below.

Now pick the clean-up. Remove tracking parameters strips anything starting with utm_ plus the usual click IDs and ref, which takes care of ref=email but leaves color=blue, because that parameter could change the content. Here it doesn't, so tick Remove all query parameters instead. With Force https:// on and Trailing slash set to Keep as entered, the output is <link rel="canonical" href="https://example.com/mugs/blue-mug" />.

That line goes into the head of the product template, so every parameterized variant carries it too, since they render the same template. Each variant now names the clean URL as canonical, and consolidation follows. The href is absolute, protocol and all; a relative href brings back the http versus https confusion the tag exists to settle.

Many URLs at once, and files with no head

Bulk lists and HTTP Link headers.

The Canonical URLs box takes one URL per line, so a list exported from a crawl becomes one tag per page in a single pass. The same clean-up rules apply to every line: https, a lowercase path, the trailing slash rule you pick, and tracking or all parameters removed. Consistency is the point, since one page ending in a slash and its twin without one would split signals again.

PDFs and other files have no head to put a tag in. For those, switch Output to HTTP Link header and you get a line such as Link: <https://example.com/guide.pdf>; rel="canonical", which your server sends with the file. On Apache that becomes a Header set line in .htaccess.

Canonical or redirect: which one moves the user

Both consolidate. Only one relocates.

The choice comes down to whether both URLs should keep working. A 301 redirect moves visitors: the old address stops serving content and everyone lands on the new one. A canonical leaves both pages reachable and only tells search engines where to pool the credit.

So: retired page, merged article, changed domain, use a redirect. Filtered views, tracking parameters, A/B variants, print pages, anything users still legitimately load, use a canonical. If you're adding a canonical because a redirect would break something, that's the tag doing exactly its job.

Canonical tag mistakes Google quietly ignores

The tag fails silently.

A broken canonical doesn't throw an error anywhere. Google just stops trusting it, and you find out months later in the indexing report. The recurring offenders:

Two canonical tags on one page, usually a theme and a plugin each adding their own; with conflicting targets, both may be ignored.
A canonical pointing at a URL that 404s or redirects, which asks Google to consolidate onto something that isn't there.
Canonicalizing every paginated page to page one, hiding everything listed beyond it.
Pointing the tag at another URL while the page also carries noindex, two signals that contradict each other.
Canonicalizing pages whose content really differs, which Google detects and overrides.

Self-referencing canonicals and two other habits

Small effort, lasting payoff.

First habit: give every indexable page a canonical pointing at itself. It looks redundant until an email platform or an affiliate starts adding parameters you never planned for; the tag is already there, absorbing whatever gets appended.

Second, check what's actually rendered, not what your CMS settings claim, because plugins overwrite each other. Inspect canonical shows what a live page declares before you change anything. Third, keep canonical targets consistent with your sitemap and internal links. When all three name the same URL, Google has no reason to pick its own winner.

When the Canonical Tag Generator isn't the right tool

Neighbors on the shelf.

Reach for the Canonical Tag Generator when duplicate URLs should all stay live. The moment a URL should stop existing, switch to the Htaccess Redirect Generator and write a 301 instead. To see a page's canonical alongside its title, description and other head tags, the Meta Tag Analyzer reports them in one pass. Inspect canonical also follows the target and warns when it redirects, errors or names yet another canonical, which is the quiet way canonicals go wrong.

Try it now

Open Canonical Tag Generator

The tool is one click away. No sign up, no upload, no payment.

Open Canonical Tag Generator

Write a review