Technical SEO · Supporting checklist

Duplicate Content Audit Checklist

A duplicate content audit checklist is a decision workflow for pages that repeat the same main content across different addresses. Use these duplicate content checks to discover candidate clusters, compare their purpose and choose between consolidation, retained copies and distinct content. Finish with a practical treatment for each real cluster. A similarity warning alone is not a reason to delete a page, and ordinary duplication is not automatically a spam violation.

Free to useNo account neededSaved in your browser
Repeated paper pages compared with a selected consolidated page and a pair of distinct pages.
Compare duplicate groups before choosing consolidation or distinct content.
Your working checklist

Work through the checklist

Click a square to mark a task as Pass. Click again to undo. Use the result menu for a problem, a blocker or a task that does not apply. You do not need to enter notes.

14 checks

Find Genuine Duplicate Content

Duplicate content means substantially the same main content is available at more than one address. Start with candidate pairs, then compare what each page actually provides before choosing a fix.

Collect the URL versions that need comparison

Find duplicates that a simple navigation crawl may miss.

Use this for: Sites with multiple routes, parameters or suspected repeated content.

Combine a current page crawl with your CMS page list or sitemap. Add known alternate hosts, protocol versions, old routes, print pages and parameter examples that are relevant to your site. Search Console duplicate indexing reasons can suggest further candidates; they are not a complete inventory.

Keep the review bounded. You need representative examples of each pattern, not an unlimited crawl of every filter combination. Compare excluded or unfetched URLs separately so they do not disappear from the conclusion.

Example

Hypothetical example: A shop crawl finds /products/clay-pot/, while the CMS also exposes it beneath /sale/clay-pot/. Add that second route to the comparison.

  1. Gather the public page inventory and known alternate address patterns.
  2. Add candidate pairs from sitemap, CMS and indexing reports where available.
  3. Mark which patterns were fetched and which still need access or investigation.
More help and optional notesMedium · Website owner or SEO lead
PassThe known duplicate-producing patterns are included in the comparison scope, with untested areas identified.
FailA known alternate host, template or route pattern is omitted while the audit is treated as complete.

If it fails: Add representative missing variants and fetch their actual content.

Retest: Check that each known pattern has a comparable page pair or an explicit unresolved access state.

Not applicable: No public or ready-to-test content exists in scope.

Keep in mind: Blocked: You cannot obtain the page inventory or access the suspected variants. Passing this discovery task does not mean the site is free of duplicates.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare the main content behind duplicate reports

Use a tool match as a candidate, not an automatic deletion rule.

Use this for: Exact, near-duplicate or repeated-metadata candidates.

Open each candidate pair side by side. Compare its main answer, products, specifications and purpose. Matching titles, headings or descriptions alone do not establish that the page bodies are duplicates.

If you use a licensed Screaming Frog setup, enable Near Duplicates under Config → Content → Duplicates, finish the crawl, then choose Crawl Analysis → Start. Review the Content tab’s Exact Duplicates and Near Duplicates filters and inspect the matching passages. Check whether the report excludes non-indexable pages. Without that feature, compare the pages manually; a tool’s similarity threshold is not a Google cutoff.

Example

Hypothetical example: Two pages share the heading “Care instructions,” but one explains glazed pots and the other unglazed pots. Read the instructions before deciding they should be merged.

  1. Open a candidate pair and compare the principal content.
  2. Check that the tool’s similarity analysis finished and covers the intended URLs.
  3. Classify the pair as equivalent content, distinct content or unresolved.
More help and optional notesMedium · Website owner or SEO lead
PassThe reviewed pairs are classified from their main content and purpose, with the report’s scope understood.
FailThe conclusion relies only on matching metadata or an unexplained similarity score.

If it fails: Review the body content and adjust the analysis scope before selecting a remedy.

Retest: Compare the same pair again with the correct content area and settings.

Not applicable: The discovery review found no candidate duplicate pairs.

Keep in mind: Blocked: Page content or the required comparison output is unavailable.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Remove menu and failed-render matches from the diagnosis

Avoid rewriting distinct pages because their shared template dominates a report.

Use this for: Unexpected matches, template-heavy pages and JavaScript-rendered content.

Look at the actual text used for a suspicious match. Repeated navigation, consent banners, footer text, a common login screen or an empty application shell can make different pages appear alike. Compare the rendered main content with the fetched content.

