All posts

How to Conduct a Content Audit for Your Blog

A content audit sorts every post into keep, update, promote, or remove. The data to pull, a simple quality score, and what to do with each group of posts.

Stylized content audit dashboard showing six blog post rows with status dots (green for keep, orange for update, pastel indigo for remove), each row with a small traffic bar chart

Your blog has a few years of posts, traffic has gone flat, and you aren't sure which old posts help and which ones drag. A content audit settles it. You list every post, pull its search data, score its quality, and sort it into one of four groups: keep, update, promote, or remove.

The data pull is mechanical. The decisions are where the value is, and most of the gains come from one group: posts that still get traffic but have gone stale. This guide covers when an audit is worth doing, what to collect, how to score posts, and what to do with each group.

When a content audit is worth it

Run one when any of these is true:

  • Search traffic is flat or falling even though you keep publishing.
  • A Google core update hit the site and you need to see which pages lost ground.
  • Most of your posts are more than two years old and nobody has reviewed them.
  • You are planning a redesign, a theme change, or a platform move.
  • You have 100 or more posts and no longer know what is on the site.

If you have fewer than about 30 posts, skip the formal audit. Read every post, update the ones that are wrong, and spend the rest of the time writing. The blog traffic plateau guide covers that lighter approach.

An audit reviews what you already have. Finding topics you are missing is a separate job, covered in content gap analysis.

The four outcomes: keep, update, promote, remove

Two-by-two table with High Traffic and Low Traffic rows, Low Quality and High Quality columns, containing action cards: Update (high traffic + low quality), Keep (high traffic + high quality), Remove (low traffic + low quality), Promote (low traffic + high quality)
Traffic and quality decide the group. High traffic means keep or update; low traffic means promote or remove.

Every post lands in one of four groups based on two things: how much search traffic it gets and how good it is.

High quality

Low quality

High traffic

Keep: leave it alone apart from light upkeep

Update: rewrite and correct it, usually the biggest win

Low traffic

Promote: help people and Google find it

Remove or merge: redirect, consolidate, or delete

Step 1: List every post

Get every URL into a spreadsheet, one row per post, with the title, publish date, and last modified date. Ways to get the list:

  • Your XML sitemap, which WordPress and most SEO plugins already generate (see how to find a sitemap).
  • A crawler such as Screaming Frog SEO Spider, free for up to 500 URLs per crawl (pricing page).
  • The WordPress REST API: /wp-json/wp/v2/posts?per_page=100&page=1, then page 2, 3, and so on. 100 is the maximum per request (REST API reference).
  • A site crawl export from Ahrefs or Semrush, if you pay for one.

Step 2: Add search and traffic data

Add these columns for each URL, using the last three months and the same period a year earlier where you can:

Column

Where to get it

Clicks, impressions, average position

Google Search Console, Performance report, Pages tab

Top query for the page

Search Console, filter by page, then Queries tab

Organic sessions and engagement

Google Analytics 4, filtered to the Organic Search channel

Referring domains

Ahrefs, Semrush, or another backlink tool

Internal links pointing to the page

Screaming Frog, or your SEO plugin's link report

Search Console's web interface only exports 1,000 rows per table. For bigger sites, use the Search Console API or a connector that reads it for you. If you would rather ask questions than build pivot tables, you can connect Search Console to Claude and ask for clicks, CTR, and striking-distance queries in plain language.

Impressions matter as much as clicks. A post with lots of impressions and few clicks is close to working, and it is often the cheapest one to fix.

Step 3: Score each post on quality

A blog post card being scored across five criteria (Writing, Accuracy, Depth, Experience, Structure) with 1-5 dot ratings and an overall grade
Score each post 1 to 5 on five criteria, then average them.

This is the subjective part. Score each post from 1 to 5 on:

  • Writing: clear, edited, and free of filler.
  • Accuracy: every fact, price, screenshot, and link is still correct today.
  • Depth: it answers the question fully instead of skimming it.
  • Experience: it shows real knowledge or first-hand detail, not a rewrite of other people's posts.
  • Structure: useful headings, a direct answer near the top, and internal links.

