Content pruning and consolidation

What content pruning means

Content pruning is reviewing the pages on your site and deciding, for each one, whether to keep it, improve it, merge it with something else or remove it. It's housekeeping. Over years, most sites collect pages that no longer help: old news, outdated guides, thin tag pages, near-duplicate posts and pages for services you've stopped offering.

Why it helps

• Visitors find better pages. Less clutter, fewer outdated answers.
• Fewer pages compete with each other. Several weak pages on the same topic can be combined into one strong one.
• Search engines see a clearer site. Google's guidance on helpful content talks about the overall impression of a site. Lots of unhelpful pages don't help that impression.
• Easier maintenance. Fewer pages to keep accurate.

When not to prune

Pruning isn't a magic trick. Deleting pages won't fix a site whose core pages are weak. And removing pages that bring visitors or links can hurt. Never prune just to reduce page count.

Step 1: Gather your pages and data

Build a spreadsheet of every page, with:

• URL and title.
• Clicks and impressions over the last 12 months, from Search Console's Performance report.
• Sessions and key events, from analytics.
• Links from other sites, from Search Console's Links report.
• Date last updated.
• Topic, so you can spot overlaps.

Step 2: Decide what to do with each page

Ask a few questions:

Is it useful and accurate?

Keep it. Maybe give it a light refresh.

Is it useful but out of date?

Update it. Refresh facts, prices, rules and examples. Often the best option for guides that used to perform well.

Does it overlap with other pages?

Merge. Combine the best parts into one page, then redirect the others to it. Google's guidance on redirects explains permanent redirects.

Is it thin, outdated and getting no visits or links?

Remove or noindex. If it has no value to visitors, remove it. Let it return a 404 or 410, or redirect it to a closely related page if one exists.

Does it need to exist for visitors but not search?

Keep but noindex. For example, thank-you pages, certain internal tools or archived documents.

Step 3: Make the changes carefully

• Work in batches, not all at once, so you can see the effect.
• Update internal links that pointed to removed or merged pages.
• Redirect merged pages to the most relevant page, not the home page.
• Update your XML sitemap.
• Keep a record of what you changed and when.

Step 4: Watch the results

Check Search Console over the following months:

• Did merged pages hold or improve their combined traffic?
• Did any important page lose visibility after a change?
• Are there new 404 errors from removed pages that had links?

How to merge pages well

Merging is more than pasting two pages together. Start with the page that has the most visits and links, and use its URL as the destination. Read every page you're merging and pick out anything genuinely useful: a good example, a clear explanation, a question the other pages missed. Rewrite the combined page so it reads as one piece, with a sensible heading structure. Then redirect the other URLs to it and update any internal links. If one of the old pages answered a specific question well, keep that answer as its own section so visitors arriving through the redirect find what they expected.

Common pruning candidates

• Old news posts, such as "We're closed for Christmas 2019".
• Event pages for past events with no lasting value.
• Tag and category archives with one or two posts each.
• Near-duplicate blog posts written years apart on the same topic.
• Pages for discontinued services or products, unless they still help visitors.
• Auto-generated pages, such as empty author archives or attachment pages.

A worked example

A wedding venue's blog had 180 posts over ten years. Many were short "real wedding" posts with a few photos and a sentence, plus several posts on "choosing your wedding date" written in different years.

The venue reviewed every post. It merged the date-choosing posts into one thorough, updated guide covering seasons, popular dates and local considerations, and redirected the old posts to it. It combined the short real-wedding posts into seasonal galleries with fuller write-ups, with couples' permission. It removed posts announcing past open days, which had no visits or links.

The blog went from 180 posts to around 60. Visitors could find genuinely useful planning guides, and the venue's team had far less to keep up to date.

Questions