Duplicate Content Risk Review
Key takeawayOne product can exist at a dozen addresses because of host name, parameters, pagination and language versions, and the system must pick one to show. This sheet works from URL layer to page layer to content layer, consolidating what should merge and separating what should not.
Industries and use cases
- Standardising URLs before a new site launches
- After product variants and language versions multiply
- When indexed pages far exceed the real page count
- When a campaign landing page closely mirrors an existing page
Checklist
| Check item | Pass criteria | Risk level | Fix hint |
|---|---|---|---|
| Protocol and host form | Only one canonical version of http or https and www or non-www is kept | High | 301 the other three to the canonical version so content is not split four ways. |
| Trailing slash | One form with or without the trailing slash is kept and the other redirects | Medium | Handle it at server level and keep template links in one style. |
| Case convention | Paths are lowercase and case variants 301 to the lowercase address | Medium | This matters most on case-sensitive servers, so add rewrite rules. |
| Parameter combinations | Sort, filter and tracking parameters do not create indexable pages | High | Canonicalise or restrict combinations with no standalone value. |
| Pagination | Paginated pages canonical to themselves and are not forced to page one | Medium | Later pages carry different items, so pointing them at page one hides them from indexing. |
| Product variants | Colour and size variants merge on the main product page or carry unique descriptions | High | Merge variants that differ only by parameter so dozens of near-duplicates do not compete. |
| Language and region | Each language version canonicals to itself and is separated by language annotation | High | Cross-language canonicals remove non-primary versions from display entirely. |
| Print and plain text views | Print or plain text pages are noindexed or canonical to the main article | Low | These pages add no standalone value and need not be indexed separately. |
| Aggregation and tag pages | Thin tag, author and archive pages are restricted or merged | Medium | Keep pages with real aggregation value and consolidate the rest. |
| Self canonical | Normal pages canonical to their own URL without gaps or cross-page targets | High | Output at template level and spot check source after a redesign. |
| Body duplication | Body text overlap between pages on the same site stays below 30% | Medium | Do not paste supplier copy wholesale; add application notes and parameter explanations. |
| Cross-site copies | Content mirrored to other domains does not remain indexed | Medium | Handle mirrors with canonical signals and direct contact before filing complaints. |
Common misjudgements
- Assuming two identical pages are both duplicates, when one is correctly canonicalised or redirected and only one participates in the index.
- Canonicalising every paginated page to page one, which removes the chance for page two and beyond to be crawled.
- Canonicalising across language versions: translated content differs, so cross-language canonicals are a configuration error, not deduplication.
How to use this checklist
- Pair with the hreflang sheet: language versions are separated by annotation, not merged by canonical.
- Run when a product line or variants are added and do a full quarterly scan.
- Link with the redirect sheet, since redirects are one deduplication method.
FAQ
How similar does content have to be to count as duplicate?
There is no published threshold; the test is whether a page offers standalone value, not a similarity ratio.
Should canonical or 301 be used?
Use a 301 when the old address is retired; use canonical when both addresses must stay reachable.
Is duplicate content penalised?
Usually not; the system picks one version to show and filters the other.
Version notes2026-11-21: first release, compiled from official Google documentation and public sources; updated as engine rules and regulations change.
If you prefer not to verify each item yourself, a pre-checked B2B template site package is available as an alternative.
Related checklists
hreflang Configuration Review for Multilingual Sitesrobots.txt Configuration Checks and Common MistakesXML Sitemap Creation, Submission and ValidationCrawl Budget and Index Permission Review for New Sites404 and Redirect Configuration ReviewNote: this checklist is a self-check reference only. Search-engine behaviour and regulations follow the latest official documentation of each provider and jurisdiction.