How to Run a Content Audit in a Weekend

A content audit sounds like the kind of thing you schedule for "next quarter" and then never do. That's usually a mistake. Say you run a 40-person B2B software company with a blog that's been live for four years, somewhere around 300 published posts, and nobody on the team could tell you which ones still earn their keep. That's a normal state for a growing company to be in, and it's fixable in two days, not two months. This content audit guide walks through that exact scenario, from Friday night to Sunday afternoon, using nothing but a spreadsheet and whatever analytics tool you already have logged into.

The whole point is to keep the scope tight. Not every page, not every metric, not a rebuild of your content strategy. Just a clear decision on every URL you've published, made fast enough that you actually finish.

Start with the inventory

You can't make decisions about pages you can't see in one place, so the first move is building a single list of everything you've published. For that 300-post blog, the fastest route is the sitemap, usually sitting at yoursite.com/sitemap.xml, which lists every live URL your site is telling search engines about. Paste those into a spreadsheet.

Four columns matter for this pass. URL and title. Publish or last-updated date. Organic clicks over the last six months, pulled from your search analytics tool. Top keyword and its current ranking position. Leave a fifth column blank for now, that's where Saturday's decisions go.

This step is tedious and it's the only genuinely boring part of the weekend. Pulling six months of clicks and positions for 300 URLs takes a couple of hours if your export tools cooperate, longer if you're copying rows by hand. Do it Friday night while something's on in the background. Google's own guidance on creating helpful content points to exactly this kind of review after a traffic drop, asking whether each page still serves people well, and you can't answer that question until the numbers are sitting in front of you [source: https://developers.google.com/search/docs/fundamentals/creating-helpful-content].

By the time you close the laptop Friday night, every row in the sheet should have a URL, a date, and traffic data attached. That's the whole setup. Everything after this is judgment, not data entry.

Sort every page

Every page in the spreadsheet gets one of four labels: keep, improve, merge, or remove. Four buckets, no fifth option, no "maybe later" column, because ambiguity is what makes audits stall out.

Keep is for pages that already work. Steady traffic, a solid ranking, information that's still accurate. Leave these alone entirely. For the software company's blog, that might be a handful of evergreen how-to posts that rank on page one and haven't needed a touch in a year.

Improve covers pages with traffic or ranking potential they're not reaching. A post sitting at position 11 for a term with real search volume, or a page racking up impressions in Search Console without the clicks to match, or content that's simply gone stale while the topic still matters. These are usually the best return on a weekend's effort, because pushing an existing page from page two to page one is cheaper than writing something from scratch and hoping it ranks eventually.

Merge is for the thin, overlapping stuff. Say the audit turns up three separate posts on "API rate limiting" written over two years by different people on the team, each thin, each ranking nowhere, each quietly splitting whatever authority the topic could carry. Combine them into one page, take the strongest sections of each, and redirect the old URLs. One solid page usually outperforms three mediocre ones covering the same ground.

Remove is for pages with no traffic, no backlinks, and no strategic reason to exist. Old product announcements, thin posts that were written to hit a quota, event pages for a webinar three years gone. Before deleting anything, check for backlinks and even a trickle of traffic, because removing a page that outside sites still link to is a way of throwing away authority you already earned.

Judge each page by what it could be worth going forward, not by how long it took to write. A post that took three days but ranks for nothing is still a remove, no matter how that stings.

Pick the highest-value fixes

A spreadsheet full of decisions isn't a plan yet. It's a list. The next move is ranking the "improve" and "merge" rows by how much they're actually worth chasing, because trying to fix all of them is how audits die on Sunday afternoon without shipping anything.

The commercially useful pages come first. That means anything already picking up impressions in Search Console, anything ranking just outside page one, positions 8 through 15 are the sweet spot, and anything covering a topic that overlaps with what you sell. A page at position 9 for a term your buyers actually search deserves far more of the weekend than a page at position 40 for a term nobody with a credit card is typing in.

Semrush's write-up on Jacaranda Finance is a useful reference point here. The company had roughly 500 content-heavy pages, ran a structured audit using traffic, engagement, keyword rankings, backlinks, social shares, and search intent as the inputs, and cut its page count by half, ending up with dozens of pages that actually ranked well [source: https://www.semrush.com/company/stories/jacaranda/]. Half the library, better results. That's the entire argument for pruning instead of publishing more.

Mark the top ten rows you'll genuinely touch this weekend and park everything else in a backlog for later. For the hypothetical software blog, that might mean three "improve" pages on core product topics, two merge candidates covering the same integration guide, and a batch of five outdated announcement posts ready to go.

Make the changes

Sunday is for execution, not admiration of the spreadsheet you built. A realistic day covers a handful of concrete moves rather than the whole backlog.

Rewriting title tags and meta descriptions on high-impression, low-click pages is the fastest win available and you can knock out three or four in an hour. Refreshing an "improve" page means updating stale facts, tightening the intro, adding whatever sections competitors are ranking with that you're missing, and linking it to and from related posts on the site. Executing a merge means combining the thin pages, setting up 301 redirects from the old URLs to the new one, and publishing the consolidated version. Processing the remove batch means deleting or redirecting each page, and this is also where Google's Refresh Outdated Content tool earns its keep, since it lets you flag pages that no longer exist so stale versions clear out of search results faster [source: https://support.google.com/webmasters/answer/7041154?hl=en]. Once changes are live, submitting an updated sitemap and requesting recrawl on the affected URLs gets the changes reflected in search sooner rather than waiting for the next natural crawl [source: https://developers.google.com/search/docs/crawling-indexing/ask-google-to-recrawl].

That's a full, genuinely useful day. You won't clear the entire backlog, and trying to would defeat the purpose. The value of the weekend is the decisions, which hold up for months, not the fixes, which continue afterward at whatever pace the team can sustain.

Keep the list current

An audit isn't a one-time cleanup. Blogs drift out of date because nobody maintains them as they grow, and the decisions made this weekend will stop reflecting reality within a year if nothing follows.

A quarterly half-day on the calendar to re-pull traffic numbers and re-sort the existing spreadsheet is far lighter than repeating the full audit, since the inventory already exists and only the numbers need refreshing. Semrush's own audit guidance frames the process the same way, as a repeatable workflow run from a template rather than something rebuilt from scratch each time, and notes that fresh, well-maintained content matters for both traditional search rankings and how AI platforms surface answers [source: https://www.semrush.com/blog/content-audit/?k_id=3143d801-76b3-4edb-8460-beabbea5c19c]. Ahrefs makes a similar point in passing, noting that a small team can run a full site audit in-house without outside help, which holds just as true for content as it does for technical SEO [source: https://ahrefs.com/blog/examine-seo-case-study/].

The value of an audit isn't the traffic bump from one weekend of fixes. It's finally knowing what you've actually published, instead of adding new posts on top of a backlog nobody's inspected in years.