5 min readNodedr Team

Canonical Tags Explained

SEOTechnical SEO

The Problem Canonical Tags Solve

Most websites have more duplicate or near-duplicate pages than their owners realize. Not copy-pasted content — the same page, reachable through more than one URL. A canonical tag is how you tell Google "these are the same page, and this one is the version that should count."

Here's a concrete example. An e-commerce product page might be reachable at:

  • yoursite.com/products/leather-wallet
  • yoursite.com/products/leather-wallet?color=brown
  • yoursite.com/shop/mens/leather-wallet
  • yoursite.com/products/leather-wallet/ (with a trailing slash)

To a visitor, these all show the same wallet. To a search engine, without guidance, these can look like four separate pages with identical or near-identical content — competing against each other instead of one strong page pulling all the ranking value.

What a Canonical Tag Actually Looks Like

It's a single line in the <head> of your HTML:

<link rel="canonical" href="https://yoursite.com/products/leather-wallet" />

Every one of the four URL variations above would carry this same tag, pointing back to the one you've designated as the "real" version. Google still crawls the other URLs if it encounters them, but it treats them as duplicates of the canonical target and consolidates ranking signals (like links pointing to any of the variants) onto that one page.

Crucially, a canonical tag is a strong suggestion, not a command. Google generally respects it, but if the "duplicate" pages actually have meaningfully different content, Google can decide to ignore the tag and index them separately anyway. This is worth knowing because it means canonical tags don't fix genuinely different pages that happen to be similar — they fix pages that are truly the same content under different URLs.

Common Situations That Create Duplicates

URL Parameters

Tracking parameters, filters, and sorting options are the most frequent source. ?utm_source=facebook, ?sort=price-asc, ?ref=email — all append to a URL without changing the underlying content, and all should canonicalize back to the clean URL.

WWW vs Non-WWW, and HTTP vs HTTPS

If both https://yoursite.com and https://www.yoursite.com load your site without a redirect between them, you effectively have two competing copies of every single page. This should ideally be solved with a 301 redirect forcing one version, with canonical tags as a backup safety net.

Printer-Friendly or AMP Versions

A stripped-down print or mobile version of a page, served at its own URL, should canonicalize to the full version.

Syndicated or Cross-Posted Content

If you publish the same article on your blog and also on a partner site or LinkedIn, the syndicated copy should canonicalize back to your original — assuming the platform supports it (LinkedIn articles don't; a standard partner blog usually does).

E-Commerce Category Overlap

A product that appears under both "Men's Accessories" and "New Arrivals" categories often generates two URLs for one product. One should be canonical; the other should point to it.

When You Don't Need a Canonical Tag

Not every similar page is a duplicate problem. Two service pages — say, "Roof Repair" and "Roof Replacement" — might share language and structure but describe genuinely different offerings. Don't canonicalize one to the other just because they look alike; that would tell Google to stop considering one of them entirely, which is the opposite of what you want if both deserve to rank for their own searches.

Location pages for a multi-branch business are a similar case. A plumbing company with pages for "Plumber in Austin" and "Plumber in San Antonio" should keep both as distinct, canonical pages in their own right — even if 80% of the copy is templated — because each targets a different, real search intent. The fix there is writing enough unique content per location (specific service areas, local details, distinct reviews) that they don't read as duplicates in the first place, which overlaps with concerns around duplicate content more broadly.

Self-Referencing Canonicals

A detail that surprises people: even pages with no duplicate should typically carry a canonical tag pointing to themselves. If yoursite.com/about is the only version of that page, its canonical tag is simply:

<link rel="canonical" href="https://yoursite.com/about" />

This isn't redundant — it's a safeguard. If someone links to your page with a tracking parameter or a different capitalization, the self-referencing canonical makes clear to Google which version is authoritative regardless of how a visitor arrived. Most modern CMS platforms and site builders (WordPress with an SEO plugin, Shopify, Next.js with reasonable defaults) add this automatically for every page. It's worth spot-checking a few pages on your site to confirm it's actually happening rather than assuming.

How to Check Your Site

View the page source (or use your browser's "view source" / inspect tool) on a handful of key pages and search for rel="canonical". Confirm:

  • Every important page has exactly one canonical tag.
  • The canonical URL uses your final domain format (HTTPS, correct www/non-www) and matches what you'd want in search results.
  • Pages that are genuinely duplicates point to the one true version.
  • Pages that are genuinely unique don't accidentally point somewhere else.

Google Search Console's "Page indexing" report also shows a "Duplicate, Google chose different canonical than user" status — that specific message means Google disagreed with your canonical tag, which is worth investigating rather than ignoring, since it usually means the pages aren't as similar (or as different) as your setup assumes.

Canonical tags are a small piece of technical SEO, but they're one of the more common misconfigurations on sites that have grown organically over a few years — new URL structures added, old ones never cleaned up, a migration that didn't account for parameters. A quick audit every so often is worth the twenty minutes it takes.

Share:

Planning a new website?

Let's talk about how a fast, SEO-ready Next.js site can help your business grow.

Start Your Project