Content Writing
How to Conduct a Content Audit for Your Blog
A six-step blog content audit with the spreadsheet columns, a simple scoring rule and a way to turn a hundred verdicts into a work plan you can finish.
A blog content audit is a structured review of every post you have published, ending in one verdict per post: keep, update, merge or remove. You build a list of all URLs, attach performance data to each, read and score them against what the business needs now, and turn the verdicts into a prioritised work plan. The spreadsheet is the easy part; the verdicts and the follow-through are where audits succeed or stall.
There is good reason to do it. Ahrefs' study of around 14 billion pages found that 96.55% got no organic traffic from Google at all. Most blogs that have published for a few years have a long tail of posts doing nothing, a handful doing most of the work, and some quietly competing with each other. An audit tells you which is which.
Step 1: Decide What the Audit Is For
Write the objective in one sentence before collecting anything, because it decides which columns you need. Three common versions:
- Search visibility: "Find which posts can be improved to win more clicks from search." Emphasis on queries, positions, overlap and internal links.
- Lead generation: "Find which posts send readers towards an enquiry and fix the ones that should but do not." Emphasis on service-page clicks, calls to action and conversions.
- Clean-up: "Remove or merge content that is outdated, off-brand or inaccurate." Emphasis on accuracy, relevance and duplication.
Most audits are a mix. Pick a primary objective anyway; it settles ties when a post scores well on one dimension and badly on another.
Step 2: Build the Inventory
Get a complete list of blog URLs. Your XML sitemap is the quickest source; a crawler catches posts the sitemap misses, and your CMS export catches drafts and unlisted posts. Combine them and remove duplicates. Then add the basic facts for each URL.
| Column | Source | Why it is there |
|---|---|---|
| URL, title, publish date, last updated | CMS or crawler | Basic identification and age |
| Target query and intent | Your judgement | What the post is supposed to rank for and why someone searches it |
| Related service page | Your judgement | Where an interested reader should go next |
| Clicks, impressions, top query (last 12 months) | Search Console, Pages tab | Search performance; the top query shows what Google thinks it is about |
| Engaged sessions, key events | GA4 | What readers did once they arrived |
| Referring domains | Backlink tool (optional) | Whether removing it would waste links |
| Internal links in | Crawler | Whether the post is reachable from the rest of the site |
| Accuracy, quality, relevance scores (1 to 3) | Reading it | The judgement the numbers cannot make |
| Verdict, owner, due date | Audit decision | The only columns that change anything |
Search Console's interface exports at most 1,000 rows per table (Google's notes on the data limits). For a bigger blog, export by subfolder or use the Search Console API.
Step 3: Pull the Data for a Fair Period
Use twelve months where you can, so seasonal posts are judged across their season. For posts published in the last six months, mark them as "too new to judge" rather than scoring their traffic; new posts are still being discovered and an early verdict will be wrong.
Step 4: Read and Score Each Post
This is the step most audits skip, and it is the one that matters. Open each post and give three quick scores:
- Accuracy (1 to 3): are the facts, prices, screenshots and recommendations still true?
- Relevance (1 to 3): does it relate to something you sell, or to a question your customers really ask?
- Quality (1 to 3): would you be happy for a prospect to read it today? Does it answer the question better than the current top results?
Add a performance score from the data: 3 if it is in your top quarter for clicks or contributed to enquiries, 2 for the middle half, 1 for the bottom quarter. You now have four numbers per post and a reasonably objective basis for the verdict.
Three example rows show how the scores point towards a verdict:
| Post | Acc. | Rel. | Qual. | Perf. | Reading |
|---|---|---|---|---|---|
| "Small business tax deadlines 2023" | 1 | 3 | 2 | 2 | Still gets impressions, facts out of date: update with current dates |
| "10 blogging tips" and "Blogging tips for beginners" | 2 | 2 | 1 | 1 | Same intent, both thin: merge into one stronger post |
| "Our team at the 2019 trade show" | 3 | 1 | 2 | 1 | Accurate but irrelevant to buyers, no links: remove |
Step 5: Assign a Verdict
| Pattern | Usual verdict |
|---|---|
| High performance, high accuracy and quality | Keep. Check links and CTA; otherwise leave alone |
| Relevant, some performance, weak quality or accuracy | Update. The most valuable group in most audits |
| Two or more posts targeting the same intent | Merge into the strongest URL and redirect the rest |
| Relevant topic, no performance, good quality | Keep, add internal links, review again in six months |
| Irrelevant to the business, no performance, no links | Remove (404 or 410), or redirect if a close equivalent exists |
The edge cases, particularly merging and removing, are covered in detail in should you update, merge, or delete an old blog post, including how to redirect without wasting links.
Do not remove posts in bulk because they have little traffic. Google's own guidance on helpful content asks whether you are removing a lot of older content mainly because you think it will help rankings, and answers plainly that it will not. Remove posts because they are wrong, off-topic or duplicated, not because the traffic column says zero.
Step 6: Turn Verdicts Into a Work Plan
A hundred verdicts are not a plan. Sort the "update" and "merge" rows by a simple priority: commercial relevance first, then current impressions (posts Google already shows are the fastest wins), then effort. Then schedule them against your real capacity.
For example, a blog with 120 posts might end up with something like: 25 keep, 40 update, 15 posts merged into 6, 10 removed, and 30 new or too-new-to-judge. If the team can refresh four posts a month alongside new writing, the forty updates are a ten-month queue, which is why the order matters more than the total. How to do each refresh well is covered in how to refresh outdated blog content.
Put the verdict, owner and due date in the same spreadsheet as the data, and add a "done" date. An audit kept in a separate slide deck is usually forgotten within a quarter.
Common Audit Mistakes
- Collecting every metric available. Thirty columns take a week to fill and are rarely read. Collect what the objective needs.
- Judging new posts on traffic. Anything under six months old gets its own category.
- Skipping the reading. Numbers can say a post is underperforming but not why.
- Redirecting removed posts to the homepage. Redirect to a genuine equivalent or let the URL return a 404.
- Forgetting internal links after a merge. Update links that pointed at the old URL so readers do not pass through a redirect.
After the Audit
Set the review rhythm so you do not need another full audit for a year. Commercial and fast-changing posts need checking more often than evergreen guides; how often to update old blog posts sets out a tiered schedule.
If the audit leaves you with a refresh queue longer than your team can work through, you can hand it over: our blog management service is written in-house, with revisions until each piece meets the brief.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
A full audit once a year is enough for most business blogs, with a lighter quarterly check of your highest-traffic and most commercial posts. Run an extra full audit after a site migration, a rebrand, a change in services, or a sustained fall in organic traffic, because each of those changes what counts as a good post.
A spreadsheet, Google Search Console, Google Analytics and your sitemap are enough for a blog of a few hundred posts. A crawler such as Screaming Frog speeds up the inventory and catches broken links and missing titles. Backlink data from a tool like Ahrefs or Semrush helps when deciding what to merge or remove, but it is not essential to start.
It depends on how many posts you have and how carefully you read them. Pulling the data can be done in a day for a small blog. Reading and judging each post is the slow part; plan on a few minutes per post for a first pass and much longer for the ones you flag. Doing the resulting work takes far longer than the audit itself.
Not automatically. Some low-traffic posts support sales conversations, answer a niche question your best customers ask, or earn links. Check whether a post is accurate, relevant to what you sell and distinct from your other posts before removing it. Google also says that removing lots of older content purely to help rankings will not work.
An inventory is the list: every URL with its basic facts. An audit adds judgement: how each page performs, whether it is accurate and useful, and what should happen to it. You need the inventory first, but an inventory on its own changes nothing; the value is in the verdict column and the work plan that comes from it.