If the extraction area is wrong, adjust the comparison to the page’s main content and rerun it. If important content never loads, investigate that delivery or rendering failure first. Do not exclude genuine repeated body content merely to obtain a better similarity score.

Example

Hypothetical example: A service site’s crawl compares only its menu and “Loading” message. The visible services differ after rendering, so fix the crawl/render investigation before merging pages.

  1. Inspect the text or HTML behind the duplicate match.
  2. Separate shared page furniture from meaningful body content.
  3. Correct extraction or investigate missing content, then compare again.
More help and optional notesMedium · Website owner or SEO lead
PassThe comparison uses the intended main content, and any remaining match is genuine rather than an extraction failure.
FailThe result is driven by irrelevant template text or failed content retrieval.

If it fails: Correct the analysis area or the rendering/access problem and rerun the affected sample.

Retest: Compare the newly extracted content with what a visitor receives.

Not applicable: The verified comparison already uses complete main content without a false-match pattern.

Keep in mind: Blocked: You cannot inspect the extracted text or render the relevant content.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Identify Why the Copies Exist

Technical duplicates and overlapping editorial pages need different repairs. Test the cause before deciding whether to redirect, retain a copy or improve distinct content.

Compare protocol, host, case and slash variants

Identify duplicate delivery of one page through alternate addresses.

Use this for: Sites that expose alternate protocol, host, case or slash forms.

For representative pages, test the alternate versions your site actually supports: HTTP and HTTPS, www and non-www, case variants or a trailing slash. Check whether they redirect, return the same content separately or serve genuinely different resources.

Group variants only when they represent the same page. A different hostname may belong to a separate app, and case can matter on some systems. Keep the observed response separate from the decision about which address should represent the content.

Example

Hypothetical example: Both /delivery and /delivery/ return the same full page without redirecting. Treat them as one duplicate cluster; do not invent two different articles to fill the routes.

  1. Choose a representative URL for each relevant template.
  2. Open its supported address variants and compare responses and content.
  3. Group equivalent versions and identify any deliberate exceptions.
More help and optional notesMedium · Website owner or SEO lead
PassEach tested variant is correctly classified as a redirect, an equivalent copy or a genuinely separate resource.
FailAn equivalent copy or a meaningful difference is misclassified or left unexplained.

If it fails: Correct the cluster classification and route equivalent-address repairs to the appropriate URL/canonical workflow.

Retest: Repeat the variant sample after implementation.

Not applicable: The platform exposes none of these variants beyond its single intended address form.

Keep in mind: Blocked: The alternate host or response cannot be inspected. This is a diagnosis task. A known uncorrected duplicate can remain in a correctly classified cluster.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Separate tracking copies from content-changing parameters

Avoid consolidating a useful page just because its address contains a question mark.

Use this for: Sites using tracking, sort, filter, product-variant or pagination parameters.

Take one parameter at a time and compare the page with and without it. Determine whether it changes only tracking, reorders the same material, selects a different product variant or shows a different set of items. Check combinations that your navigation actually creates.

Group equivalent views for a consolidation decision. Keep a filtered landing page or a pagination page separate when it serves materially different content or a distinct visitor need. A parameter name alone cannot decide its treatment.

Example

Hypothetical example: A ref parameter leaves a guide unchanged, while page=2 opens a different set of products. They should not receive the same duplicate-content fix.

  1. List parameters observed in links or reports.
  2. Compare representative values with the base page.
  3. Classify each pattern by its actual content and user purpose.
More help and optional notesMedium · Website owner or SEO lead
PassEach reviewed parameter pattern has a correct content-based classification and intended treatment.
FailAll parameters are labeled duplicates, or an unchanged copy is mistaken for a distinct page.

If it fails: Correct the classification before changing redirects, canonicals or indexing controls.

Retest: Repeat the content comparison with the same values and representative combinations.

Not applicable: No query parameters are used by the pages in scope.

Keep in mind: Blocked: You cannot determine what the parameter changes or how the intended feature should work.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Compare overlapping guides and service pages by their job

Choose whether two editorial pages should remain separate.

Use this for: Similar articles, repeated service pages and old/new editorial versions.

