FOOTPRINTSEO Training Center
(239) 457-1867
New
  • Module 094
  • 2026-10-23
  • "REX (Matt Diamante / Get-Found school)"
  • "Content Strategy / Technical SEO / Quality Signals"

Module 94: Content Pruning — The 3%-Clicks Cut List That Re-Ranks the Pages That Matter

The Signal — What Changed

Search Engine Land published a content pruning case study on October 19, 2026: a site pruned 33% of its pages — the ones driving just 3% of total clicks — and overall site performance improved after the cut. Two weeks earlier, on October 20, SEL also covered Google's clutterScore: a hidden quality signal where a bloated, overlapping, thin content inventory raises the risk Google's quality systems treat the whole site as scaled, low-value content — and drag down pages that were fine.

Two signals, one doctrine: the Get-Found "quality over quantity" rule now has published numbers behind it. A third of the URL inventory was consuming crawl budget, diluting topical authority, and contributing nothing — and deleting it helped.

Every client site in our roster has a dead-weight tail: old service pages, thin blog posts from 2022, duplicated location pages, tag archives nobody reads. This module is the playbook for finding that tail and cutting it safely — quarterly, not once.

Why It Works

Three mechanisms stack when you prune:

  • Crawl budget concentration. Googlebot has a finite crawl allocation per site. Every dead page it recrawls is a visit not spent on the money pages. Cut the tail, and the crawlers re-spend their budget on the pages that convert.
  • Topical authority dilution. Google evaluates site-level quality, not just page-level. When 30% of the inventory is thin, the site's average quality floor drops — and that floor caps how hard your best pages can rank. Pruning raises the floor.
  • Link equity consolidation. Internal links and any external links pointing at dead pages flow equity into nothing. Redirecting or deleting those pages pushes that equity to pages that can use it.

The clutterScore angle (SEL, Oct 20) is the enforcement mechanism: content-heavy sites with overlapping, near-duplicate inventory read as scaled content abuse risk even if each page individually looks innocent. The May 2026 spam update already punished scaled low-value content; pruning is the standing defense.

What pruning is NOT: it is not deleting pages that rank but don't convert (a page at #4 for a mid-funnel query may still feed leads). It is not a blog purge for aesthetics. Every cut is evidence-based: no traffic, no rankings, no links, no conversions — or a duplicate that should be consolidated.

How to Run It

