How to Run a Content Audit (And What to Do With the Results)

Why Run a Content Audit (and When It’s Actually Worth It)

Most business blogs are graveyards with a few live exhibits. A handful of pages earn nearly all the organic traffic, a middle tier limps along, and a long tail of posts hasn’t been seen by a human being since the week it was published. That distribution isn’t a failure — it’s the normal physics of content — but it creates a quiet problem: every page on your domain costs something. It costs crawl attention, it dilutes your topical focus, it shows up in site search, and when it’s outdated it actively misinforms the people who do land on it.

A content audit is the structured process of finding out what you actually have, how each piece is performing, and what to do about it. The output isn’t a report; it’s a decision per URL — keep, update, merge, or delete — and a prioritized list of which decisions to execute first.

The honest threshold: if you have fewer than roughly 30 pieces of content, you don’t need a formal audit. Read everything in an afternoon and make notes. The spreadsheet process in this guide earns its keep somewhere past that point, and becomes non-negotiable past a couple hundred URLs, where nobody at the company can hold the inventory in their head anymore.

Timing-wise, three triggers justify a full audit: you’re planning a site redesign or migration (auditing before you migrate is dramatically cheaper than after), organic traffic has been sliding for two or more quarters without an obvious cause, or it’s simply been more than a year since anyone looked. Outside of those, a lightweight annual pass plus quarterly spot checks on your money pages is a sane cadence for most small and mid-sized sites.

Step 1: Build the Content Inventory Spreadsheet

An audit starts with a complete list of URLs, and “complete” is doing real work in that sentence. Your CMS post list, your sitemap, and what search engines have actually indexed are three different sets, and the gaps between them are often where the problems live — orphaned pages the CMS forgot, indexed URLs from a template you retired years ago, drafts that went live by accident.

Pull URLs from at least two sources and merge them. A site crawler (Screaming Frog is the standard; its free tier handles up to 500 URLs) gives you what’s linkable from your own navigation. Your XML sitemap gives you what you’re telling search engines exists. Google Search Console’s pages report gives you what’s actually indexed and earning impressions. Dedupe the combined list, then scope it: a content audit covers blog posts, guides, resources, and landing pages — not your checkout flow or careers page. Service pages sit in a grey zone; include them if they’re meant to rank.

Then set up the spreadsheet. One row per URL, and a deliberately boring set of columns: URL, title, content type (post, guide, landing page), topic or category, publish date, last updated date, word count, and the target keyword or intent if one was ever assigned. Leave four columns empty for now — traffic, rankings, backlinks, and conversions — and two more at the end: Action and Priority. Those last two are the entire point of the exercise.

Resist the urge to add twenty columns. Every column you add is a thing you must now collect for every row, and audits die of ambition far more often than they die of laziness. Eight to twelve columns is the typical sweet spot; you can always deepen the data on the pages that turn out to matter.

Step 2: Pull the Performance Data That Actually Matters

Now fill the empty columns. Four data sources cover almost everything a content audit needs, and all but one are free.

From Google Search Console, pull clicks, impressions, and average position per URL over the last 12 months. Twelve months matters — a shorter window punishes seasonal content unfairly. GSC is your truth source for search performance, and it surfaces the most valuable pattern in any audit: pages with high impressions but low clicks, which means Google already believes the page is relevant but searchers don’t find the result compelling. Those pages are sitting one title-and-intro rewrite away from real traffic.

From Google Analytics, pull sessions, engagement, and — critically — conversions per landing page. Traffic columns get all the attention, but the conversions column changes decisions. A post with 80 visits a month that generates two enquiries outranks a post with 3,000 visits and none, and without conversion data in the sheet you will systematically misjudge which pages are carrying the business.

From a backlink tool (Ahrefs, Semrush, or Moz — or GSC’s own links report if budget is zero), pull referring domains per URL. This column exists to prevent the costliest audit mistake: deleting a page that other sites link to, vaporizing authority you spent years accumulating.

The fourth source is your own eyes. Data can’t tell you that a 2019 post recommends a tool that no longer exists, that the pricing is wrong, or that the writing embarrasses the brand. For any page the data flags as interesting, a two-minute human skim — accurate? current? on-brand? answers the query? — is the step that separates a real audit from a spreadsheet ritual.

Step 3: Score Every Page Into Update, Merge, Keep, or Delete

With the data in place, every URL gets a verdict. Two questions drive it: is the page performing, and is the topic worth competing for? Cross them and you get four quadrants, which map cleanly onto the four actions.

Performing and worth it — keep, and protect. These are your money pages. The action isn’t “do nothing”; it’s “monitor, keep current, and don’t break them in the redesign.” On most sites this is a surprisingly short list, which is exactly why it deserves explicit protection.

Underperforming but worth it — update. The topic has search demand or business relevance, but the page is stale, thin, outranked, or mistargeted. This is usually the largest actionable bucket and the highest-ROI one, because refreshing a page that already has age, links, and indexed history is typically far faster than earning equivalent results from a brand-new post.

Underperforming and redundant — merge. Three mediocre posts about the same question are worse than one strong post: they split internal links and force search engines to pick a winner among your own pages (the keyword-cannibalization problem). The tell is several URLs ranking weakly for the same query in GSC. Consolidate them into the strongest URL and redirect the rest.

Underperforming and not worth it — delete. No traffic, no rankings, no links, no conversions, no strategic reason to exist. Be honest here; this bucket is bigger than most teams want to admit.

Two overrides trump the quadrants. Pages with meaningful backlinks almost never get deleted outright — they get updated or merged so the authority is preserved. And pages that exist for non-search reasons (sales enablement, support deflection, compliance) get judged on that job, not on traffic.

What “Update” Actually Means (It’s More Than Changing the Date)

