Canonical Tags, Explained

A canonical tag is a hint, not a command — and mixing that up causes most of the mistakes businesses make with it. Here's exactly what it does and how to use it correctly.

Bartu Cavusoglu

Founder, Vazagency · Runs reputation recovery and SEO campaigns for businesses across 35+ industries.

9 min read·Updated July 2026

The canonical tag is one of the most-used and most-misunderstood tools in technical SEO. It looks simple — one line of HTML in the page's <head> — but the mechanics of what it actually does, and what it doesn't, trip up even experienced site owners. This guide covers exactly what a canonical tag does, when to use one, and the mistakes that quietly undo it.

What a canonical tag is

A canonical tag is an HTML element that looks like this: <link rel="canonical" href="https://example.com/preferred-url/" />. It sits in the page's head section and tells search engines: "if you've found this content at more than one URL, treat this specific URL as the authoritative, indexable version." It exists to solve a genuine and common problem — the same or nearly identical content is very frequently reachable at more than one URL on a real website, often without the site owner realizing it.

A hint, not a directive

This is the single most important thing to understand: Google explicitly treats the canonical tag as one signal among several, not a binding instruction. Google's own documentation describes weighing the declared canonical against other signals — internal linking patterns (which URL do most of your own links point to), the presence of redirects, sitemap entries, and how similar the pages actually are — before deciding which URL to treat as canonical.

What happens when Google disagrees with your declared canonical

In Google Search Console's URL Inspection tool, you'll sometimes see two different fields: "User-declared canonical" (what your tag says) and "Google-selected canonical" (what Google actually chose). When these don't match, it's usually because other signals — like internal links pointing to a different version, or the two pages not being similar enough to count as duplicates — contradicted the tag. It's a genuinely useful diagnostic, not a bug.

When you actually need a canonical tag

Parameter-heavy URLs

Tracking parameters, session IDs, sort orders, and filter combinations often create multiple URLs serving the same or near-identical content — for example /services?sort=price and /services?utm_source=email both showing the same underlying service list. Canonicalizing all variants to the clean base URL prevents them from competing with each other as separate, weaker versions of the same page.

HTTP vs. HTTPS, and www vs. non-www

If your site is technically reachable at more than one of these variants (even if you've set up redirects, belt-and-suspenders canonicalization is standard practice), a canonical tag reinforces which version is the one that should actually get indexed.

Syndicated or cross-posted content

If you publish the same article on your own site and also syndicate it to a partner site or platform, a canonical tag on the syndicated copy pointing back to your original is the standard way to make sure your site gets credit as the source.

Paginated and filtered category pages

This one is more nuanced than it looks, and it's easy to misuse — see pagination and SEO, explained for the full mechanics of when paginated pages should self-canonicalize versus canonicalize to page one.

Print-friendly or alternate-format versions

A "print view" of an article or product page is genuinely duplicate content. Canonicalizing it back to the main version keeps it from being indexed as a separate, thinner competing page.

Self-referencing canonicals as a default

Best practice, and what most modern CMS platforms and SEO plugins do automatically, is to include a self-referencing canonical tag on every indexable page — a page's canonical tag simply points to its own URL. This costs nothing and protects against future duplication you haven't created yet, like a parameterized version some third-party tool or campaign link generates later.

Mistakes that quietly break canonical tags

Canonicalizing to a noindexed or blocked page — pointing a canonical tag at a URL that's itself set to noindex, or blocked from crawling in robots.txt, creates a contradiction search engines have to resolve on their own, often unpredictably.
Canonical chains — page A canonicalizes to page B, which canonicalizes to page C. Every canonical tag should point directly to the final, real destination in one hop.
Cross-domain canonicals used incorrectly — pointing your own original content's canonical at someone else's domain hands away credit for content that's actually yours.
Canonical tags that don't match the actual content — declaring a canonical to a page that isn't a genuine duplicate or near-duplicate is a strong signal to Google that your declared canonical isn't reliable, which can cause it to be ignored site-wide, not just on that one page.
Relying on a canonical tag instead of a redirect — when a page should genuinely stop existing (a discontinued service, a merged location page), a canonical tag is the wrong tool; use a 301 redirect instead.

How to check what Google actually chose

Two ways: first, view a page's raw HTML source and confirm the canonical tag is present, correct, and points where you intend. Second, and more reliably, use the URL Inspection tool in Google Search Console — it shows both your declared canonical and Google's actual selected canonical for that URL, which is the only way to know for certain whether Google agreed with your tag or overrode it based on other signals.

Canonical tags work alongside other duplicate-content and indexing tools, each with a distinct job. See robots.txt vs. noindex vs. canonical for how these three commonly confused mechanisms differ, and how to fix duplicate content issues for the broader picture of resolving duplication site-wide.

Frequently asked questions

Is a canonical tag a command that Google has to follow?

No, and this is the single most misunderstood thing about canonical tags. Google itself describes the canonical tag as a hint, not a directive — one of several signals it weighs alongside internal linking patterns, redirects, sitemaps, and its own crawl data. In the majority of cases Google respects a clearly and correctly implemented canonical tag, but it can and sometimes does choose a different URL as canonical if other signals point elsewhere.

Does a canonical tag stop Google from crawling or indexing the non-canonical page?

No. Both the canonical page and the page pointing to it typically still get crawled — the tag doesn't block crawling the way a robots.txt disallow does. What it affects is indexing and ranking consolidation: Google generally won't show the non-canonical duplicate as a separate result and will attribute ranking signals (like links) to the canonical version instead. The non-canonical URL can still appear in Search Console reports and still gets visited by Googlebot periodically.

Can I use a canonical tag to point one page's content to a completely unrelated page?

You can technically write the code, but it won't work the way you might hope. Canonical tags are meant for genuine duplicates or near-duplicates — the same or very similar content reachable through different URLs. Pointing a canonical tag at an unrelated page is a well-known error pattern, and Google is generally good at detecting when a declared canonical doesn't actually match the page's content, in which case it ignores your declaration and picks its own.

What's the difference between a canonical tag and a 301 redirect?

A 301 redirect actually sends visitors and crawlers to a different URL — the original URL stops being accessible as its own page. A canonical tag leaves both URLs live and accessible; it's purely a signal about which one should be treated as authoritative for indexing purposes. Use a redirect when a URL should permanently cease to exist as its own page. Use a canonical tag when both URLs need to remain accessible (often for legitimate reasons, like a filtered product view) but only one should be indexed. See the guide on 301 redirects for more on when to use one.

Do I need a canonical tag on every page, even ones with no duplicate?

Yes, as a default best practice — every indexable page should include a self-referencing canonical tag, meaning it points to itself. This isn't strictly required in every case, but it's cheap insurance: it removes any ambiguity if a duplicate or parameterized version of that URL ever gets created later (intentionally or not), and it's the standard most CMS platforms and SEO plugins now apply automatically.

Put this into practice

301 Redirect Generator

More guides

Robots.txt vs. Noindex vs. Canonical: What's the Difference?How to Fix Duplicate Content Issues Pagination and SEO, Explained What Is a 301 Redirect, and When Should You Use One?Website Structure for SEO

Want this handled for you?

We build the SEO foundation and handle the ongoing work — no long-term contract, no guaranteed-rankings sales pitch.

Get in touch See our SEO Foundation