Learn
Duplicate Content Canonicalization Guide: Fix Canonical Tags, Parameters, and URL Variants
A practical guide to duplicate content and canonicalization: where variant URLs come from, how to choose between canonical, redirect, and noindex, and how to consolidate safely.
Run a fresh DomainLens audit and use the report as your priority list.
What duplicate content really costs you
There is no "duplicate content penalty" in the way people fear. What actually happens is dilution and unpredictability: when the same content sits on several URLs, Google has to pick one to index and rank, and it might not pick the one you want. Links, crawl attention, and ranking signals get split across the variants instead of concentrating on a single strong URL.
It also wastes crawl budget. On a large site, thousands of near-identical parameter and filter URLs mean Google spends its time re-crawling copies instead of discovering your genuinely new pages — a problem that compounds as the site grows.
Where duplicate URLs come from
Duplication is rarely someone copying an article. It is almost always the same page reachable through many URLs:
- Protocol and host variants: http vs https, www vs non-www, trailing slash vs not.
- Tracking and session parameters: ?utm_source=…, ?sessionid=…, that change the URL but not the content.
- Faceted navigation and sort orders: ?color=red&sort=price producing endless combinations.
- Pagination and "view all" versions of the same list.
- Uppercase/lowercase paths, index.html vs /, and printer or AMP variants.
Canonical, redirect, or noindex: choosing the tool
These are not interchangeable — pick by what you want to happen to the duplicate URL.
- 301 redirect: when the duplicate should not exist as its own URL at all (http→https, www consolidation, old→new). It consolidates signals and removes the variant.
- rel="canonical": when both URLs must stay reachable but only one should rank (parameter variants, a product in two categories). It is a hint, not a directive — keep the pages near-identical or Google may override it.
- noindex: when the page must stay accessible to users but must never rank (internal search results, thin filter combinations). Do not combine noindex with canonical to another URL.
- robots.txt: not a deduplication tool — it blocks crawling, which prevents Google from even seeing your canonical.
How to consolidate duplicates safely
- Decide the single canonical URL for each piece of content and make internal links, sitemaps, and canonicals all point to it.
- Enforce one host and protocol with a site-wide 301, and normalise trailing slashes and case.
- For parameters that do not change content, canonical them to the clean URL; for facets that create value, decide case by case whether to index.
- Make the canonical self-referential on the URL you want to rank, so it is not accidentally pointing elsewhere.
- Roll changes out per template and re-crawl before applying the pattern site-wide.
Mistakes that make duplication worse
- Blocking duplicate URLs in robots.txt, which stops Google reading the canonical that would have consolidated them.
- Canonicalising to a page that is itself redirected or noindexed, which invalidates the hint.
- Pointing every paginated page’s canonical at page 1, which hides the deeper items from indexing.
- Mixing signals: a canonical to URL A while internal links, sitemap, and hreflang all point to URL B.
How to validate consolidation
Use URL Inspection on a duplicate and confirm Google reports your chosen URL as the "Google-selected canonical", then watch the "Duplicate" and "Alternate page" buckets in the Page Indexing report shrink over the following weeks as consolidation takes effect.
In DomainLens, the canonical target and status code are surfaced together, so a page whose canonical points somewhere unexpected — or a variant that returns 200 when it should redirect — shows up as a conflict you can fix before it splits your ranking signals.