For local service clients (HVAC, roofing, security, appliance repair)

  • Pull the inventory. Export all indexable URLs: site:domain.com in Google, plus your sitemap and GSC Pages report. Target: every URL Google knows about.
  • Pull the evidence. In Google Search Console → Performance, export last 12 months of clicks + impressions per URL. Cross-reference with rankings (GSC position data is enough for small sites).
  • Tag each URL in 4 buckets:
  • - KEEP — clicks in the last 90 days, or ranks top 20 for a service/city keyword.
    - CONSOLIDATE — ranks #20–50 or gets a trickle of impressions for the same intent as another page. Merge content into the stronger page, 301 the weaker one.
    - REDIRECT — dead page but has backlinks or internal links: 301 to the closest relevant page.
    - PRUNE — zero clicks in 12 months, no rankings, no external links: 410/delete (or noindex + remove from sitemap if you're nervous).

  • Fix the local offenders first. The classic Get-Found local pattern: one keyword per city page, one service per service page. If you have "Roof Repair in Kennesaw," "Roofing Services Kennesaw GA," and "Kennesaw Roofing Company" all competing, keep the one with history — consolidate the other two into it.
  • Update the sitemap and request recrawl of the survivors in GSC. Then wait a full crawl cycle (2–4 weeks) before judging results.

For insurance/YMYL clients (xactinsure.net, floridahealthinsuranceweb.com)

  • YMYL raises the bar — prune thinner, not broader. Google's quality raters expect depth, credentials, and review dates on insurance pages. Thin state-coverage pages ("Florida Medicare Plans 2025" with 200 recycled words) are the highest-risk inventory on the site.
  • Consolidate instead of expand when overlap exists. Two pages covering "Open Enrollment dates" and "Medicare enrollment deadlines" compete with each other. Merge into one deeper page with the licensed agent's byline, a review date, and a clear answer block in the first 100 words.
  • Never 410 a YMYL page that carries legacy rankings without a 301 — equity loss on health/insurance topics is slower to recover. When in doubt: consolidate with a redirect, don't delete.
  • Add E-E-A-T to the survivors. After the cut, audit the remaining pages for author credentials (license numbers), last-reviewed dates, and source citations. Pruning + E-E-A-T is the pair; pruning alone on YMYL is half the fix.

For e-commerce clients (gressofab.com, raybaconstore.com)

  • Facet/duplicate variants are the tail. Filtered category URLs, near-duplicate product variants, and discontinued SKUs bloat the inventory. Consolidate variants onto the canonical product, and noindex faceted URLs that add no search value.
  • Thin category pages (2–3 products) either get depth (buyer's guide intro + photos + FAQ) or get consolidated into the parent category.
  • Check Merchant Center alignment — with Universal Cart live in Search (Oct 23), feed hygiene and page inventory must match. Don't prune a page the feed still advertises.

Real Example

growwithfootprint.com runs this playbook as the internal case study. The blog archive is the obvious tail: years of SEO-tip posts where a handful drive nearly all clicks. The audit rule: any post with <10 clicks in the trailing quarter and no top-20 ranking gets pulled into the consolidation list — either merged into a related pillar (e.g., three thin "GBP tips" posts → one complete GBP optimization guide) or redirected to the closest evergreen piece. Pages with real backlinks get 301s; pages with nothing get 410s. The result template becomes the client deliverable: a one-page cut list with KEEP / CONSOLIDATE / REDIRECT / PRUNE tags and the projected crawl-budget savings, ready to hand to a roofer or an insurer alike.

pattonroofsystems.com gets the same logic in local form: expired storm-season pages (e.g., "Hurricane Season 2025 Roof Prep") become evergreen "Roof Repair vs. Roof Replacement" pillar content with the seasonal detail folded in — one strong page instead of a graveyard of dated ones.

Checklist

  • [ ] Exported full indexable URL inventory (GSC Pages + sitemap + site: search)
  • [ ] 12 months of clicks/impressions pulled per URL from GSC
  • [ ] Every URL tagged: KEEP / CONSOLIDATE / REDIRECT / PRUNE
  • [ ] No page tagged PRUNE that has backlinks (moved to REDIRECT instead)
  • [ ] Consolidations point 301s at the page with the stronger ranking history
  • [ ] Sitemap regenerated, survivors recrawled via GSC
  • [ ] YMYL sites: survivors carry author credentials + review dates
  • [ ] Re-check rankings 2–4 weeks post-prune before declaring victory

Quiz

Q1: A page gets zero clicks in 12 months but has 6 backlinks. Do you delete it?
No — pages with external links get redirected (301) to the closest relevant page, preserving the equity. Deletion (410) is reserved for pages with no traffic, no rankings, and no links.

Q2: For an insurance client with two overlapping Medicare enrollment pages, what's the right move?
Consolidate: merge them into one deeper page with agent credentials, a review date, and a clear answer block up top, then 301 the weaker page to it. YMYL pages should almost never be outright deleted — thin pages get merged, not dropped.

Q3: You prune 33% of a local service site's blog. When do you judge whether it worked, and what do you check?
After a full crawl cycle — 2–4 weeks — check: (1) survivor rankings in GSC, (2) crawl stats/crawl waste in the Crawl report, (3) whether consolidated pages picked up the merged keywords' impressions. Judging the day after the prune is the classic mistake.

Try This Today

Pick the client with the biggest content archive — for us that's growwithfootprint.com — and run steps 1–3 of the audit in 30 minutes: export GSC Performance data for the last 12 months, sort by clicks ascending, and tag the bottom 50 URLs into KEEP / CONSOLIDATE / REDIRECT / PRUNE. You'll find 70–80% of them are obvious. That's the cut list draft — send it for review before touching anything.

Sources

  • Search Engine Land — "Content pruning case study: cutting 33% of pages that drove 3% of clicks" (Oct 19, 2026): https://searchengineland.com/
  • Search Engine Land — "Google's clutterScore: the hidden SEO risk for content-heavy sites" (Oct 20, 2026): https://searchengineland.com/
  • Google Search Console — Performance & Pages reports (the audit's data source): https://search.google.com/search-console
  • Google — Spam policies: scaled content abuse: https://developers.google.com/search/docs/essentials/spam-policies