Most bloggers avoid content audits because the word “audit” sounds like a multi-week project involving spreadsheets, consultants, and a headache. It doesn’t have to be. For most blogs under a couple hundred posts, a useful first-pass audit takes an afternoon — not because you’re doing it sloppily, but because the goal of a first audit isn’t perfection. It’s visibility.This post walks through exactly how to do that first pass: what to look at, what to record, and what decisions to make once you can see your whole blog laid out in front of you.
Why Bother Auditing at All
If you’ve been publishing for a while without a deliberate structure, you likely have posts that overlap, posts nobody links to, and posts that used to rank and quietly stopped. None of that is visible from inside the WordPress dashboard, where posts are just a flat list sorted by date. An audit turns that flat list into a map — which is the prerequisite for building the content clusters discussed in the previous post in this series.You can’t fix what you can’t see. That’s really the whole case for doing this.
What You’ll Need
A spreadsheet (Google Sheets or Excel is fine)Access to your site’s analytics (Google Search Console is the most useful single source)An hour or two of uninterrupted timeEvery published URL on your blogThat’s it. You don’t need paid tools for a first pass.
Step 1: Pull a Full List of URLsExport every blog post URL you have. If your site has a sitemap.xml, that’s the fastest source — most platforms generate one automatically at yoursite.com/sitemap.xml or yoursite.com/post-sitemap.xml. Paste the list into your spreadsheet, one URL per row.
If you don’t have a sitemap, your CMS’s post list (sorted by date, exported or copy-pasted) works fine too.
Step 2: Add the Basic Columns
For each post, record:TitleURLPublish datePrimary topic (your own best guess, one or two words)Word count (rough estimate is fine)Last updated (if different from publish date)This is tedious but mechanical — you’re not making judgment calls yet, just recording facts.
Step 3: Pull in Performance DataOpen Google Search Console and export the Pages report for the last 12 months. Match it against your spreadsheet by URL and add two more columns:Clicks (last 12 months)Average positionThis step turns your audit from a content list into a performance map. Posts with high average position but low clicks might have a title or meta description problem. Posts with neither clicks nor decent position are candidates for a rewrite, a merge, or retirement.
Step 4: Group by TopicNow the actual audit work begins. Sort your spreadsheet by the “Primary topic” column and look at what clusters naturally. You’re looking for two things:
Groups of 4+ posts that clearly belong together — these are your candidate content clusters
Singletons — posts with no obvious siblings, which either need a cluster built around them eventually, or don’t deserve one and should be evaluated on their own merits
Don’t worry about perfect categorization here. The goal is a rough map, not a taxonomy PhD.
Step 5: Flag the ProblemsAs you go through each group, tag posts with one of these flags:Orphan — no internal links point to this post from anywhere else on the site (check this using a “site:yoursite.com [exact title]” search, or a crawler if you have one)
Overlap — two or more posts in the group are targeting essentially the same keyword or question
Decayed — a post that used to rank well (check older Search Console data if available) but has dropped significantlyThin — under 500 words, unlikely to be comprehensive enough to be useful as-is
These four flags are the ones worth tracking first. You can add more later, but these four alone will tell you 80% of what’s wrong with an unaudited blog.
Step 6: Make the Calls
With everything tagged, go group by group and make three decisions per cluster:
Which post is the pillar candidate? Usually the longest, broadest, or best-performing post in the group.Which posts need to be merged? Overlapping posts targeting the same query should usually become one stronger post, with the weaker one redirected.
Which posts need new internal links? Any orphan that fits a group gets added to your linking to-do list.
You now have a working map: pillar candidates, cluster members, merge targets, and a linking backlog. That’s a real content strategy, built in an afternoon, from information you already had sitting in your dashboard and Search Console.
What This Looks Like at Scale
This process works cleanly up to maybe 40–60 posts. Past that, the manual grouping step (Step 4) starts to break down — not because the method is wrong, but because human pattern-matching gets slower and less consistent the more rows you’re staring at. Bloggers with a couple hundred posts often quit the audit around this point, not because it stopped being valuable, but because it stopped being fast.
This is the part of the process most worth automating: reading every post’s content (not just its title), grouping by actual topical similarity rather than a guessed keyword, and flagging orphans and overlaps algorithmically instead of by eye. The judgment calls in Step 6 — which post becomes the pillar, what gets merged — still benefit from a human decision. But the grouping and flagging in Steps 4 and 5 are exactly the kind of repetitive classification work that doesn’t need to be done by hand past a certain blog size.
What to Do With the Results
Once you’ve got your map, the next posts in this series cover each fix directly: finding and repairing orphaned posts, building a proper pillar page, and deciding how many posts belong in a cluster. Treat this audit as the diagnostic step — everything downstream depends on having gone through it honestly, even if the results are a little embarrassing the first time you see your blog laid out end to end.
Most bloggers who do this for the first time find at least a handful of posts they’d completely forgotten existed. That’s normal, and it’s exactly the problem an audit is meant to surface.