Content Updates and Pruning: What Stays, What Goes
Not every old blog post deserves a refresh. A practical way to decide which content gets updated, merged, or removed and why.
rabbitclip teamPublished: 5 min read
Short answer
Content pruning means updating, merging or removing pages that no longer earn their place in search, either because they are outdated or because they get no traffic at all. The goal is not a smaller site for its own sake, it is making sure every remaining page actually does its job; Google's own guidance states that content should be created primarily to help people, not produced as filler aimed at a search engine.
A blog that has published weekly for three or four years tends to accumulate two very different kinds of post: ones that still bring in search traffic but need a refresh, and ones that never got traffic and likely never will. Treating both the same way is a mistake.
Which posts are candidates for an update?
A post is a candidate for updating when its topic is still searched but the content itself has aged. Posts showing impressions in Search Console's Performance report but low clicks, or a slipping average position, fall into this group; interest in the topic is still there, the page just no longer meets it.
Dated phrases ('back in 2023', 'recently changed') are a particular risk, since both readers and search engines read those as a sign of age. If a title still holds true but the examples, figures or rules inside it have changed, updating takes priority.
Which posts are candidates for removal or merging?
A post is a candidate for removal or merging when it has had no impressions for months, its topic is no longer searched, or another page on the site already covers nearly the same ground. That second case leads to two weak pages splitting the same traffic instead of one strong one earning it.
Removal does not have to mean deletion. Content can move into another post with a 301 redirect from the old address to the new one, keeping whatever small signal the page had built up.
What does Search Console's Remove Outdated Content tool actually do?
It is normal for Google's search results to keep showing an old version of a page after it has been removed or changed; Search Console Help describes this tool as the way to update a stale search result for a page that no longer exists on the site or has changed.
This tool is a complement, not a strategy. The real work is deciding which pages stay and setting up redirects correctly; the tool only speeds up how quickly that decision shows in search results.
How does pruning affect the rest of the site?
Cutting a site's total page count looks risky at first, but removing weak pages usually raises the average quality of what remains. Google notes that the overall proportion of unhelpful content on a site can affect how the whole site is assessed, separately from any individual page's own quality.
On a flooring manufacturer's blog, cutting twelve similar old posts down to three and updating what remained was followed by an improvement in the remaining posts' average ranking; that is one case, not a percentage to generalise from, but it is telling as a direction.
How to plan a pruning round
A round that can run once or twice a year can follow this sequence.
- Sort Search Console's Performance report by page for the last 12 months; list pages with zero impressions separately.
- Group that list by topic similarity; flag any that cover nearly the same ground as merge candidates.
- Keep posts with impressions but low clicks on a separate list; they are update candidates, not removal candidates.
- Decide the redirect target for every page being removed before removing it.
- Submit the updated sitemap to Search Console after the change and rerun the same report three months later.
The common mistake: trying to update everything
Updating every old post one by one is usually wasted effort; a topic nobody searches for will not bring traffic no matter how well it is rewritten. Priority should always go to content that still gets interest but has aged.
On a spa chain's site, a post about a service that had since been discontinued was refreshed and republished three times without traffic ever picking up; the problem was never the quality of the writing, the topic simply was not searched anymore. Removal, not another update, was the right call there.
Content pruning is not about shrinking a site, it is about making sure every page left actually earns its place. The decision should follow data, whether the topic is still searched, rather than instinct; content deleted or updated on a hunch usually wastes time on the wrong target. A short discovery call with rabbitclip is enough to see which posts on a given blog belong in which pile.
FAQ
What happens to a removed page's traffic?
If the content moves to another page with a 301 redirect, most of the signal it built up is preserved; deleting without a redirect loses that traffic entirely.
How many months of zero impressions justifies pruning?
There is no fixed threshold; posts with zero impressions for over a year, on a topic no longer searched, are the first group worth reviewing.
Is updating or rewriting more effective?
If the topic still holds, an update is enough; if the topic or approach has changed entirely, a rewrite wastes less time overall.
Does the Remove Outdated Content tool replace a removal strategy?
No. It only updates a stale search result; deciding which pages stay is a separate task done beforehand.
