Duplicate content splits ranking signals across multiple URLs instead of consolidating them on one. A canonical tag tells Google which version counts — here is how to use one correctly.
Duplicate content is more common than most site owners realize. A product page reachable via /shoes/red-sneaker and /shoes/red-sneaker?color=red looks like two different pages to a search engine, even though a human sees the same content. A rel="canonical" tag solves this by explicitly declaring which URL is the authoritative version.
Placed in the <head> of a page, a canonical tag looks like this: <link rel="canonical" href="https://example.com/shoes/red-sneaker" />. It tells search engines: "if you find this content at multiple URLs, treat this one as the original, and consolidate ranking signals — links, relevance, authority — onto it."
This matters because duplicate or near-duplicate URLs without canonicalization split signals across multiple pages instead of concentrating them on one. A page with ten backlinks split across three duplicate URLs ranks worse than the same page with all ten backlinks consolidated onto a single canonical URL.
?utm_source=...), sort orders, and session IDs all create technically distinct URLs serving identical content./page and /page/ can be treated as different URLs depending on server configuration.It's worth being precise about when to use which. A redirect (see our 301 Redirect Generator) is for URLs that should no longer exist at all — the old URL goes away and users are sent to the new one. A canonical tag is for URLs that legitimately need to keep working — like a parameterized filter view — but shouldn't compete with the main page for ranking. Using a 301 where a canonical is appropriate (or vice versa) is one of the most common technical SEO mistakes.
Best practice is to add a self-referencing canonical tag to every page — even ones with no duplication risk — pointing to its own URL. This removes ambiguity if the page is ever later accessed through an unexpected parameter combination, and it's a cheap, low-risk default to apply site-wide.
If you're restructuring URLs — running titles through the Slug Generator to clean up a legacy permalink structure, for instance — canonical tags and redirects work together. The old URL should 301 redirect to the new one; the new URL should self-canonicalize. Skipping the redirect and relying on a canonical tag alone leaves the old URL live and indexable, which re-introduces the duplication problem you were trying to solve.
Get this right once, early, and it quietly prevents a whole category of ranking problems that are otherwise hard to diagnose after the fact — because nothing looks "broken," the signals are just diluted.
No sign-up required — use them instantly in your browser.