UX AuditTYPENORMLabs8 minJuly 24, 2026

What Is a Content Audit? How to Run One, Step by Step

A content audit is a structured review of every page you own — inventory, score, decide. Here's what a content audit is, the step-by-step process, and how to decide what to keep, revise, merge, or delete.

Most sites don't have a content problem. They have a too much content problem — years of blog posts, half-finished landing pages, three articles that all half-answer the same question, and a support doc nobody has opened since 2021. Every one of those pages costs you: it dilutes your topical authority, splits your own rankings against each other, and makes the site feel bloated to the humans trying to use it. A content audit is how you find out what you actually have, and decide what deserves to stay.

So what is a content audit? At its simplest, it's a structured review of every page you own: you inventory what exists, score each page against a consistent set of criteria, then decide — keep, revise, merge, or delete. That last step is the whole point. An audit that ends in a spreadsheet nobody acts on isn't an audit; it's an inventory with anxiety attached. This guide walks the process end to end. It's a close cousin of the broader UX audit: the same discipline of scoring what exists before you change it, pointed at content instead of screens.

What is a content audit, really?

The word "audit" scares people because it sounds like accounting. Strip that away and it's three verbs: inventory, evaluate, decide. You list every URL, you judge each one against the same yardstick, and you make a call on its future. The rigor lives in consistency — every page gets scored on the same axes, so a low score means something and the decisions defend themselves later when someone asks "why did you delete my article."

A content audit is not the same as a content strategy, though it feeds one. The audit tells you the state of what exists today; the strategy decides what to publish next. And it's distinct from a one-off "let's refresh the blog" — a refresh edits pages you already like, while an audit questions whether each page should exist at all. The uncomfortable output of a good audit is a delete list, and that's the part most teams flinch from and shouldn't.

Why bother

Three payoffs, roughly in order of how fast you'll feel them:

  • You stop competing with yourself. When four pages target the same query, search engines split your authority across all four and rank none of them well. Merge them into one strong page and rankings usually consolidate upward.
  • You cut maintenance drag. Every live page is a promise you keep — links to fix, facts to update, a tone to hold. Pages that earn nothing still cost that upkeep. Deleting dead weight is the cheapest performance win most sites have.
  • You find the gaps. Laying every page on one grid makes the holes obvious: the topic cluster with a strong intro and no follow-through, the product page with no supporting content pointing at it. The audit is as much about what's missing as what's rotting.

The content audit process, step by step

1. Inventory every page

You can't judge what you can't see. Pull a complete list of live URLs — a crawler like Screaming Frog, a sitemap export, or your CMS's own page list. Dump them into one sheet, one row per URL. Grab the cheap metadata while you're there: title, publish date, word count, author.

This is also the reality check. Teams routinely discover they have two or three times more pages than they thought, most of them long forgotten. If you'd rather not build the grid from scratch, our free content audit template gives you the columns and scoring model ready to fill.

2. Pull the numbers that matter

Bolt on the data that tells you whether each page is pulling its weight. At minimum:

  • Traffic (organic sessions over the last 6–12 months) from analytics.
  • Search performance (impressions, clicks, average position) from Search Console.
  • Engagement (time on page, bounce, conversions or assisted conversions).
  • Links (internal links pointing in, and any external backlinks — backlinks are a strong reason not to delete).

Twelve months is the right window; anything shorter punishes seasonal pages unfairly.

3. Score each page against consistent criteria

This is where judgment comes in. Score every page on the same handful of axes — a simple 1–3 or high/medium/low is plenty. The axes that earn their place:

  • Performance — does it get traffic, rank, or convert?
  • Quality — is it accurate, well-written, and genuinely useful today?
  • Relevance — does it still fit who you are and who you serve?
  • Strategic fit — does it support a page or product that matters?

The point of scoring, rather than eyeballing, is that it forces a decision on the pages in the mushy middle — the ones that aren't obviously great or obviously dead. Those are exactly the pages a "quick refresh" leaves untouched forever.

4. Decide: keep, revise, merge, or delete

Every row resolves to one of four actions:

  • Keep — strong on the axes, leave it alone. Note the next review date and move on.
  • Revise — good bones, stale or thin execution. Update facts, deepen thin sections, fix the title, add internal links. Your highest-ROI bucket, because you're improving a page that already has some equity.
  • Merge — several pages circling one topic. Combine them into the single best version, then 301-redirect the losers into it so their link equity flows to the survivor.
  • Delete — no traffic, no links, no strategic reason, no realistic path to any of those. Redirect it to the nearest relevant page (or return a clean 410 if nothing fits). Deleting genuinely dead pages can raise overall site quality in the eyes of search engines — you're concentrating value, not losing it.