Read the opening answer, detailed sections and promised action on both pages. Decide whether a visitor needs both. An old and new version of the same guide may belong together; a buying guide and maintenance guide can share vocabulary while answering different questions.

When two pages compete to do the same job, identify useful material that should survive in one complete page. When their jobs differ, identify the specific missing answers or examples that would make that distinction clear. Do not merge pages solely because a keyword appears in both.

Example

Hypothetical example: “Choosing a clay pot” and “Clay pot buying guide” repeat the same advice. “How to clean a clay pot” has a different job and should be assessed separately.

  1. State the task each page helps the visitor finish.
  2. Compare the main answers and useful unique material.
  3. Choose a merge candidate or a concrete distinct-content improvement.
More help and optional notesMedium · Website owner or SEO lead
PassEach reviewed pair has a justified keep-distinct or consolidate decision based on its actual content and purpose.
FailThe decision ignores useful differences or preserves two interchangeable pages without a reason.

If it fails: Merge the useful coverage or give each retained page a distinct, supported purpose.

Retest: Read the resulting pages and confirm that their promised jobs match their content.

Not applicable: No overlapping editorial pages were identified.

Keep in mind: Blocked: The content owner cannot confirm which service or editorial purpose is intended.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check whether product and location templates provide distinct information

Preserve real differences and fix empty repetition.

Use this for: Repeated product, service, location or directory templates.

Compare representative product or location pages beyond their shared layout. Look for facts that matter to the visitor: model specifications, available services, delivery coverage, opening times or useful local instructions. Use only information the business can verify.

A swapped product name or town name does not by itself make the rest of a repeated page useful. Where a separate page has a real job, add its missing relevant details. Where the offer and answer are genuinely the same, consider whether one page would serve the visitor better.

Example

Hypothetical example: Two workshop locations use the same introduction, but have different access instructions, staff availability and class schedules. Keep those useful distinctions instead of rewriting shared wording for its own sake.

  1. Compare one representative pair from each repeated template.
  2. Identify meaningful page-specific facts and any missing answers.
  3. Improve justified separate pages or propose consolidation of interchangeable ones.
More help and optional notesMedium · Website owner or SEO lead
PassRetained pages provide the verified information needed for their distinct visitor task, or interchangeable pages have a justified consolidation decision.
FailPages differ only superficially while omitting the information needed to justify their separate purpose.

If it fails: Add verified differences that help the reader, or consolidate genuinely interchangeable content.

Retest: Compare representative pages after the content changes.

Not applicable: No repeated content templates are used in scope.

Keep in mind: Blocked: The business cannot supply the facts needed to distinguish the pages. There is no universal word-count or percentage-unique threshold for this decision.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Protect translations, regional pages and pagination from blanket fixes

Recognize related pages that may still need separate URLs.

Use this for: Duplicate candidates involving translations, regional variants or paginated lists.

Check why a flagged page exists before grouping it with another. A fully translated main body is different from a page whose menu alone is translated. Regional versions in the same language need deliberate regional and canonical handling.

For pagination, compare the items on page two with page one; different list pages are not duplicates merely because the heading and introduction repeat. Do not apply one sitewide canonical or redirect rule to all these cases. Ask the relevant owner to confirm the intended language, region or list behavior.

Example

Hypothetical example: An English and Spanish care guide share photographs but have translated instructions. A second product-list page shows different stock. Neither should be merged solely because the template matches.

  1. Identify the language, region or pagination purpose of the flagged URL.
  2. Compare its main content and the audience or items it serves.
  3. Exclude legitimate differences from blanket fixes and route special cases for review.
More help and optional notesMedium · Website owner or SEO lead
PassLegitimate differences are preserved and same-content exceptions have an appropriate specialist decision.
FailA blanket rule collapses different languages, audiences or list pages without comparing them.

If it fails: Remove the overbroad rule and review the affected international or pagination pattern separately.

Retest: Open each retained version and verify its intended content after the rule changes.

Not applicable: No language, regional or pagination candidates occur in scope.

Keep in mind: Blocked: The intended audience or pagination behavior is unknown.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Choose and Implement the Right Resolution

Choose the page that should remain useful to visitors, then select the technical treatment. Do not use a canonical tag to hide a missing content decision.

Choose a preferred page and a treatment for each genuine cluster

