Content Audit
Most content audits are wasted because the team skips deduplication and then acts only on traffic data. You must crawl and clean first.
Start here
- Crawl every indexable URL on your site and deduplicate before you analyse anything.
- Combine quantitative data (clicks, impressions) with qualitative checks on relevance and intent match.
- Group pages into keep, improve, consolidate, delete or redirect – then prioritise by business impact.
- Schedule recurring audits every six to twelve months, not a one-off cleanup.
- Include product pages, landing pages and category pages, not just blog posts.
Plain-English take
A content audit is a full stocktake of the pages your site has that search engines can index. You gather every URL – from your sitemap, from [internal links](/internal-links-seo/), from analytics – then you score each one. The goal is not to fill a spreadsheet. The goal is to decide: what do I keep, what do I improve, what do I consolidate, what do I delete or redirect. Most people start with traffic and bounce rate. That is a mistake. I now start by checking whether a page actually matches the intent of the queries it ranks for. A page that gets 200 visits a month but answers the wrong question is worse than a page that gets 20 and converts. You also need to check for duplication. A single site can serve three versions of the same page because of URL parameters, trailing slashes or HTTP/HTTPS. If you do not deduplicate first, you will waste hours scoring clones. I use Screaming Frog to crawl, then export the list to Google Sheets. From there I pull Search Console data per URL and add a column for 'purpose match'. That column, more than any metric, tells me what to do.
I also add a column for 'business value' – does this page support a conversion or a subscription? Without that, you end up keeping content that ranks but does nothing for the bottom line.
When it actually matters
A content audit matters when you see organic traffic drop and you cannot explain why. It also matters when your site passes 100 indexable pages. Below that, you can probably eyeball everything. Above that, you need a system. I run an audit every time I take over a site, then again every twelve months. It also matters before a redesign or a migration. If you are about to move URLs, you need to know which pages actually drive value so you do not break or lose them. It matters when you suspect [keyword cannibalisation](/on-page-seo/) because two pages target the same query and neither ranks well. I found this on a client site last year: three blog posts all optimised for 'running shoe reviews'. None of them got above position 12 because they split the authority. Consolidating them into one strong page pushed it to position 3.
The audit also matters when you have old content that was written for the wrong audience or with outdated information. Refreshing that content can bring back traffic without writing anything new. The key is to act on the findings. If you stop at the spreadsheet, you wasted the crawl.
I have also used audits to identify [content gaps](/seo-content-strategy/) – topics that the site should cover but does not. The audit shows what competitors rank for that you do not, and you can fill those holes with a clear action plan.
What I got wrong
Early in my career I treated a content audit as a traffic report. I would export sessions, bounce rate and pageviews, then delete anything with low numbers. That was naive. I deleted pages that had strong backlinks and high click-through rates from a small set of queries. I also deleted pages that served a transactional purpose – a booking confirmation page, a thank-you page – that should never have been indexed in the first place. I now know that indexability matters more than traffic volume. I also used to ignore the [quality of the content](/blogs/). I would keep a page because it ranked well, even if the writing was thin and the user experience poor. That is short-sighted. Google's helpful content updates punish that. I changed my process: after the quantitative pass, I read a sample of pages and score them on 'would I recommend this to someone who asked the question?' If the answer is no, the page goes into the improve bucket regardless of its rankings.
Another mistake: I audited only blog posts. Product pages and category pages make up the bulk of many ecommerce sites, and they need the same treatment. I also skipped deduplication in my early audits, which meant I was double-counting pages that were essentially the same. That inflated my 'content gap' analysis and led me to write unnecessary content. I now crawl with Screaming Frog, deduplicate by canonical and by URL parameters, then filter to indexable pages only before I import data.
Next step
Quick answers
What is the difference between a content audit and a content inventory?
A content inventory is simply a list of all your content assets. A content audit adds analysis: you score each page for performance, quality, and intent match. The inventory is the raw data; the audit is the decision-making layer on top. You need both, but the audit is where the real work happens.
How often should I run a content audit?
I run audits every six to twelve months on most sites. If the site has frequent content publishing or major algorithm changes, six months is better. For smaller or static sites, once a year is enough. The key is to treat it as a recurring process, not a one-off project. Set a calendar reminder.
Should I delete low-traffic pages or keep them?
It depends. If a page has zero traffic, no backlinks, no conversion history, and no opportunity to rank, delete or noindex it. But if it has a few hundred organic clicks or strong backlinks, improve it instead. Never delete based on traffic alone. Check the page's referral sources, its place in the site architecture, and its purpose.
Sources
Primary documentation is linked directly. Anything commercial is marked nofollow.
- Google Search Central — Because it covers indexing and canonicalization which affect audit inventory.
- Moz — Because it explains the keep/improve/remove framework I reference.
- Screaming Frog — Because it outlines practical crawl steps and index bloat issues.
- Search Engine Land — Because it frames the audit from goal setting to action planning.
Notes from Callum Bennett.