A quick guardrail on delete: check for backlinks and existing rankings first. A page with earned links or a page-one position is worth reviving before you kill it, even if its traffic looks flat this quarter.

5. Turn the audit into a plan

The spreadsheet is not the deliverable — the prioritized action list is. Rank the actions by impact against effort: merges that consolidate rankings and revisions to pages already ranking on page two are usually top of the list; net-new rewrites are slower to pay off. Assign owners and dates, or the audit joins the graveyard of documents everyone agreed with and nobody executed.

SEO content audit vs. UX content audit

"Content audit" means two overlapping things depending on who's asking. An SEO content audit weights rankings, search intent, keyword cannibalization, and internal linking. The question behind it is "does this content win search?" A UX content audit weights clarity, reading level, tone, and whether the page actually answers the question a real person arrived with. It asks something narrower: does this content serve the reader in front of it?

You want both lenses on the same grid. A page can rank on page one and still lose every reader who lands on it. The reverse happens too: careful, well-made writing aimed at a query nobody types. Score for search and for the human, and the merge/revise/delete calls get a lot less arguable.

How often should you run one

A full site-wide content audit is a once-a-year job for most teams — twice a year if you publish heavily. Between the big passes, run a lightweight rolling audit: every quarter, pull the pages that have lost the most traffic and triage just those. The annual audit catches structural rot; the rolling one catches decay before it compounds. What you don't want is the five-year audit, where the backlog is so large the project dies before the delete list ships.

FAQ

What is a content audit? A content audit is a structured review of every page on your site. You inventory what exists, score each page against consistent criteria (performance, quality, relevance, strategic fit), and then decide what to keep, revise, merge, or delete. The goal is a prioritized action plan, not just a spreadsheet.

How long does a content audit take? For a small site (under ~100 pages), a focused audit is a few days of work. Larger sites scale with page count — the inventory and data-pull are quick to automate, but the page-by-page scoring is the time sink. Splitting a big site into sections and auditing one section at a time keeps the project shippable.

What tools do I need? A crawler (Screaming Frog or your CMS export) for the inventory, analytics and Search Console for the numbers, and one spreadsheet to hold it all. A pre-built content audit template saves you setting up the columns and scoring model from scratch. You don't need expensive tooling to run a solid audit.

Should I really delete pages? Yes — thoughtfully. Pages with no traffic, no links, and no strategic role drag down the whole site's perceived quality and cost you upkeep. Redirect them to a relevant page so any residual value carries over. The one exception: check for backlinks and existing rankings before deleting, because those are worth reviving rather than losing.

What's the difference between a content audit and a UX audit? A content audit scores the pages themselves — are they useful, findable, worth keeping. A UX audit scores the product experience around and beyond the content — flows, interface clarity, friction. They share the same core method (inventory, score, prioritize) and often run together.

The one call that matters

Strip away the tooling and a content audit is one honest question, asked of every page: if this didn't exist, would we build it today? Most sites are carrying far more than they'd guess, and a lean, deliberate content set where every page earns its place is worth the afternoon with the spreadsheet.

Free UX Snapshot for 50 Product Teams

Apply now and get a complimentary UX Snapshot — our rapid clarity audit delivered in 48 hours. Limited to the first 50 products.

Apply for Free UX Snapshot

Related

Information Architecture

UX Collective UX Teardown: Building the Biggest Design Publication on Rented Land

A UX teardown of UX Collective: the largest independent design publication runs entirely on Medium, and every page is shaped by owning the taste but not the platform. How the read flow races Medium for the reader — and the one tab that wins.

TYPENORMLabs · 5 min · July 24, 2026

Web
Information Architecture
Interaction Design

Research Methods

Usability Testing — A Step-by-Step Guide

How to run a usability test end to end: framing the question, picking moderated or unmoderated, recruiting five people, writing tasks that don't lead, and turning what you watched into a ranked list of fixes.

TYPENORMLabs · 8 min · July 29, 2026

Research Methods
UX Clarity
Web

Accessibility

Skip Navigation Links for Accessibility

A skip navigation link lets a keyboard user jump past the nav straight to the content. Four lines of markup, and almost every implementation gets the CSS or the focus wrong.

TYPENORMLabs · 7 min · July 25, 2026

Accessibility
Web