Build a consolidation plan that matches the reason for the duplicate.

Use this for: Confirmed duplicate clusters after content and exception review.

For equivalent content, choose a stable, complete page that should represent the cluster. Check that it is accessible and appropriate for search before using it as a target. Then decide whether the other address must remain available for a real user or platform need.

If a duplicate is being retired, plan a permanent redirect to its relevant successor. If an equivalent copy must stay, pass the relationship to the canonical tags workflow. If the pages serve different needs, keep them distinct and fix missing content instead. Noindex is for an intentional search exclusion, not a substitute for choosing a representative page.

Example

Hypothetical example: A print view must remain for customers, while a retired duplicate guide does not. Retain the print view with an appropriate canonical relationship; merge and redirect the retired guide.

  1. Choose the complete intended representative for each genuine cluster.
  2. Decide whether every other version is retired, retained or distinct.
  3. Assign the corresponding redirect, canonical, content or intentional-exclusion action.
More help and optional notesHigh · Website owner or SEO lead
PassEach cluster has a relevant accessible representative and a treatment that preserves required user functions.
FailThe plan points to a missing or unrelated target, or uses the same remedy for incompatible cases.

If it fails: Correct the target or treatment before implementation.

Retest: Walk through a representative cluster and verify that its planned outcome serves the original user task.

Not applicable: No genuine duplicate cluster remains after classification.

Keep in mind: Blocked: The owner has not decided whether a version must remain available. This plan can pass before implementation. It does not prove that Google selected the preferred URL.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Keep useful content before retiring an overlapping page

Avoid losing valuable instructions during consolidation.

Use this for: Overlapping content that has an approved merge-and-retire decision.

Before redirecting an overlapping page, move any still-useful unique answers, examples or business details to the intended successor. Check that the successor now fulfills what the old page promised and that no contradictory outdated material was carried over.

Publish the completed successor, then implement the planned permanent redirect for the retired address. Update editable internal links to the final page. Do not retire a useful page merely to reduce the count of duplicate warnings.

Example

Hypothetical example: An older delivery guide has the only explanation of fragile-item packaging. Keep that useful section in the current guide before redirecting the old page.

  1. Compare the pages and identify useful material that must survive.
  2. Publish the complete successor and the planned redirect.
  3. Update internal references and test both addresses.
More help and optional notesHigh · Website owner or SEO lead
PassThe successor contains the useful needed coverage, and the retired address redirects to that relevant page.
FailUseful content is lost, the target is incomplete, or the retired route still serves the unintended copy or an error.

If it fails: Complete the successor and correct the old-to-new mapping and source links.

Retest: Read the successor and follow the original URL and incoming internal links.

Not applicable: No page is being merged and retired.

Keep in mind: Blocked: Content approval, editing access or redirect implementation is unavailable.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Check retained copies against the intended representative

Keep a necessary alternate page without making its relationship ambiguous.

Use this for: Equivalent copies that intentionally remain available at separate addresses.

For a copy that must remain, confirm that its principal content is equivalent to the chosen representative. Inspect the page source or ask the developer for its canonical declaration and compare the declared target with the plan. Use the canonical tags checklist for the full implementation test.

Check a normal visitor can still use the retained function, such as printing or viewing a permitted variant. A correct canonical declaration is a preference signal; it does not guarantee that Google will choose the target or make the duplicate disappear immediately.

Example

Hypothetical example: A printer-friendly guide remains available, but its canonical accidentally points to the homepage. Correct the relationship to the complete guide while preserving the print function.

  1. Open the retained copy and its planned representative.
  2. Compare their main content and current canonical relationship.
  3. Repair the relationship through the specialist workflow and test the retained feature.
More help and optional notesMedium · Website owner or SEO lead
PassThe retained copy matches its intended representative, its canonical relationship matches the plan and its required function works.
FailThe declaration targets a wrong page, the pages are not equivalent or the retained function breaks.

If it fails: Correct the relationship or reclassify the pages; use the canonical implementation checks before release.

Retest: Recheck the declared target and required visitor function on the published copy.

Not applicable: No equivalent alternate copies need to remain available.

Keep in mind: Blocked: The canonical output or the required alternate function cannot be inspected.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Make retained pages answer their different questions

Improve substance rather than changing words to defeat a similarity report.