The update bucket is where audits go to die, because “update this post” is vague enough to mean anything. A real content refresh has a diagnosis first and edits second.

Start by asking why the page underperforms, because the fix differs by failure mode. If it ranks on page two or three for its target query, study what currently ranks: the pages above you define what a satisfying answer looks like for that query right now — the subtopics covered, the depth, the format. Close the gap honestly rather than padding word count; longer is not the goal, more complete is. If it has impressions but few clicks, the page is fine and the snippet is the problem — rewrite the title and meta description against the actual queries GSC shows it appearing for, which are frequently not the keyword the post was originally written for. If it gets traffic but no conversions, the content is doing its job and the page isn’t: fix the next step — the internal links, the relevant call to action, the path to a service page.

In every refresh, do the hygiene pass: correct anything factually outdated, replace dead external links, update screenshots and examples, tighten the intro (the original was probably written to warm up the writer, not the reader), and add internal links both ways — from the refreshed post to your important pages, and from your strong pages to it.

Keep the URL unless it contains a year or is genuinely broken; the URL carries the history you’re trying to leverage. Update the visible date and the dateModified only when the changes are substantive — search engines and readers have both gotten good at detecting cosmetic re-dating, and it spends trust for nothing.

Merging Content Without Losing What the Old Pages Earned

Consolidation is the most technically delicate action in the audit, and the one most worth doing carefully, because a good merge converts three weak assets into one strong one while keeping everything the originals earned.

First, pick the surviving URL. Default to the page with the most backlinks and the strongest ranking history — not necessarily the best-written one. Words are easy to move; authority isn’t. If one URL has the links and another has the better content, the content moves to the URL with the links.

Second, actually merge the content. A merge is editorial work, not concatenation. Take the strongest sections, examples, and angles from each source page and rebuild them into one coherent piece that fully covers the topic. Check each dying page’s GSC queries before you delete anything — if a page earned impressions for a phrasing or subtopic the survivor doesn’t cover, fold that in, or the merged page will quietly lose that demand.

Third, 301-redirect every retired URL to the survivor. Permanent redirects pass the overwhelming majority of link equity, and they catch every old bookmark, every external link, and every indexed reference. Then update your internal links to point directly at the surviving URL rather than bouncing through the redirect, and remove the dead URLs from your sitemap.

Expect turbulence. It’s typical for rankings to wobble for a few weeks after a consolidation while search engines re-evaluate, which is why you merge in batches you can monitor rather than all at once, and why you don’t merge your money pages in the same week as a product launch. Done right, the consolidated page commonly ends up stronger than the best of its sources — one complete answer beats three partial ones.

Deleting Content: The Scary Part That Usually Isn’t

Deleting published content feels like destroying work, so teams avoid it — and end up dragging hundreds of zombie pages through every redesign. The reframe that helps: you’re not destroying value, you’re removing pages that demonstrably have none, so that everything remaining is something you’d stand behind.

The deletion checklist, per URL: near-zero clicks over 12 months, no rankings worth rescuing, no meaningful backlinks, no conversions, no internal business function, and no salvageable angle that a merge or update would serve better. A page must fail all of those. Expired event announcements, thin tag pages, decade-old company news, 300-word posts written for a keyword strategy nobody remembers — this is the natural population of the delete bucket.

Mechanically, you have two clean options. If a related page exists, 301 the deleted URL to it — relevant redirects preserve whatever scraps of equity and user intent exist. If nothing related exists, let it return a 404 or 410; a genuine “this page is gone” is an honest and perfectly acceptable signal, and redirecting everything to the homepage is worse than a clean 404, since irrelevant mass redirects tend to be treated as soft errors anyway.

Two safety rails. Export and archive everything before deleting — content you remove from the site can still feed newsletters, sales answers, or a future rewrite. And delete in reviewable batches with a note in your annotations log, so that if something unexpected moves in the following weeks, you can see what changed and when.

What you should typically expect afterwards is nothing dramatic — and that’s the point. The win from pruning is rarely a traffic spike; it’s a cleaner crawl, a tighter topical footprint, and an inventory small enough to actually maintain.

Turning the Spreadsheet Into a Roadmap (Prioritization Beats Completeness)

At this point you have a verdict on every row, which is where most audits stall — a sheet with 200 decisions and no sequence. The fix is a Priority column with exactly three values, assigned by expected impact against effort.

Priority one: pages already on the edge of winning. Anything ranking in roughly positions 4 through 15 for a query with real demand, anything with high impressions and weak click-through, and any conversion-relevant page with a fixable flaw. These are days-to-results opportunities, and front-loading them does something strategically important: it produces visible wins early, which buys patience for the slower work.

Priority two: the structural fixes. Cannibalization merges, refreshes of declining money pages, and updates to pages with strong backlinks but weak content. Slower to pay off, but this is where the durable gains live.

Priority three: everything else — the long-tail deletions, the minor cleanups. Batch them into maintenance windows rather than scheduling them individually; a hundred small deletions are one afternoon’s work if you treat them as one task.

Then put the roadmap on a calendar with names attached. A realistic cadence for a small team is typically two to four meaningful refreshes a month alongside one consolidation batch — modest, but compounding, and far better than the heroic two-week audit sprint that touches nothing afterwards.

Finally, measure what the audit changed. Annotate the date each action shipped, then compare each URL’s clicks, position, and conversions over the following 8 to 12 weeks against the prior period — organic changes need that long to read. We run this exact loop on SearchPod client sites, and the pattern repeats: the audit that gets executed at ten URLs a month beats the comprehensive one that ships as a PDF.

The last deliverable is a habit, not a document. Keep the inventory alive — add new content to it as it publishes, re-pull the data quarterly for your top pages — and the next audit stops being an excavation and becomes a review.