How to Do an SEO Content Audit
On this page
- Join the data before you decide anything
- The six-action decision framework
- Consolidation mechanics
- When removal, noindex, and redirect each apply
- Why pruning lifts the whole site
- The mistakes that ruin an audit
- Frequently Asked Questions
- Should I delete pages that get zero traffic?
- Is removing content actually good for SEO?
- How often should I run a content audit?
- Sources
- Related posts:
A content audit is a per-URL decision: keep, improve, consolidate, redirect, noindex, or remove. You make that decision by joining performance, backlink, and intent data, then acting on the verdict. The main lever is not endlessly improving your winners. It is removing or merging the dead weight, because a large body of low-value pages dilutes site-wide quality and drags down the pages you care about. Most audits go wrong by optimizing what already works and ignoring the long tail of pages that are quietly costing you.
Join the data before you decide anything
You cannot judge a URL on a single metric, and most bad audit decisions come from looking at only one. Before assigning any verdict, build one inventory row per indexable URL that joins at least these fields:
- Clicks, impressions, and average position from Google Search Console
- Referring domains or backlinks pointing at the URL
- Word count and last-updated date
- Crawl and index status (indexed, or excluded with the reason)
- The query intent the page targets, and whether you still serve it
Backlinks are the field that most often flips a verdict, which is why they have to be in the join. A page with zero traffic looks like an obvious deletion until you see it has referring domains. Delete it and you throw away link equity that a 301 could have preserved. The whole point of joining the data is that no single column tells you what to do; the verdict is the intersection of three signals (does it earn traffic, does it hold equity, does it still serve a live intent), and a page can fail one while passing another.
The six-action decision framework
Run each URL through a short decision tree and assign exactly one action.
| Signal pattern | Action |
|---|---|
| Gets traffic, healthy | Keep, monitor |
| Gets some traffic, underperforms its intent | Improve |
| Two or more URLs competing for the same intent | Consolidate |
| No traffic, has referring domains | Redirect (preserve equity) |
| No traffic, no links, topic you still want to own | Improve or rewrite |
| No traffic, no links, topic you would not create today | Remove (410/404) or noindex |
The tree that produces this is short: does it get traffic? If yes, keep or improve. If no, does it have backlinks? If yes, it is a redirect candidate, not a deletion. If no backlinks, would you still create this page today? If yes, improve it; if no, remove or noindex it. The discipline is to ask the questions in that order, because asking “any traffic?” alone sends you deleting linked pages, and asking “any backlinks?” alone leaves you keeping dead content nobody links to or reads.
Consolidation mechanics
Consolidation is where most of the quality gain comes from, and where it is easiest to do damage. When two or more pages target the same intent, pick one keeper, usually the URL with the strongest backlinks and best existing rankings, not the most recent one. Merge the genuinely useful material from the losers into the keeper so the surviving page is more complete than any individual page was. Then 301-redirect the loser URLs to the keeper.
Two details matter. First, repoint internal links directly at the keeper rather than letting them resolve through the redirect; chained redirects waste crawl budget and lose a little equity at each hop, and they accumulate over years of audits. Second, do not consolidate pages that serve different intents just because they share a keyword. Two pages ranking for the same query with different jobs (a comparison versus a how-to) should be differentiated, not merged. Cannibalization is one trigger for consolidation inside an audit, but it is a trigger, not a goal in itself.
When removal, noindex, and redirect each apply
These three are not interchangeable, and using the wrong one either loses equity or leaves clutter indexed.
Redirect (301) is correct when a page has equity worth preserving (referring domains, or historical rankings) and there is a relevant destination to send it to. Never delete a backlinked page outright; redirect it.
Remove (410 or 404) is correct when a page has no traffic, no links, and no relevant redirect target, and you simply want it gone. A 410 (Gone) signals permanence more clearly than a 404, which can prompt Google to recrawl longer, but both result in deindexing. Use removal when there is nothing to preserve and nowhere sensible to send the user.
Noindex is correct when a page must stay live and accessible to users (a thin but necessary utility page, a tag archive, a filtered view) but should not compete in search. The page keeps serving its on-site purpose while leaving the index.
Why pruning lifts the whole site
Site-wide quality is evaluated by Google’s core ranking systems, not by a separate toggle. The standalone Helpful Content Update was folded into the core ranking system in the March 2024 core update, so there is no separate “HCU penalty” to recover from now; helpful-content quality is a site-wide signal applied through core updates. The mechanism for an audit is that a large proportion of thin, unhelpful pages can weigh on how the system assesses the site overall. Removing or consolidating genuine dead weight changes that proportion, which is why an aggressive, well-judged prune can lift pages you did not touch.
The honest caveat is that this works on the ratio, not on any single page. Removing a handful of pages from a site that is mostly thin will not move the signal; the prune has to be large enough to change the overall composition. And “low quality” has to be a real judgment, joined from the data, not a blind cull of anything below a traffic threshold.
The mistakes that ruin an audit
Two errors recur. The first is deleting backlinked pages because they have no traffic; this is the single most expensive audit mistake, because the equity is unrecoverable once the URLs return 404 and the links rot. Always check referring domains before any deletion and redirect instead. The second is auditing on traffic alone without intent: a zero-traffic page is not automatically a deletion. If it holds links, it is a redirect candidate; if it covers a topic you would still create today, it is an improve candidate. The verdict is a join of three signals, never a single number, and treating any one metric as the whole answer is how audits remove the wrong pages.
Frequently Asked Questions
Should I delete pages that get zero traffic?
Not on traffic alone. Check backlinks first: a zero-traffic page with referring domains is a redirect candidate so you keep the equity. Check intent next: if it covers a topic you would still create today, improve it instead of deleting. Only no-traffic, no-link, no-longer-relevant pages are clean removals. When you do act, roll the changes out in tracked batches and watch the affected URLs afterward, so a wrong verdict means reversing a single redirect instead of unwinding the whole audit.
Is removing content actually good for SEO?
It can be, because site-wide quality is assessed across all your indexed pages by the core ranking systems. Cutting or consolidating a meaningful proportion of thin pages changes the overall composition. It works on the ratio, so a small prune on a mostly-thin site will not move much; the cut has to be large enough to shift the mix.
How often should I run a content audit?
Tie the cadence to how fast the site changes rather than to a fixed calendar. A large, frequently publishing site benefits from a full audit roughly once a year, with lighter checks on new content in between; a small, stable site can go longer. The trigger that matters more than the calendar is accumulation: once you have published a meaningful volume of new pages, or after a core update changes how the site performs, the inventory is worth rejoining and re-deciding. Auditing too often wastes effort re-evaluating pages that have not changed; auditing too rarely lets dead weight build up unmeasured.
Sources
Google Search Central, spam policies (thin content, doorways): https://developers.google.com/search/docs/essentials/spam-policies
Google Search Central, removals and deindexing guidance: https://developers.google.com/search/docs/crawling-indexing/remove-information
Google Search Central, redirects and site moves: https://developers.google.com/search/docs/crawling-indexing/301-redirects