Use this for: Pages retained for distinct purposes but lacking sufficient useful differentiation.

For a keep-distinct decision, write the missing answer, specification, comparison or example that belongs on each page. Make the title and opening reflect that job, then remove redundant material that crowds it out. Keep accurate shared facts when readers need them.

Review the revised pages side by side. A synonym rewrite is not the goal; each page should now help someone do something the other does not. If no useful distinction can be supplied, revisit the consolidation decision.

Example

Hypothetical example: A pot-size guide gains a dimension comparison and fit examples; a pot-care guide gains cleaning steps and material cautions. Their content now supports their separate purposes.

  1. Identify the missing page-specific answer from the classification step.
  2. Add verified detail and align the title and introduction.
  3. Compare the revised pages against their separate visitor tasks.
More help and optional notesMedium · Website owner or SEO lead
PassEach revised page fulfills its separate task with accurate relevant information.
FailThe pages remain interchangeable or differ only through superficial wording changes.

If it fails: Add the needed substantive answer, or consolidate if the separate purpose is not justified.

Retest: Have someone follow the task on each published page and compare the result.

Not applicable: No retained page needs substantive differentiation.

Keep in mind: Blocked: The verified facts, examples or content approval needed for the distinct answer are unavailable.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Stop Recurrence and Check the Result

A page-by-page fix can leave the generator creating new copies. Check the source of the pattern and distinguish a correct live implementation from a later search-engine decision.

Stop templates and navigation from creating new copies

Repair the pattern that produced the duplicate cluster.

Use this for: Duplicate patterns created repeatedly by navigation, templates or CMS output.

Trace a representative duplicate back to its CMS template, filter, menu or URL generator. Check new output from that source after the repair. For equivalent content, use the intended preferred addresses in ordinary internal links and sitemap entries.

Do not remove a necessary feature or block all parameter URLs without reviewing their function. If the pattern creates a large or effectively unbounded URL space, hand that finding to the crawl-budget workflow rather than generating every possible combination during this audit.

Example

Hypothetical example: Editors stopped linking to a duplicate product route, but a recommendation widget still creates it on every new product page. Fix the widget’s URL field.

  1. Locate the template or component that creates the duplicate addresses.
  2. Correct its address generation and preferred internal references.
  3. Test fresh output and representative existing pages.
More help and optional notesHigh · Website owner or SEO lead
PassThe reviewed generator no longer creates unintended copies or links to redundant versions.
FailNewly generated content or navigation recreates the same unintended pattern.

If it fails: Correct the generating rule and regenerate or republish affected content where necessary.

Retest: Create or inspect fresh output from the repaired component and recrawl its links.

Not applicable: The duplicate is a one-off editorial copy with no recurring generator.

Keep in mind: Blocked: The component owner or generation settings cannot be accessed.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Verify repaired clusters and review later search records separately

Confirm the actual repair without mistaking old indexing data for the current site.

Use this for: Duplicate-content or consolidation fixes that have been published.

After publication, revisit the same cluster members and rerun the relevant content comparison. Check the expected outcome: relevant redirect, retained equivalent copy with the intended relationship, or clearly distinct content. Include the generator sample so the issue is not recreated.

Where Search Console access is available, inspect the indexed record for representative affected URLs and compare its last crawl with the change date. Read the Google-selected canonical separately from your declared preference. An old or missing indexed record leaves that search outcome unconfirmed even when the live repair passes.

Example

Hypothetical example: The live old guide now redirects correctly, but Search Console still describes a crawl from before the change. The implementation is fixed; recognition of that change remains pending.

  1. Recheck the live behavior and content of each representative repaired cluster.
  2. Repeat the relevant crawl or comparison with the same scope.
  3. Review later indexed records separately when available and investigate a current mismatch.
More help and optional notesHigh · Website owner or SEO lead
PassThe live cluster matches the chosen treatment and fresh verification no longer shows the repaired defect.
FailThe live content, redirect, canonical relationship or generator still contradicts the plan.

If it fails: Correct the remaining implementation defect; investigate a later canonical mismatch through the specialist workflow.

Retest: Repeat the same cluster checks after correction and compare newer indexed records separately.

Not applicable: No duplicate-content repair has been published for verification.

