Canonical Tags: What They Are, How to Use Them, and 9 Mistakes to Avoid

Most websites have far more URLs than pages. The same product can be reached with and without www, with tracking parameters, with a sort order, through two different categories. To Google, every one of those URLs is a separate address showing the same content, and it has to pick one to show in search.

A canonical tag is how you tell Google which one you want. Get it right and your ranking signals pile up on one strong URL. Get it wrong and you can point Google at the wrong page, a redirect, or a 404, and watch the right page disappear from search.

This guide explains what canonical tags do, when to use them, how to check them, and the nine mistakes that cause the most damage.

What is a canonical tag?#

A canonical tag is a line in a page's <head> that names the preferred URL for that content:

<link rel="canonical" href="https://example.com/trail-running-shoes/" />

Put that on every version of the page (the one with tracking parameters, the one sorted by price, the one reached through a different category) and you're telling search engines: "these are all the same page; index and rank this URL."

The canonical URL is the one Google shows in search results and the one that collects ranking signals such as links. The duplicates are crawled less often and usually don't appear in results.

A canonical tag is a hint, not a command#

This is the part most guides skip. Google treats rel="canonical" as a strong signal, not an order. It weighs your canonical tag alongside other clues:

• Redirects pointing to a URL
• Which URL you link to internally
• Which URL is in your sitemap
• HTTPS over HTTP
• hreflang annotations

When those signals agree, Google almost always follows your canonical tag. When they contradict each other (your canonical says one URL, your internal links and sitemap say another), Google may pick a different canonical than the one you declared. That's why the fix for canonical problems is usually consistency, not a stronger tag.

When to use canonical tags#

URL parameters. Tracking codes (?utm_source=newsletter), sorting (?sort=price), session IDs and filters create endless variations of the same page. Each should canonicalize to the clean URL.

Protocol and hostname variations. http://, https://, www and non-www versions should redirect to one version. A canonical tag on that version is a useful backup.

Products in several categories. If /men/shoes/trail-runner and /sale/trail-runner show the same product, choose one and point the other to it.

Syndicated content, with care. Cross-domain canonicals are allowed, but Google no longer recommends them for syndication, because a partner's copy often differs from your original. If another site republishes your article and you want to keep their copy out of Google, ask them to noindex it and link back to your original.

Non-HTML files. PDFs can't hold a <link> tag, but you can send a canonical in the HTTP header: Link: <https://example.com/guide/>; rel="canonical".

Every page, pointing at itself. Google recommends a self-referencing canonical on canonical pages too. It protects you against parameter variations you didn't anticipate.

Canonical tag vs. 301 redirect vs. noindex#

How to check your canonical tags#

1. View the page source and search for rel="canonical". There should be exactly one, in the <head>, with a full absolute URL.
2. Use a canonical checker. MyKavo's free Canonical Tag Checker finds every canonical a page declares, in its HTML and HTTP headers, spots conflicting ones, and checks that the canonical URL returns 200, doesn't redirect and isn't noindexed.
3. Ask Google. In Search Console, URL Inspection shows the user-declared canonical next to the Google-selected canonical. If they differ, Google has overruled your tag, and the rest of your signals are probably disagreeing with it.
4. Check the Page indexing report. "Duplicate, Google chose different canonical than user" is the status that deserves attention. "Alternate page with proper canonical tag" is usually fine: it means Google found a duplicate and followed your canonical as intended.

The 9 canonical tag mistakes that cost rankings#

1. Canonical pointing to a redirect, 404 or noindexed page. Your canonical must point at a live page that returns 200 and can be indexed. After a migration, old canonical tags often point at URLs that now redirect. Check the target, not just the tag.

2. More than one canonical tag. A theme and an SEO plugin each add their own, with different URLs. Google's advice is clear: when a page declares conflicting canonicals, Google is likely to ignore all of them.

3. Relative URLs. <link rel="canonical" href="/shoes/"> is technically allowed but easy to break, especially on sites served on several hostnames. Use the full https:// URL.

4. A canonical tag in the <body>. Google only accepts rel="canonical" in the <head>. Scripts or badly closed tags can push it into the body, where it's ignored.

5. Every paginated page canonicalized to page 1. Page 2 of a category isn't a duplicate of page 1: it lists different products. Point each paginated page to itself, or the products on deeper pages may never be found.

6. Canonicalizing different content. A canonical tag says "these pages are the same". Pointing a category page at a featured product, or every blog post at the homepage, isn't consolidation, and Google will likely ignore it.

7. Mixed signals. The canonical says https://example.com/page/ but the sitemap lists https://www.example.com/page, and the navigation links to a third variant. Make your canonical, sitemap and internal links agree.

8. JavaScript changing the canonical. If the HTML says one canonical and JavaScript rewrites it to another, Google may see either. Put the correct canonical in the HTML source and don't change it with JavaScript.

9. Canonical tags that fight hreflang. On multilingual sites, each language version should point to itself as canonical. If your German page canonicalizes to the English page, Google treats it as a duplicate of the English one. Our hreflang guide covers that pairing in detail.

Why canonical tags change without warning#

Canonical tags are usually generated by your CMS, theme or SEO plugin, not written by hand. That means they change when those change: a plugin update alters the format, a theme switch drops the tag entirely, a migration leaves every canonical pointing at the old domain. Nothing breaks visibly. The page looks exactly the same.

MyKavo watches the canonical tag on the pages you monitor against an approved baseline and alerts you when it's changed or removed, with the old and new values side by side, so a bad update is caught on the first scan instead of after rankings fall.

The bottom line#

Canonical tags tell search engines which URL to rank when the same content lives at several addresses. Use one absolute canonical per page, point it at a live, indexable URL, keep your sitemap and internal links consistent with it, and check what Google actually chose in Search Console.

Check any page now with the free Canonical Tag Checker, then start free with MyKavo so you hear the day a canonical changes.