Average the five. Treat anything under 3 as low quality and anything at 4 or above as high quality. Google's own questions for evaluating content (linked below) make a good second rubric if you want one.

On a large site, an AI model can draft scores against your rubric to save time (see using ChatGPT for SEO). Check a random sample by hand, because the model will be confidently wrong on some.

Step 4: Sort posts into groups

Set your cutoffs relative to your own site rather than borrowing someone else's numbers. A reasonable starting point:

  • High traffic: the top 20 percent of posts by search clicks.
  • Low traffic: posts with almost no clicks and no upward trend over the last year.
  • High quality: an average score of 4 or more.
  • Low quality: an average score under 3.

Posts in the middle on both counts can wait for the next audit.

Step 5: Act on each group

Keep (high traffic, high quality)

Don't break what works. Check these once a year: fix outdated facts, swap in links to newer related posts, and leave the URL, title, and main angle alone unless something is wrong.

Update (high traffic, low quality)

This group usually pays off the most, because the post already ranks. For each one:

  • Keep the URL, and keep the sections that answer the queries it gets clicks for.
  • Answer the main question in the first few sentences (see how to format a blog post).
  • Correct or cut every outdated fact, stat, and tool reference. Remove any stat you can't trace to its source.
  • Add what current top results cover that yours doesn't.
  • Change the "last updated" date only if the content changed in substance.

That last point comes straight from Google. Its helpful content guidance lists "changing the date of pages to make them seem fresh when the content has not substantially changed" as a warning sign. Editing the year in a title is not an update.

Promote (low traffic, high quality)

The post is good but nobody finds it. First, check whether anyone searches for its topic at all. If nobody does, it belongs with the remove-or-merge group, or it stays as a resource you share by hand. If there is demand:

  • Add links to it from three to five of your most-visited related posts.
  • Retitle it to match how people search, if the current title is vague.
  • Share it where your readers already are, such as your email list or relevant communities.

Remove or merge (low traffic, low quality)

These posts help nobody. Options, in order of preference:

  1. Merge several thin posts on one topic into a single strong post, and 301 redirect the old URLs to it.
  2. Redirect a single weak post to the closest relevant page, if one really covers the same thing.
  3. Noindex it if it still has a use for visitors, such as a page you link from emails, but shouldn't compete in search.
  4. Delete it and let it return a 404 or 410 when there is no relevant page to send people to. Google simply drops a removed URL from the index (Google Search Central).

Check for backlinks before deleting. A post with links from other sites should usually be redirected to a related page instead. Clean up internal links to anything you remove, too (see fixing broken links).

Don't prune for the sake of it. The same Google guidance warns against removing lots of older content just because you believe it will help rankings. Remove posts because they are bad or redundant, not because they are old.

Tools for each step

Step

Free

Paid

Inventory

XML sitemap, WordPress REST API, Screaming Frog (up to 500 URLs)

Screaming Frog license, Ahrefs or Semrush site audit

Search data

Search Console, Google Analytics 4

Ahrefs, Semrush

Scoring

A spreadsheet and your rubric

AI model drafts, checked by hand

WordPress

Rank Math or Yoast for SEO checks, a link checker plugin

Link Whisper for internal link reports

How often to audit

  • Under 100 posts: no formal audit. Review your top 10 posts every few months.
  • 100 to 500 posts: a full audit once a year.
  • More than 500 posts: audit one section or category at a time on a rolling schedule, so the job stays finishable.
  • Any size: a quick check of the hardest-hit pages after a core update causes a clear drop.

Common mistakes

  • Making decisions before pulling data. Without the numbers, the sorting becomes guesswork.
  • Judging posts on clicks alone. Impressions show where you are close to ranking.
  • Deleting posts that have backlinks instead of redirecting them.
  • Changing URLs during an update. Every slug change needs a 301 redirect (see SEO slugs).
  • Updating everything a little instead of fully fixing the posts in the update group.
  • Skipping the quality score. Traffic tells you what happened; quality tells you what to do about it.

Where to start

If you only have time for one thing, open Search Console, sort your pages by impressions, and fix the stale posts near the top. That is the update group, and it is where an audit pays off fastest. Once those are done, use a content gap analysis to plan what to add next.