Content & Writing
Content & Writing
Live

Content Pruning Analyzer

Identify low-value pages for removal, redirect, or rewrite.

Page metrics CSV

Header: url,clicks,impressions,position,age,words (age in years)

2
keep
2
improve
1
merge
0
redirect
0
noindex
2
delete

Per-page recommendations

keep
/blog/best-hiking-boots8,400 clk · pos 4 · 2400w · 3y
improve
/blog/old-camping-tips42 clk · pos 33 · 800w · 8y
delete
/blog/short-thoughts2 clk · pos 52 · 180w · 5y
keep
/blog/sock-guide580 clk · pos 12 · 1200w · 4y
improve
/blog/duplicate-trail38 clk · pos 28 · 950w · 6y
delete
/blog/legacy-sale-20180 clk · pos 90 · 200w · 7y
merge
/products/discontinued-boot15 clk · pos 40 · 300w · 9y

Start here · What is content pruning?

Pruning decides which URLs earn ongoing investment and which should merge, redirect, or retire so crawl equity focuses on winners.

Paste a CSV with page-level metrics: URL path, clicks, impressions, average position, age in years, and word count.

Rules emit recommendation badges such as delete for zero-traffic aged posts or improve for high impressions with weak positions. Treat them as triage—not legal approval to remove content.

When to use this tool

  • Quarterly inventory sweeps

    Blend GSC URL exports with content scores to color-code what writers should touch next.

  • Legacy blog cleanups

    Highlight thin, low-click articles that dilute topical focus.

  • Stakeholder dashboards

    Six bucket counts show distribution before detailed manual reviews.

  • Training junior strategists

    Walk through the sample file to show how clicks, impressions, and age interplay.

Examples

Walk through these with the form above — they are practice scenarios, not live data.

High performer

Try this

Row with more than a thousand clicks should land in keep with solid traffic reasoning.

What to look for

Badge stays green; deprioritize pruning tickets for that URL.

Thin aged post

Try this

Fewer than fifty clicks, sub-three-hundred words, older than a year.

What to look for

Expect delete or merge style guidance—confirm legally and internally before removal.

Short tutorial

Follow in order the first time you use the tool; later you can skip to the step you need.

  1. Step 1 — Export merged metrics

    Combine Search Console URL data with CMS word counts and publish age.

  2. Step 2 — Match header names

    Use lowercase url,clicks,impressions,position,age,words exactly as the UI describes.

  3. Step 3 — Paste and scan buckets

    Totals per badge summarize portfolio health at a glance.

  4. Step 4 — Manual review each delete candidate

    Check backlinks, brand value, and legal retention before taking action.

  5. Step 5 — Execute merges in other tools

    Pair Content consolidator planning with redirect work when you merge URLs.

More detail

New here? Skim Start here first, then run one Examples scenario in the form above.

Content Pruning Analyzer does one job: identify low-value pages for removal, redirect, or rewrite. It lives under Content & Writing on SEOToolkits, where the beginner idea is simple: Content SEO is the practice of making a page useful, clear, and complete enough to satisfy a searcher.

FAQ

Why is noindex never shown?
The current rule set never assigns noindex even though the legend reserves the badge for future rules.
Can I customize thresholds?
Not inside this UI. Export to Sheets and apply your own formulas if you need bespoke cutoffs.
Does it fetch live pages?
No. You supply metrics CSV-style. Crawler word counts should match your CMS exports.
Will delete recommendations auto-run?
Never. Human editors must confirm removals, redirects, and messaging impacts.

Same workflow cluster on SEOToolkits — open another module without leaving context.