Merge overlapping service pages without losing useful answers

Confirm the pages represent one task

Read both pages as a customer and state their promised service. Similar labels can describe different appointments, equipment, or eligibility. If the tasks differ, clarify the distinction rather than merging automatically. If they genuinely represent the same service, document that decision with the person responsible for delivery.

Source checks: Google Search Central: People-first content · Google Search Central: Redirects and Search · Google Search Central: Canonical URL methods

Inventory information before choosing the winner

List scope, exclusions, preparation, estimate factors, evidence, FAQs, and inquiry instructions from each page. Mark repeated facts separately from unique useful answers. A stronger-looking design may still omit an important limitation found only on the older page. Do not delete content based only on word count or a traffic comparison.

Choose the surviving destination deliberately

Review relevance, current use in promotions, URL stability, and the planned information structure. The surviving page should be the actual replacement for visitors using the retired URL. Verify that it is public, has the intended canonical, and supports the relevant inquiry. Record the decision before implementing a redirect.

Transfer facts and test the visitor task

Use the inventory as an acceptance checklist.

• Move approved unique scope and exclusions into the surviving page.
• Combine repeated explanations without contradicting the real service process.
• Keep evidence context and permissions intact.
• Update internal and important owned external links to the final destination.
• Map the retired URL to the genuine replacement with the correct permanent intent.
• Test mobile reading, estimate requirements, and inquiry delivery.

Avoid content merging by automatic concatenation

Pasting both pages together can retain conflicting prices, dates, or promises. Review each fact with its owner and remove outdated statements. Likewise, a redirect does not preserve information that never reached the final page. Keep genuinely different service tasks separate instead of forcing all work into one broad page to reduce the URL count.

Verify the information transfer after release

Reopen the retired URL and the final page. Check that the mapped destination contains every approved unique answer identified in the inventory. Monitor later canonical and search observations without treating a consolidation as an automatic ranking improvement. Record which old references remain to update.

Keep the transfer sheet in the website content history. A future editor may recreate the retired page from an old draft unless its retirement and replacement are explicit. Add the final URL, effective date, and service owner so the next redesign starts with the current decision rather than a folder of indistinguishable versions.

Illustrative two labels for the same appointment

An illustrative site has /washer-repair and /washing-machine-repair for the same service. The second uniquely explains model-label preparation and exclusions. The owner transfers those approved answers to the chosen /washer-repair page, updates current links, and redirects the retired path. The useful facts survive instead of disappearing with the duplicate URL.

The transfer sheet lists the model-label instruction and equipment exclusions as separate retained answers. The owner opens the final page from the retired URL and checks both statements before accepting the merge. This avoids losing useful content that previously lived below the fold on the less-promoted page.

Questions about this task