Keep in mind: Blocked: The changed pages or a fresh verification run cannot be accessed. Missing Search Console access does not invalidate a live implementation check. It does prevent a claim about Google’s selected canonical or current indexing.

Optional: the page or URL pair you checked, what happened and the next action. Keep confidential data out of shared exports.

No result recorded yet.

Changing this result updates your checkmark and progress immediately. Notes are optional.

Reset this checklist?

This removes saved statuses, evidence and result dates for the checks on this page. Other checklists keep their records. Export a CSV first if you need a copy.

A useful result, every time

Check a task. Choose a result.

This is a manual SEO workflow. It helps you decide what to investigate and keep a usable record. It does not crawl your website or verify your answers automatically.

  1. Choose your scope. Pick the relevant task group and representative pages you are authorized to inspect.
  2. Run the stated check. Follow the steps, then choose your result. Click the square for Pass, or use the result menu for another status. You do not need to type anything.
  3. Assign the next action. Fix a problem when you can, or ask the right person for help. Optional notes can remind you what to do next. Check the result again after a fix.

What your progress means

Review progress counts passes and failures against applicable checks. Failed work still counts as reviewed. Blocked and untested checks remain unfinished. This is not an SEO score.

Untested
You have not checked this yet.
Pass
You checked it and it works as described.
Fail
You checked it and found something to fix.
Blocked
You need access, information or someone’s help.
Not applicable
This task does not apply to your website.

Export CSV downloads the checks currently shown and any optional notes. Print expands the instructions for that view. Saved results stay in this browser; there is no account sync.

Apply the workflow

What Should You Do With the Duplicate Clusters?

Use each cluster’s purpose and cause to choose a treatment, then verify the published behavior separately from Google’s later canonical selection.

Should You Redirect, Canonicalize or Keep Distinct Content?

Choose the treatment from the relationship between the pages and whether both need to remain available. Canonicalization concerns equivalent content; it is not a remedy for every weak or overlapping page. These examples are hypothetical.

A content-based duplicate treatment decision.
RelationshipUseful actionCheck before proceeding
Equivalent old page no longer neededMerge useful material and permanently redirect.The successor fulfills the old page’s purpose.
Equivalent copy needed for a user functionRetain it with an appropriate canonical relationship.The target is relevant and the alternate function still works.
Different questions with repeated generic textKeep distinct pages and improve their main answers.There is a real separate visitor task and verified supporting detail.
Tracking value leaves the content unchangedUse the preferred version consistently and review canonical handling.The parameter is not needed to select different content.
Page two shows different list itemsKeep its separate pagination URL.Do not assume repeated headings make it a copy of page one.
Page intentionally excluded from searchUse the appropriate exclusion workflow.Exclusion is the desired outcome, not an attempt to choose a canonical.

What Should Your Consolidation Plan Contain?

A consolidation plan needs a cluster, the reason the copies exist, the page to retain and the exact treatment. Keep it in your existing project tool if that is easier. The example rows below are hypothetical; the checklist’s CSV export saves your checks and optional notes, not a discovered URL inventory.

Hypothetical duplicate clusters and decisions.
ClusterCauseDecisionVerification
Two delivery guide pathsOld and current editorial versionsKeep useful old details, then retire the old page with a relevant redirect.Read successor and test old address.
Guide and its print viewRequired alternate presentationKeep the print function and review canonical relationship.Compare content, declared target and print behavior.
Buying guide and care guideShared introductory boilerplateKeep distinct purposes and improve the specific answers.Review each against its visitor task.

Does Duplicate Content Automatically Cause a Penalty?

Ordinary duplicate content does not automatically violate Google’s spam policies. The practical problems here are unclear representative URLs, unnecessary copies and pages that do not provide the intended distinct answer. Manipulative or abusive publishing is a separate issue.

There is no universal acceptable duplicate percentage in this checklist. A crawler’s similarity setting helps find candidates; the main-content comparison and the reason each page exists determine the next action. A site-limited crawl cannot establish whether another website copied your content.

Which Checklist Should You Use for the Chosen Fix?

Finish the classification here, then follow the workflow that implements your decision. This keeps a content choice from becoming a blanket technical rule.

A clear process, with honest limits.

Follow the steps, choose the result that matches what you found, and check again after changes. Notes are optional. A completed check does not guarantee indexing, traffic or rankings. How the checklists work.