Content Pruning for SaaS Blogs: What to Cut, Merge or Keep

Content pruning means reviewing your existing articles and deciding what to cut, merge, refresh or leave alone. For a SaaS blog, the main reason to do it is usually focus: to stop weak or overlapping posts from competing with stronger ones, and to keep outdated claims about your product and market away from readers. It isn't a quick way to raise rankings, and deleting pages simply because they get little traffic can do more harm than good.

Most pruning advice is written for media sites with tens of thousands of pages. A SaaS blog with 300 posts has a different profile. Pages might bring in few visitors but sell well, and an article that looks dead in analytics might be one your sales team sends every week.

Why Google's position matters here

Google has been clear that deleting content isn't a trick for better rankings. If a page has no value, removing it may be sensible, but you shouldn't expect a ranking gain from removing it purely because it's old. Older content isn't automatically worse, and a dated post that still answers a question well should stay.

Google does have systems looking at whether content's helpful, and it describes people-first content as what it wants to reward. So there's a reasonable case for clearing away pages that exist purely to catch a keyword. But the reason should always be better pages for readers, and not a guess about what the algorithm wants.

Pull the data first

Say you run a 35-person SaaS for managing employee benefits, and your blog has 280 posts, most of them written by a string of freelancers. Build one sheet with a row per URL and these columns:

• Clicks and impressions over the past 12 months, from Search Console
• Change against the previous period, to reveal posts in decline
• Top query for each URL
• Referring domains, from a backlink tool
• Conversions, including assisted ones if you can get them, from your analytics
• Internal links pointing to it, from a site crawl
• Sales or support use: Ask those teams which posts they send out.
• Last updated date

Use a long window. A short one will misjudge seasonal topics, and B2B searches can be slow.

The decision: five outcomes

Go through each row and choose one result.

Outcome	When to choose it	What you do
Keep	Brings relevant traffic or conversions, and is accurate	Nothing, except adding internal links to money pages
Refresh	Has demand, but is out of date or slipping	Update the content properly
Merge	Several posts answer the same question	Combine into the strongest URL, and 301 the others
Redirect	Weak page, with a clearly better page on the same topic	301 to that page
Remove	No traffic, no links, no purpose, and no replacement	Return a 404 or 410, or noindex if the page must stay available

Here are some rough rules for using it. Anything with conversions, meaningful links or sales usage should stay unless there's a strong reason. A post with impressions but few clicks isn't a removal candidate, as it has demand: it's a refresh candidate. Our content refresh strategy has the method for those.

Removal should be your last choice, and it's rarer than you may think. Going back to the benefits SaaS, the 280 posts might end up as 120 kept, 60 refreshed, 50 merged into about 15, 30 redirected and just 20 removed. Those numbers are made up for illustration, but the shape is typical: you'll merge much more than you delete.

How to spot merge candidates

Overlap is the most common problem on SaaS blogs with a long history, as different writers cover the same ground in different years. Look for:

• Several URLs appearing for the same top query in Search Console
• Titles that say roughly the same thing, such as "Benefits Enrollment Tips" and "How to Run Open Enrollment"
• Posts targeting a phrase and its plural, or its slight rewording

Then search each pair yourself. If the same pages rank for both phrases, they probably belong together. Our guide to keyword cannibalization covers this in detail.

To merge well, choose the URL with the strongest links and traffic, even if it's not the best-written. Bring across the useful parts of the others, and don't just paste them in. Update the article's date only if the content has really changed. Then 301 redirect the old URLs and update any internal links pointing at them.

Reasons to remove a page that have nothing to do with SEO

Some pages should go even if their numbers look acceptable, and SaaS companies accumulate these:

• Posts about retired features, or a pricing model you no longer offer
• Announcements about partnerships that ended
• Claims or statistics you can no longer support
• Advice you no longer agree with
• Content about a market you left
• Thin AI-generated posts published without review

These can do real damage, because buyers, sales prospects and AI systems can all read them. An old post stating an outdated limit on your product may well be what an AI tool quotes back to a prospect. See how to fix AI search brand misinformation.

What not to prune

Be careful with these, as they often look weak on a traffic report.

Low-traffic commercial pages. A comparison page with a small audience that converts well is worth far more than a popular definition post.

Pages with valuable links. If a page has good external links, redirect rather than delete. Otherwise you'll lose them.

Docs, changelogs and glossaries. Different reader, different job. A support article's value won't be visible in a marketing report. Our guide to SEO for docs and help centers discusses how to treat them.

New posts. Give an article several months at least. B2B search takes time.

Pages supporting a cluster. A post that gets few visitors but links usefully to a main page might still be doing something. Don't remove a page just because it isn't an entry point.

How to remove a page safely

For anything you're taking down, follow the same steps:

1. Check for links and conversions one last time.
2. Find all internal links pointing to the page, and update or remove them.
3. Apply the redirect or set the correct status code.
4. Remove the URL from your sitemap.
5. Log what you did, with the date and the reason.

Do this in batches, and don't do the whole lot in one release. If something goes wrong, you'll want to know which batch caused it. Keep a copy of the content too, since you may want to reuse it or restore it. Don't use robots.txt to remove pages: it stops Google from seeing a noindex tag, and it doesn't remove anything.

How to tell if it worked

Compare the affected groups of pages over the following months, not the whole blog. Did the merged URLs gain impressions and clicks over what the separate pages got? Did the refreshed posts recover? Check that overall organic conversions haven't fallen.

Be careful with the conclusions you draw. Traffic to the removed pages going away is expected, and an improvement elsewhere could have other causes, so a simple record of the dates will help you to sort this out.

Make it routine

A big pruning project every few years is painful. A quarterly review of a smaller batch is much easier. Add a simple rule for new content, too: before writing anything, check your keyword map for existing coverage. Most blog bloat comes from writing new posts when you should have updated old ones.

If you've inherited a blog that nobody can quite explain, see how we approach content for B2B SaaS.