Content Strategy · Guide

Decide When to Merge, Rewrite or Remove Old Content

Merge similar posts when they address the same task and one stronger guide would serve readers better. Retain distinct pages when they offer meaningfully different help. This guide takes that specific topic through four practical steps, beginning with the following action: List overlapping URLs, their unique sections, search queries and any links pointing to them. You will also see a realistic example, a verification test and a common mistake to avoid. Use the process on your own site, and check current vendor documentation whenever a platform setting has changed.

What to prepare before starting

The article’s reader, the decision or task it should help with, and someone who can verify claims. Your own business records and practical examples are more useful than a fixed target word count.

Keep this boundary in mind while carrying out the steps: A publication date is a record of a real event, not a method for forcing a page higher in search results.

Step 1: Start with a reliable inventory

List overlapping URLs, their unique sections, search queries and any links pointing to them.

Write down the starting state before changing anything. If an issue is not reproducible on the live site, distinguish a suspected concern from a confirmed problem. This gives you a defensible reason for prioritizing the work. Where the recommendation affects user-facing claims, confirm them with the business owner or the relevant official source. A clear but inaccurate change can make a page less trustworthy.

Step 2: Examine the important details

Choose merge when two pages serve one task, rewrite when a valuable page misses intent, remove when a page has no continuing purpose.

Keep the page's actual audience and publishing platform in view. A check that succeeds in an editor preview may fail at a public URL, and a setting that works in a custom site may not exist in a hosted website builder. Keep proof of the published outcome, especially if multiple people edit the same website. The task is complete when you have verified the intended behavior, not merely clicked Save.

Step 3: Make the targeted improvement

Move genuinely unique content to the retained page; use a 301 redirect only where the replacement is relevant.

Focus on the smallest effective change first. Maintain a short record of the before state, the revision and the pages affected; this makes it possible to reverse a mistake instead of guessing what changed. For this particular task, the evidence to collect is related to decide when to merge, rewrite or remove old content. Note any conditions that would prevent another site owner from following the same action exactly.

Step 4: Verify the live outcome

Update navigation, internal links and sitemap entries, then monitor crawl errors after the change.

Use the public, signed-out version of the page for the final test. Search Console and analytics can provide later signals, but your immediate acceptance check is whether the intended page, content and links behave correctly. If the page or tool returns an unexpected result, first recheck the URL, permissions and configuration rather than inventing an SEO explanation. Fix a verified issue, then run the same check again.

Worked example: apply the process to a real website

Three guides about the same “first SEO audit” checklist become one maintained article; a distinct analytics troubleshooting post stays separate.

Treat this as a planning example, not a claim about a SiteGrowth customer or a tested client outcome. Write down the starting problem, the affected URL and which of the four steps you applied. Then compare the published result with the original question. If the example does not apply to your site, adapt the sequence to its content and platform instead of copying details that are not true.

How to check whether you finished successfully

Old links lead to relevant content and duplicate coverage is reduced without hiding useful material.

Do the check in a signed-out browser session where possible. Follow links manually; inspect the actual mobile page and any relevant source-code or search-console evidence. If a metric matters, save the date range and definition. A page being published, discovered or indexed does not automatically establish that it gained traffic or customers.

Common failure: what to avoid and how to recover

Mass redirecting unrelated retired pages to the home page or deleting content without checking value.

If you see this failure, stop expanding the change across more pages. Identify the affected URL or editor setting, restore the last known-good version when appropriate, and test one corrected example. Only then repeat the change at scale. This is especially important for URL migrations, canonical tags, robots directives and automated bulk content updates.

Final practical checklist

Before marking the task complete, confirm all five points:

1. You identified the real visitor task and the exact page or record involved.
2. You completed the initial check: List overlapping URLs, their unique sections, search queries and any links pointing to them.
3. You completed the final step: Update navigation, internal links and sitemap entries, then monitor crawl errors after the change.
4. You checked the outcome: Old links lead to relevant content and duplicate coverage is reduced without hiding useful material.
5. You recorded outstanding caveats and, when warranted, linked from a relevant existing page.

If this guidance depends on a platform feature, consult its current documentation before implementing a large change.

Key takeaways

List overlapping URLs, their unique sections, search queries and any links pointing to them.
Choose merge when two pages serve one task, rewrite when a valuable page misses intent, remove when a page has no continuing purpose.
Move genuinely unique content to the retained page; use a 301 redirect only where the replacement is relevant.
Update navigation, internal links and sitemap entries, then monitor crawl errors after the change.
Old links lead to relevant content and duplicate coverage is reduced without hiding useful material.

Common questions

Should I merge similar blog posts?

Start with the actual website and the reader's need. List overlapping URLs, their unique sections, search queries and any links pointing to them. Then choose merge when two pages serve one task, rewrite when a valuable page misses intent, remove when a page has no continuing purpose. The final check is: Old links lead to relevant content and duplicate coverage is reduced without hiding useful material.

What is a common mistake to avoid?