Sign in Start free

Prune Content That Dilutes the Site

Low-value pages do not merely fail to help - they consume crawl attention, spread internal link equity thin, and make it harder for Google to tell what the site is about. The instinct is to leave them alone because deletion feels risky. But the risky move is deleting without checking links and conversions, not pruning itself.

CATEGORY
Content strategy
FORMAT
prune-diluting-content.md
STEPS
6
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when a site has accumulated hundreds of pages, traffic is flat, and adding more content has stopped producing results.

The skill file

prune-diluting-content.md 
---
name: prune-diluting-content
description: Use when a site has accumulated hundreds of pages, traffic is flat, and adding more content has stopped producing results.
---

# Prune Content That Dilutes the Site

Low-value pages do not merely fail to help - they consume crawl attention, spread internal link equity thin, and make it harder for Google to tell what the site is about. The instinct is to leave them alone because deletion feels risky. But the risky move is deleting without checking links and conversions, not pruning itself.

## What you need first

- 12 months of Search Console page data
- internal link counts per URL
- conversion or assisted-conversion data per URL

## Method

1. List every indexable URL with under 10 clicks and under 100 impressions in 12 months. That is the candidate pool, not the deletion list.
2. Remove from the pool anything with external referring domains, any conversions or assisted conversions, or any role in a journey such as a pricing or contact page. Seasonal pages need a full 12 months before they are judged.
3. Sort the survivors into three actions: merge into a stronger page on the same topic, improve because the topic matters and the execution was poor, or remove.
4. For merges, move the useful content across, then 301 the old URL to the merge target. Never merge into a page on a different intent just to avoid a deletion.
5. For removals, return 410 rather than 404 for pages with no equity and no suitable redirect target - it gets them out of the index faster and stops Google recrawling them for months.
6. Prune in tranches of no more than 10 percent of indexable URLs at a time, and wait 4 to 6 weeks between tranches so you can attribute any change.

## What this produces

A tranche-by-tranche prune plan with merge, improve, or remove recorded per URL and the redirect target where applicable.

## Where this goes wrong

- redirecting every pruned URL to the homepage, which Google treats as a soft 404 and ignores
- deleting pages that carry external links, throwing away the only hard-won authority on the site
- pruning everything at once so when traffic moves you cannot tell which change caused it

---

From the QuQi skill library - https://www.quqi.io/skills/prune-diluting-content
Free to download · no account, no email

What you need first

  • 12 months of Search Console page data
  • internal link counts per URL
  • conversion or assisted-conversion data per URL

Method

  1. 01 List every indexable URL with under 10 clicks and under 100 impressions in 12 months. That is the candidate pool, not the deletion list.
  2. 02 Remove from the pool anything with external referring domains, any conversions or assisted conversions, or any role in a journey such as a pricing or contact page. Seasonal pages need a full 12 months before they are judged.
  3. 03 Sort the survivors into three actions: merge into a stronger page on the same topic, improve because the topic matters and the execution was poor, or remove.
  4. 04 For merges, move the useful content across, then 301 the old URL to the merge target. Never merge into a page on a different intent just to avoid a deletion.
  5. 05 For removals, return 410 rather than 404 for pages with no equity and no suitable redirect target - it gets them out of the index faster and stops Google recrawling them for months.
  6. 06 Prune in tranches of no more than 10 percent of indexable URLs at a time, and wait 4 to 6 weeks between tranches so you can attribute any change.

What this produces

A tranche-by-tranche prune plan with merge, improve, or remove recorded per URL and the redirect target where applicable.

Where this goes wrong

  • redirecting every pruned URL to the homepage, which Google treats as a soft 404 and ignores
  • deleting pages that carry external links, throwing away the only hard-won authority on the site
  • pruning everything at once so when traffic moves you cannot tell which change caused it

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/prune-diluting-content/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When is pruning the right move rather than publishing more?

When a site has hundreds of pages, traffic is flat, and new content has stopped producing results. Publishing more spreads internal link equity thinner across the same crawl attention. Prune when the problem is dilution rather than coverage. On a 40 page site there is nothing meaningful to prune and the effort is better spent building.

What do I need in hand before starting?

Twelve months of Search Console page data, internal link counts per URL, and conversion or assisted-conversion data. The conversion data is the input people skip and the one that stops you deleting a low-click page sitting inside a buying journey. Twelve months matters for seasonal pages too, which look dead for most of the year and are not.

What do I end up with, and which part of it gets used?

A plan recording merge, improve or remove per URL, with the redirect target where one applies. The tranche schedule is the operational part: no more than 10 percent of indexable URLs at a time with four to six weeks between tranches, so any traffic movement can be attributed to a specific batch rather than to pruning in general.

What ruins this most often?

Redirecting every pruned URL to the homepage. Google treats an irrelevant redirect as a soft 404, so you get neither the consolidation you expected nor a clean removal. Redirect only where a genuinely equivalent page exists, and return 410 for pages with no equity and no sensible target so they leave the index instead of being recrawled for months.

More in Content strategy

Build a Topical Map From Real Demand

Use when you have a subject area but no defensible list of what to publish, and keyword exports...

Prioritize by Effort Against Realistic Win

Use when your content backlog is longer than your capacity and you need to decide what gets buil...

Decide Build New or Refresh Existing

Use when a target query is one you already have a page for and you are unsure whether to rewrite...

Competitor Gap Analysis Without Fooling Yourself

Use when you want to learn from competitors' content but keep producing a list of topics you hav...