A content audit is a structured pass over every page you have published, ending in a decision for each one. Most teams skip it because it sounds like accounting. Then they keep stacking new posts on top of old ones that compete with each other, embarrass the brand, or rank for queries nobody who buys anything ever types.
The audit is how you find out what you actually own. It often produces faster wins than a quarter of new content, because the fixes are cheap: a refresh here, a merge there, a short list of deletions. Here is how to run one without letting it swallow a month.
What a content audit actually is
One spreadsheet, one row per URL, one verdict per row. That is the whole artifact. An audit that produces a forty-page report and no decisions has failed, because the point is not to describe the content. The point is to decide what happens to each piece next.
Scope it to what you can finish. If you have sixty pages, audit all of them. If you have six hundred, start with the blog and the pages that used to get traffic. A complete audit of one section beats an abandoned audit of everything.
Step 1: build the inventory
Pull every URL from your sitemap or CMS export. Then add a few columns of data per page. Do not build a wall of metrics; you need just enough to judge each page against its job:
- The target keyword or topic, if the page ever had one
- Organic traffic over the last several months
- Impressions and average position from Google Search Console
- Publish date and the date it was last touched
- The page's job: bring traffic, convert visitors, support customers, or explain the company
Step 2: score every page against its job
There is no universal score. A page only fails relative to what it was for. A conversion page with modest traffic that keeps producing signups is a success. A traffic page with no traffic is not, no matter how well written it is. A support page is judged by whether customers still need it, not by its search rankings.
Go row by row and answer one question: is this page doing its job? Yes, partly, or no. Pages with no discernible job get flagged too, because a page with no job cannot be doing it.
Step 3: keep, refresh, merge, or delete
Every row now gets one of four verdicts:
- Keep: the page is doing its job. Leave it alone and check again next audit.
- Refresh: right topic, stale execution. Outdated details, thin coverage, a weak title. Update it and republish on the same URL.
- Merge: several thin pages circle one topic and split its strength. Combine them into the strongest URL and redirect the others to it.
- Delete: no traffic, no links, no job. Remove it, and redirect the URL if anything still points there.
Step 4: turn verdicts into a schedule
A verdict without a date is a wish. Put the refreshes into a queue and work through them at a steady pace, one or two a week alongside new content. Do the merges carefully, since they involve redirects, and batch the deletions so you can sanity-check the list once before removing anything.
This is also where the mechanics can stop being manual. Creaiter can pull your Search Console data into the same chat where you rewrite and republish a page, which turns the refresh queue from a one-time project into a habit. However you do it, the schedule is what separates an audit from a spreadsheet you made once.
How often to repeat it
For a small site, a full content audit once a year is enough, with a light quarterly pass over the pages that matter most. The second audit is much faster than the first, because the verdicts are already there and most pages just need their row updated. The pile only gets scary when nobody looks at it.
Keep reading