This is a walkthrough of a content pruning project at a mid-sized B2B SaaS company, illustrating the decision criteria and the shape of the results — the kind of project that's easy to describe in principle and genuinely uncomfortable to execute in practice, since it means deliberately removing content someone spent time creating.

The starting problem

The site had roughly 1,100 published pages accumulated over about five years of steady blogging, much of it published without a consistent content strategy — overlapping topics covered multiple times by different writers, thin pages written to hit a keyword that never developed real depth, and outdated pages about product features or industry conditions that had since changed. Organic traffic had been flat for over a year despite continued publishing, and the team suspected — correctly, as it turned out — that a meaningful share of the site was actively working against its best content rather than neutrally sitting unused.

Scoring criteria

Every page was scored on three factors, not on age or word count alone:

  • Organic traffic over the trailing 12 months. Consistently low or zero traffic was a strong pruning signal, but not on its own — a genuinely new or niche page can have low traffic without being a pruning candidate.
  • Backlinks. A page with meaningful external links, even with modest current traffic, was preserved or consolidated rather than removed outright — deleting a page that's earned real external link equity forfeits that equity entirely unless it's redirected.
  • Topical overlap with other existing pages. This was the most decisive factor. Pages covering substantially the same search intent as another, stronger page on the site were the clearest pruning candidates, regardless of their individual traffic — these were splitting ranking signals that would perform better concentrated into one page.

Age and word count, the two criteria most commonly proposed for pruning decisions, turned out to be weak signals on their own — several of the site's best-performing pages were both old and relatively short, and pruning by those criteria alone would have flagged genuinely valuable content.

What got pruned vs. consolidated vs. left alone

Of roughly 1,100 pages: 340 were flagged for action. Of those, about 210 were consolidated into a stronger existing page via a 301 redirect, and about 130 were deleted outright with no reasonable page to redirect to (mostly pages about discontinued product features or fully superseded industry conditions with no current equivalent).

Consolidation, not deletion, handled the large majority of the pruning — most of the problem was overlapping content splitting signals across multiple pages, which redirecting and merging fixes directly, rather than content with genuinely no reason to exist anymore.

The results, and the shape of the timeline

Organic traffic roughly doubled over the six months following the pruning project, but the path wasn't a smooth upward line. The first two months showed a modest dip — the pruned pages, even the low performers, had been contributing some residual traffic that disappeared immediately upon removal or redirect. Growth from the consolidated pages ranking better than their previous split-signal versions took a few weeks to materialize as search engines re-crawled and re-evaluated the redirected URLs, and continued accelerating over the following months as the site's overall topical clarity improved.

An unplanned secondary benefit: crawl efficiency improved measurably. With roughly 30% fewer pages, and specifically fewer thin, overlapping pages diluting the site's topical signal, the pages that remained were both easier to crawl thoroughly and clearer, category by category, about what the site was actually authoritative on.

What we'd do differently

The scoring process was manual and took longer than anticipated — building an actual repeatable scoring script against traffic and backlink exports would have saved meaningful time and made the criteria easier to re-apply on a future pruning pass, which the team now plans to run annually rather than treating this as a one-time cleanup.