Content Marketing & CopywritingAuditing & Updating Historical Content

How to Run a Full Content Audit: Step-by-Step Process

A content audit is a systematic inventory of every page on your site, scored against performance and quality data, that tells you what to update, consolidate, or remove. Most sites of any real age have never had a full audit, which means genuine opportunities — pages one update away from a ranking jump, or ones actively dragging down site quality — sit unidentified for years.

Step 1: Build the full page inventory

Export every indexable URL using a crawler (Screaming Frog or Sitebulb) rather than relying on your CMS's content list, which often misses pages or includes ones no longer live. Cross-reference against your XML sitemap and Google Search Console's indexed pages report to catch discrepancies — pages that are live but not indexed, or indexed but no longer exist, are both worth flagging early.

Step 2: Pull performance data for every URL

For each page, gather: organic sessions and trend over the last 12 months (GA4), impressions, clicks, average position, and CTR (Google Search Console), backlinks and referring domains (Ahrefs or Semrush), and publish/last-updated date. Export all of this into one spreadsheet keyed by URL — this becomes your working audit sheet, and the single most time-consuming but essential step in the process.

Step 3: Add qualitative quality signals

Numbers alone miss real quality problems. For each page, or at minimum for every page below a traffic threshold worth investigating, note: does the content still accurately reflect current information, does it match current search intent for its target keyword (check what's actually ranking now), is it thin relative to top-ranking competitors, and does it have working internal and external links. This step requires actual human review and can't be fully automated, but you can triage efficiently by starting with pages that show concerning quantitative signals first.

Step 4: Score and categorize every page

Assign each page to one of a small number of categories based on the combined data:

  • Keep as-is: performing well, no meaningful gaps found.
  • Update: reasonable traffic or backlink history, but outdated, thin, or losing ground to fresher competing content.
  • Consolidate: overlaps significantly with another page on your site, splitting authority and cannibalizing rankings.
  • Redirect/remove: no meaningful traffic, no backlinks, no longer relevant to the business.

This categorization is the actual deliverable of the audit — everything before this step is data collection in service of making this call page by page.

Step 5: Prioritize within the "update" category

Not every page flagged for update deserves equal urgency. Rank them by a combination of current traffic (pages with existing traffic and rankings respond faster to updates than pages starting from zero), search volume ceiling for the target keyword, and business relevance. The next guide in this section covers prioritization in more depth, since it's often the step teams rush past, updating whatever's easiest rather than whatever matters most.

Step 6: Set a cadence for the next audit

A full site audit is a significant undertaking, but content decay is ongoing, so most sites benefit from a full audit annually and a lighter, rolling audit of your highest-traffic pages quarterly. Build the audit process (crawler settings, GSC/GA4 export queries, the scoring spreadsheet template) into a repeatable, documented workflow the first time through, so the second audit takes a fraction of the effort. For a deeper look at this, see our guide, Crawl Errors & Broken Links.

Tools that speed this up

Beyond Screaming Frog, GA4, and Search Console, dedicated content audit tools like Semrush's Content Audit feature or ContentKing can automate much of the data pulling and flag decay patterns automatically. For sites without budget for additional tools, the spreadsheet-based manual process above works perfectly well — it just requires more hands-on time to assemble. For a deeper look at this, see our guide, Mobile-First Indexing & Responsiveness.