The canonical tag is the most overused and underthought line of code in technical SEO. On one hand, it's the fix for duplicate content. On the other, a canonical slapped on lazily can quietly merge your two best pages into one weaker version and slice your traffic in half — and no error message ever tells you.
What a canonical actually does
A rel="canonical" is a declaration: among several URLs that look related, this one is the one I want indexed. When search engines trust it, they consolidate the signals — the link equity, the ranking potential — toward the canonical and stop treating the others as separate pages.
That's powerful, and that's exactly why misuse is dangerous. You're telling the engine which of your pages deserves the credit. Get that decision wrong and you've done the merging yourself.
When it's clearly right
Use canonicals when you truly have duplicates that serve the same intent:
- A page reachable via multiple URLs (trailing slash, uppercase, tracking params).
- Two pages carrying essentially the same content for the same search, where one should win.
- Print versions, session variants, and international variants handled by other means.
In these cases, a canonical protects you from your own redundancy. It's the right tool.
When it's quietly costing you
Here's where the harm creeps in:
Merging pages that should stand alone. If two pages have meaningfully different content and each targets a separate buyer question, forcing one to be the canonical of the other tells Google to pick a winner — and usually leaves the other page all but ignored. You didn't have duplicate content; you had two opportunities, and you folded them into one.
Canonicalizing pagination. Long-ago best practice said canonicalize page 2, 3, and 4 to page 1. Modern guidance is the opposite: self-canonicalize each, because page 3 answering a distinct query is still a real page. Pointing an archive series at page one can bury your later content.
A canonical pointing somewhere broken. Pointing a canonical at a redirect, a noindexed page, or a 404 is the fastest way to tell Google "this content doesn't matter" — and it usually obeys.
Contradictory signals. A self-canonical plus an internal link telling the engine one thing, plus a sitemap telling it another, equals confusion. The engine resolves confusion toward caution, and caution often means "index the weaker one."
The rule that keeps it safe
Before you add a canonical, answer one question honestly: are these URLs really the same thing, or are they related but different? If they're the same, canonical. If they're different — different intent, different audience, different content — they deserve to be separate pages with their own links and their own chances.
The mistake isn't using canonicals. It's reaching for them as a default whenever content overlaps, instead of thinking about whether you'd rather have one strong page or let two each compete.
A canonical audit is a traffic audit
Walk your biggest pages and check who's being canonicalized to whom. You may find a page you've quietly demoted. Fixing an aggressive canonical has, in our experience, restored meaningful traffic that had been silently merged away for months.
Want us to look at whether your canonicals are helping or erasing value? Book a free website teardown and we'll audit your canonicalization alongside the duplicate-content issues it's supposed to solve.