Content Prune Rate Calculator

What Content Prune Rate Measures and Why It Matters

Content prune rate tells you what share of your audited content library is a candidate for consolidation, redirection, or removal. The formula is simple: prune candidates divided by total audited assets. What the number reveals is the overall health and efficiency of a content catalog — a library where a large portion of assets are stale, duplicative, or underperforming is harder to navigate, dilutes internal linking value, and splits crawl budget across pages that are not earning their place.

The metric matters because content teams often produce faster than they review. Over time, a library accumulates assets that were useful at launch but have since been superseded by better pieces, assets that were created for campaigns that ended, and topic clusters where three articles cover nearly the same ground with none dominating. Prune rate is a diagnostic tool that surfaces how much of this accumulation has happened before teams decide how to allocate refresh capacity.

Importantly, prune rate is not a measure of failure — a mature content program with a large back-catalog will naturally have some percentage of assets that need thinning. What makes the number useful is tracking it over time and across categories. A prune rate that is climbing quarter over quarter suggests production is outpacing quality control. A prune rate that stays flat after an audit and pruning cycle suggests the maintenance process is working.

How to Use This Calculator

Enter the number of assets flagged as prune candidates from your audit and the total number of assets included in that audit. The result is the percentage of your audited library identified for action. The calculator works at whatever scope you define — a full site audit, a single topic cluster, a social media back-catalog, or a specific content type like lead magnets or video scripts.

The most useful approach is to first agree on what qualifies as a prune candidate before running the audit, so the output is consistent and comparable across audits. Common candidate criteria include: traffic below a meaningful threshold for more than ninety days, significant keyword overlap with a stronger page, no meaningful backlinks or internal link equity, outdated information that would require a substantial rewrite to salvage, and content created for a product, campaign, or audience segment that no longer exists.

Once you have a prune rate, segment the candidates by the recommended action — consolidate (merge with a related stronger piece), redirect (301 to a more authoritative URL), update (needs a lighter refresh rather than full removal), or delete (no value to preserve). The prune rate gives you the scale of the problem; the action breakdown tells you the workload.

• Define prune criteria before auditing — consistency makes the rate comparable over time
• Audit at a category or cluster level as well as site-wide to find problem areas
• Separate prune candidates by action type: consolidate, redirect, refresh, or delete
• Re-audit the same cluster after acting to measure whether prune rate improved

What Drives a High Prune Rate and How to Reduce It

The most common driver of a high prune rate is a mismatch between content production pace and editorial governance. When teams publish frequently without a systematic review process, topic overlap accumulates naturally. Two writers cover adjacent angles on the same subject, legacy campaign pages persist after the campaign ends, and exploratory content from earlier audience targeting assumptions lingers even after the strategy has shifted. None of this is negligence — it is the natural byproduct of productive content programs that lack a maintenance rhythm.

Reducing prune rate over time requires building the review cycle into production, not treating it as a separate annual initiative. Practical approaches include quarterly cluster audits that flag underperformers before they multiply, a decay threshold that automatically queues content for review when traffic drops by a set percentage from its baseline, and a topic ownership model where a designated person or team is responsible for maintaining a cluster rather than just publishing into it.

Content brief standards also affect future prune rate. Briefs that require a differentiation statement — explaining how the new piece is distinct from everything already published on the topic — reduce duplicative output at the source, rather than requiring cleanup later.

Common Mistakes When Auditing for Prune Rate

The most significant mistake is using traffic alone as the prune threshold. Some high-value pages generate very little organic traffic because they serve a narrow, late-funnel purpose — proposal templates, onboarding guides, or comparison pages linked from sales materials. Pruning by traffic alone removes strategically valuable content while leaving genuinely thin content that happens to get some passing visits.

Another common error is auditing and flagging without acting. A prune rate calculation that produces a list of candidates but no assigned actions or timeline for resolution does not improve the library — it just documents the problem. Tie every audit output to a concrete action queue with owners and deadlines. Prune rate is only useful as a metric if it drives decisions, not just reports.