Quick answer: a content audit is a review of every post on a blog to decide what to do with each one. Export a list of all published URLs, add performance data from Google Search Console and your analytics tool, then mark each post keep, update, merge, redirect or remove. Update posts that are outdated but useful, merge posts that answer the same question, and use 301 redirects when a URL goes away so readers and links land somewhere helpful. Do not delete posts simply because they are old; Google has said age alone is not a reason to remove content.
Blogs that have been around for a few years tend to collect clutter. Early posts written before the site had a clear focus, product roundups that list items no longer sold, thin posts that never found readers, and two or three articles that all try to answer the same question. None of that disappears on its own.
A content audit is the systematic way to deal with it. This guide walks through the full process: building an inventory, gathering data, making decisions post by post, carrying out changes safely, and keeping the site tidy afterward. It belongs to the maintenance stage of our guide on how to start a blog that makes money, because older content is often the fastest place to find improvements.
Why Audit an Old Blog
An audit is worth the time for several reasons.
Outdated posts can mislead readers. Prices, rules, software menus and program terms change, and a post that was accurate three years ago may now give wrong instructions. Updating or labeling that content protects readers and the site’s credibility.
Duplicate posts compete with each other. When two articles answer the same question, they can split links and attention, and neither may perform as well as one strong post would. Combining them often produces a better resource.
Strong old posts are often underused. Posts that already earn impressions in search but sit just off the first page can sometimes improve with a careful update, better internal links and a clearer title.
An audit also reveals structure. Mapping every post to a topic shows which subjects are well covered, which have gaps and which do not fit the site anymore.
What an audit is not
An audit is not a purge. Google’s guidance on creating helpful, reliable, people-first content focuses on whether content serves readers, not on how old it is. Google’s Search Liaison account has publicly said that deleting content simply because it is old is not something Google rewards. Removal makes sense for posts that are inaccurate, unhelpful and not worth fixing, not for posts that are merely dated.
Step 1: Build a Content Inventory
Start with a complete list of published URLs. A spreadsheet works fine.
Ways to pull the list:
- Export posts from WordPress using a plugin or the built-in export tool, or copy the list from your XML sitemap
- Download the Pages report data from Google Search Console
- Use a site crawler to fetch every page and its title, word count and status code
Useful columns for each post:
- URL and title
- Publish date and last updated date
- Category and the topic cluster it belongs to, if any
- Word count
- Primary keyword or the question the post answers
- Number of internal links pointing to it
- Any monetization on the page, such as ads, affiliate links or a product offer
Group posts by topic as you go. That grouping will make duplicates obvious later.
A note on scale: a blog with a few dozen posts can be audited by hand in a spreadsheet. Larger archives benefit from a crawler export, because checking hundreds of URLs one by one invites mistakes. Either way, freeze new publishing in the topic you are auditing until decisions are made, so nothing new overlaps a post that is about to be merged.
Step 2: Add Performance Data
Numbers make decisions less subjective. Pull at least the last 12 months so seasonal posts get a fair hearing.
From Google Search Console’s Performance report, add clicks, impressions, average position and the top query for each page. From your analytics tool, add pageviews or sessions and an engagement measure. If the site earns money, add revenue by page where your ad network or affiliate dashboards allow it.
Look for these patterns:
- Posts with clicks and impressions: valuable, protect and improve
- Posts with impressions but few clicks: possibly a title or intent mismatch
- Posts with neither clicks nor impressions after a year or more: candidates for update, merge or removal
- Posts with traffic from sources other than search, such as Pinterest or email: keep even if search numbers are low
Remember that Search Console covers only Google Search. A post with no search traffic may still be a reader favorite on social media, so check every source before deciding.
Step 3: Decide What to Do With Each Post
Every post gets one of five labels. Writing a one-line reason next to each label helps when you come back to the sheet later.
Keep
The post is accurate, useful and performing reasonably. Leave it alone apart from small fixes such as broken links. Adding a link to a newer related post is fine.
Update
The post answers a real question but has outdated facts, thin sections, weak structure or missing images. Update it in place and keep the same URL. Typical updates include:
- Checking every fact, price and instruction against the current official source
- Rewriting the introduction to answer the question sooner
- Adding sections that cover questions searchers ask today
- Replacing missing or broken images and adding descriptive alt text, covered in our guide to image SEO for bloggers
- Adding or fixing internal links to the relevant pillar and related posts
- Checking that any affiliate or sponsored content carries a clear disclosure, as explained in our guide to affiliate disclosure for bloggers
Change the “last updated” date only when the update is substantial. Google’s documentation on dates in search results advises showing a date that reflects significant changes, not minor tweaks made only to look fresh.
Merge
Two or more posts answer the same question. Pick the strongest one, usually the one with the most clicks, links or the best URL, and fold the useful parts of the others into it. Then redirect the weaker URLs to the merged post with 301 redirects.
Redirect
The post no longer belongs on the site, but a closely related post exists that would serve the same reader. Point the old URL to that post with a 301 redirect. Choose genuinely related content as the destination; sending every removed URL to the home page frustrates readers, and Google’s documentation notes it may treat irrelevant redirects like soft 404 errors.
Remove
The post is inaccurate, unhelpful, off-topic for the site and has no related page to redirect to. Removing it is acceptable. Let the URL return a 404 or 410 status. Google’s documentation explains that both tell Google the page is gone, and that 404 errors for pages that no longer exist are normal and do not harm the rest of the site.
Step 4: Carry Out the Changes Safely
Changes to URLs and site structure carry risk, so work carefully.
- Back up the site, or at least export the posts you plan to change, before starting.
- Work through one topic group at a time rather than the whole site at once.
- For merges, publish the combined post first, then add redirects from the old URLs.
- Use server-side 301 redirects for permanent moves. Google Search Central’s documentation on redirects describes permanent server-side redirects as the best way to make sure Google and people are sent to the right page. On WordPress, a redirection plugin or your host’s tools can handle this.
- Update internal links that pointed to old URLs so they point directly to the new destination instead of passing through a redirect.
- Keep a log of every change: date, old URL, new URL and action.
- Check redirected URLs in a browser and with the URL Inspection tool in Search Console.
Redirects vs noindex vs canonical
Three tools are easy to confuse:
- A 301 redirect sends readers and search engines from one URL to another; use it when content has moved or been merged
- A noindex directive keeps a page available to visitors but asks search engines not to include it in results; use it for pages people need but searchers do not, such as thank-you pages
- A canonical tag tells search engines which of several similar URLs is the preferred version; use it for true duplicates that must both stay live, such as printer-friendly versions
For merged blog posts, a redirect is usually the right choice, because the old page no longer needs to exist.
Step 5: Strengthen What Remains
Once the clutter is handled, the audit sheet becomes a plan for improvement.
Map each kept or updated post to a topic. Clusters of related posts benefit from a pillar page that links to every post in the group, with each post linking back. Gaps in the map, questions no post answers, become new article ideas. Our guide to free keyword research for beginner bloggers explains how to check whether those gaps have search demand.
Prioritize updates by potential. Posts with many impressions but positions just off the first page usually reward effort sooner than posts with no visibility at all. Posts tied to how the site earns money deserve attention early too.
How Often to Audit
A full audit is a big job, and most blogs do not need one more than once a year. Smaller checks in between keep things from drifting:
- Monthly: review Search Console for posts with sharp drops and fix any obvious problems
- Quarterly: check broken links and outdated facts in your most-visited posts
- Yearly: run the full inventory, data pull and decision process
Seasonal posts deserve a check a few weeks before their season begins, so updates are in place when readers start searching.
Measuring the results
Changes from an audit take time to show up. Search engines need to recrawl updated pages and process redirects. Compare three-month periods before and after the audit rather than checking daily, and use your change log to connect results with specific actions.
Common Audit Mistakes
- Deleting posts in bulk based only on traffic numbers, without checking other sources or whether the post could be improved
- Redirecting removed posts to unrelated pages or the home page
- Changing URLs of posts that are performing well
- Updating the date without updating the content
- Merging posts but leaving internal links pointing at the old URLs
- Making many changes at once with no log, so results cannot be explained later
Frequently Asked Questions
How long does a content audit take?
It depends on the size of the blog. A site with a hundred posts can often be inventoried and labeled over a few working sessions, while larger sites may take weeks. Working through one topic group at a time keeps it manageable.
Should I delete old blog posts with no traffic?
Not automatically. First check whether the post could be updated, merged into a stronger post or redirected to a related one. Remove it only if it is inaccurate, unhelpful and has no related page to point to.
Will deleting posts improve my rankings?
Google has said that removing content simply because it is old is not something it rewards. Improving or consolidating weak content can help readers, which is the goal Google’s guidance describes.
Is a 404 bad for SEO?
Google’s documentation says 404 errors for pages that no longer exist are normal and do not hurt the rest of the site. Use a redirect when a closely related page exists, and let truly removed pages return a 404 or 410.
Should I change the publish date after updating a post?
Show an updated date when the changes are substantial. Changing the date without meaningful updates can mislead readers.Sources: Google Search Central, Creating helpful, reliable, people-first content; Google Search Central, Redirects and Google Search; Google Search Central, How HTTP status codes affect Google Search; Google Search Central, Block search indexing with noindex; Google Search Central, Consolidate duplicate URLs; Google Search Central, Influence the date shown in search results.