What Is a Content Audit? How to Review Content and Decide What to Fix

A content audit is a structured review of the pages, posts and landing pages you already have, in which every URL is judged against clear criteria and gets one decision: keep, update, merge, redirect or remove. Teams run content audits to improve SEO, user experience and content strategy. Without that review, a content library only grows and rarely improves.

• A content audit reviews existing content, not just missing keywords.
• It looks at performance, intent fit, freshness, quality and duplication, and increasingly at visibility in AI search.
• The output's a prioritized decision backlog, not a giant spreadsheet nobody opens again.
• A content inventory's the list of pages. The audit's the judgment you apply to that list.

What is a content audit?

A content audit is the process of reviewing your existing content against a clear set of standards so you can decide what to improve. Every page gets judged. Each URL either earns its place on the site or gets an action assigned to fix the problem.

Most content libraries grow faster than they improve. Teams keep adding pages, but older pages drift out of date, overlap with each other or stop matching what users need. An audit gives you a way to clean that up without guessing.

Five questions drive the whole process:

• Should this page stay live?
• Does it need a light refresh or a full rewrite?
• Is it competing with another page on the same site?
• Does it still match user intent?
• Is it helping traffic, trust or conversion in a meaningful way?

Content audit vs content inventory: A content inventory is a list of every page on your site, capturing metadata like URL, title and last-updated date. A content audit's the quality and relevance judgment you apply to that inventory. The inventory tells you what you've. The audit tells you what to do with it. Build the inventory first, then run the audit on top of it.

Types of content audits

The four common types differ in how much of the site they cover and how often they run.

Type	What it covers	Best for
Full audit	Every page on the site	A first audit, a migration, a rebrand or a site that was never reviewed
Partial audit	One section, cluster, content type or funnel stage	Teams with limited time and a clear problem area
Sample audit	A representative selection of pages, for example the top 10 percent by traffic plus a random slice of the rest	Large sites that need a health check before committing to a full review
Rolling audit	A fixed slice reviewed on a schedule, such as one cluster per month	Publishers who want the library reviewed continuously instead of in one big project

Quantitative vs qualitative audits

Most audits combine two layers. The quantitative layer is data you can export: URLs, traffic, rankings, backlinks, status codes, word counts. The qualitative layer is judgment you can only apply by reading the page, and it covers whether the answer is correct, current, complete and aimed at the right reader.

The quantitative layer tells you where to look. The qualitative layer tells you what to do. An audit that stops after the data export's a content inventory with colored cells.

Why a content audit matters

Noisy content operations are expensive. Too many similar pages, outdated advice, weak articles that never got a second pass and clusters that look larger than they really are all compound over time.

A good audit helps in several concrete ways.

• It finds pages that deserve an update before you create duplicates.
• It spots outdated examples, screenshots and pricing claims.
• It reduces cannibalization between similar URLs.
• It improves the consistency of a topic cluster.
• It focuses effort on the pages most likely to move traffic or revenue.

SEO isn't the only reason to run one. Content audits also support brand clarity, conversion, product education and editorial quality.

What does a content audit review?

Five dimensions shape every content audit: performance, intent fit, freshness, quality and depth, and duplication or overlap. A sixth lens, visibility in AI search, is now worth adding. Strong teams review each page through all of them at once rather than relying on data alone.

Performance

Start with the measurable signals: organic traffic, impressions, clicks, rankings, engagement, leads and assisted conversions. Whatever metrics matter for the page type go into the spreadsheet first.

Performance data shows whether a page gets attention. It can't tell you why a page succeeds or fails, but it gives you a strong starting point for judgment.

Intent fit

Pages underperform for many reasons. A query might want a comparison while your page's a generic explainer. Visitors might arrive at the top of the funnel when the real business need is mid-funnel education.

Intent fit is one of the highest-value review criteria. Healthy internal metrics can mask a page that's simply the wrong answer for the audience, and intent review is how you catch that gap.

Freshness

Some content types go stale fast: software pricing, feature lists, product screenshots, legal requirements and process guidance. When the facts are tied to a platform that has changed, the page is outdated whether it looks current or not.

Trust erodes quickly when examples, numbers or screenshots fall behind reality. A well-written page can still fail this check if the facts beneath it have moved on. This's the same underlying problem as content decay, and the fix's usually a targeted content refresh rather than a full rewrite.

Quality and depth

Manual review matters most here. Ask whether the page teaches, helps, compares or guides the reader. Thin sections, vague claims, weak examples and poor structure are all audit findings even when the page still ranks.

Quality review should include these checks.

• Each heading opens with a clear, direct answer.
• The depth matches the difficulty of the topic.
• Claims come with specifics, examples and proof.
• The page is easy to scan.
• Internal links lead to a useful next step.

Duplication and overlap

Some pages shouldn't both exist. Two URLs competing for the same query class is keyword cannibalization, and one thin page that belongs inside a stronger canonical page's a merge candidate. The audit should say so clearly.

Merging or redirecting weak overlapping pages often improves a cluster faster than creating new content, which makes it one of the highest-return actions in the whole audit.

AI search visibility

Pages aren't only read by people anymore; AI search features read, quote and link them too. Google states that there are no additional requirements to appear in AI Overviews or AI Mode and no special optimizations necessary, and that a page needs to be indexed and eligible to be shown in Search with a snippet to be a supporting link (Google Search Central).

For an audit, that turns the AI lens into a short per-page check rather than a separate project.

• Confirm that the page is indexable and eligible for a snippet.
• Check that each section opens with a direct, self-contained answer that can be quoted on its own.
• Make sure the facts are current and attributed, so a quoted passage doesn't spread outdated information.
• If you track AI citations or mentions with a tool, note which pages get cited and which never do.

Treat AI citation data as a signal to investigate, not a score. It's useful for spotting patterns, but it won't tell you what to fix, and it's still noisy. Tools differ a lot in how they measure it.

How to do a content audit

Doing a content audit isn't complicated once you break it into seven steps. Keeping the output actionable is the only real challenge. These steps apply whether you're reviewing a single cluster or an entire site.

1. Define the goal and the scope

Start with the question the audit's to answer. "Why did organic traffic fall?" and "Which pages should we merge before the relaunch?" lead to different audits. Write the goal in one sentence, because you'll check every later decision against it.

Then avoid starting with the whole site unless it's small. Pick a realistic slice: one topic cluster, one product line, one blog category or one stage of the funnel. For teams new to the process, a single cluster of 20 to 30 pages's a good starting point. On a larger site, begin with the pages that bring the most organic traffic or backlinks and work outward.

Unclear scope's the most common reason audits stall before producing output.

2. Build a page inventory

List the URLs in scope and capture the basic fields you need to review them:

• URL
• Page title
• Content type
• Target topic or keyword
• Funnel stage
• Owner
• Last updated date
• Core performance metrics (traffic, impressions, rankings)

A sitemap export or a crawl gives you the URL list. Google Sheets works well for most teams; larger operations may use Airtable or Notion.

3. Set the review criteria

Before scoring anything, decide what good looks like. Skip this step and different reviewers will judge pages by different standards. The scoring section below gives a ready-made scorecard.

4. Review each page manually

Now go page by page. Some signals come from analytics tools, but others require reading the page. Open each URL and judge whether it's still the right answer. If it isn't, say so.

Many teams rush this step. They export data, color a spreadsheet and call it done, missing everything that matters. Reading and judging each page is the core work, and no tool does that for you. For each page, also check the technical basics that decide whether it can perform at all: it should return a 200 status, be indexable, use itself as the canonical URL and have internal links pointing to it. Google's own guidance is that every page you care about should have a link from at least one other page on your site (Google Search Central).

5. Assign an action to each URL

Each page should end with one recommended action. Keep the action set small, because a complicated set won't get applied. The five actions are keep, update, merge, redirect and remove, and the decision matrix below shows when each applies.

If an action isn't obvious, the audit was probably too vague, and you'll want to tighten the criteria.

6. Prioritize the backlog

Not every page deserves work now. Prioritize by some mix of business value, traffic upside, conversion impact, cluster importance and effort required.

A page with moderate traffic but high commercial intent may deserve attention before a high-traffic page with little strategic value. The audit's job's to make those tradeoffs visible. Quick wins, such as a refresh for a page that already ranks on page two, usually go first. They're cheap, and they build trust in the process.

7. Measure the results

An audit that never gets measured can't improve the next one. Record the baseline (clicks, impressions, average position) for every page you change, then compare after search engines have had time to reprocess the pages. Common guidance is to wait at least a couple of months before judging a change, and longer for a page that's newly published.

Mark the date of each change in the sheet so you can tell which action caused which movement. Then feed the lessons into the criteria for the next audit.

Content audit template

You don't need special software to start. A spreadsheet with one row per URL and the columns below covers the whole workflow. The first nine are inventory and data columns, the last four are the audit itself.

Column	What it holds	Layer
URL	Full canonical address	Inventory
Title	Page title or H1	Inventory
Content type	Guide, comparison, landing page, glossary	Inventory
Primary topic	The query or topic the page should own	Inventory
Owner	Who is responsible for the page	Inventory
Last updated	Date of the last substantive change	Inventory
Clicks and impressions	Search Console data for the period you chose	Data
Indexable	Yes or no, from a crawl or URL inspection	Data
Inbound internal links	Count of internal links pointing to the page	Data
Score	Average of your 1 to 5 criteria	Audit
Action	Keep, update, merge, redirect or remove	Audit
Reason	One sentence explaining the action	Audit
Priority	High, medium or low	Audit

Here's the header row. Paste it into the first row of a new sheet (tab separated):

URL	Title	Content type	Primary topic	Owner	Last updated	Clicks	Impressions	Indexable	Inbound internal links	Score	Action	Reason	Priority

Two habits keep the sheet useful. Write the reason in a full sentence, so a stakeholder who wasn't in the review can follow the decision. And don't overwrite the data columns by hand: re-export them for each audit so the sheet stays comparable over time.

How do you decide whether to keep, update, merge, redirect or remove a page?

Look at the page's job, its performance and whether a better page on your site already covers the topic. That's the whole logic. The matrix below turns that into a starting rule for each action. These are rules of thumb, not laws: adjust them to your site and always read the page before you apply one.

Action	Typical signals	Rule of thumb
Keep	Meets intent, accurate, earns traffic or serves a business purpose	Leave it alone and recheck at the next audit
Update	Right topic and intent, but outdated facts, thin sections, weak title or declining clicks	Refresh the facts and sections, keep the URL
Merge	Two or more pages answer the same query, each partly	Combine the best parts into the strongest URL
Redirect	A page is retired or merged and still has backlinks or traffic	301 to the closest equivalent page, never to the homepage by default
Remove	No traffic, no links, no business role and no better home for it	Delete it, or archive it if it must be kept for legal or internal reasons

Some pages shouldn't be judged on traffic at all. Legal pages, contact pages, category pages and paid landing pages exist for other reasons, so mark them "keep (not a traffic page)" in the sheet instead of letting a low click count push them toward removal.

Be careful with removal; it's the one action that's hard to undo, so don't rush it. Before you delete or redirect a page, check whether it has referring domains pointing to it and whether other pages link to it. A page with no traffic can still be carrying links your site needs, and you'd lose them.

How should you score pages in a content audit?

The best scoring system is one your team will trust and reuse. A simple score from 1 to 5 across five or six criteria is enough for most audits, and the scale's simple enough that two reviewers reach the same conclusion independently.

Criterion	1 means	5 means
Accuracy and freshness	Outdated or wrong facts	Every fact current and attributed
Intent fit	Wrong answer for the query	Directly answers what searchers want
Depth	Thin, generic	Specific, complete, with examples
Structure	Wall of text	Answer-first, easy to scan
Uniqueness	Duplicates another page	Clearly owns its topic
Business value	No role in the funnel	Directly supports a goal

After scoring, translate the numbers into action. Not every weak page's a cut. A low-scoring but strategically important page usually becomes an update or rewrite candidate. A low-scoring page with low strategic value is more likely a merge or removal, especially if a stronger page already covers the same ground.

A simple decision rule: pages averaging 3 or above on intent fit and business value deserve at least a light update before removal is considered.

What tools do teams use for content audits?

Most teams combine a site crawler with analytics data and a spreadsheet; that's the setup that works. No single tool handles the full process, so it's practical to pick one from each category and connect them through a shared inventory file.

• Crawl and inventory: Screaming Frog SEO Spider and Sitebulb discover all URLs on your site and flag technical issues like broken links, missing meta descriptions and redirect chains. Both export a full URL list. Screaming Frog's free version crawls up to 500 URLs, which covers a single cluster or a small site (Screaming Frog).
• Analytics and performance: Google Analytics and Google Search Console are the standard starting point, since they're both free and cover organic traffic, impressions, click-through rates and top queries.
• Rankings and backlinks: Ahrefs and Semrush add ranking data, backlink signals and competitive comparisons when you need them.
• Spreadsheets and tracking: Google Sheets or Notion hold the master audit document where you paste crawl data, add analytics columns and record the status and action for each URL.
• All-in-one platforms: Tools like Siteimprove or the Semrush Content Audit tool combine crawl, analytics and quality scoring in one interface. They can save time on larger sites, though they're usually overkill for a focused cluster.

Audit scope mostly decides tool choice. For a single cluster on a small blog, Search Console exports and a spreadsheet are enough. A full-site audit for a large editorial operation fits a dedicated crawler and an integrated platform better.

Content audit example

The scenario below is illustrative, not real client data. It shows how the decisions work, so don't read the page types as benchmarks. A content team at a B2B software company audits its SEO cluster on project management tools. The cluster has 18 URLs. After reviewing against the criteria, they reach these decisions:

• Keep: A strong comparison page that already ranks near the top and needs only small freshness updates to its screenshots.
• Merge: Three how-to articles with overlapping angles, combined into one definitive guide, with the other two redirected to it.
• Update: A landing page with healthy traffic but a low intent score, because it targets the wrong funnel stage and needs a new angle.
• Remove or redirect: Four old pages with no traffic, no backlinks and no strategic role.
• Fix the structure: No clear internal path exists from the informational content to the product trial page, so internal links are added.

Publishing more content isn't the next move. Merging the overlapping how-tos, fixing the intent-mismatched landing page, retiring the zero-value pages and building internal links toward the trial page will do more than adding four new articles.

Common mistakes in content audits

The process is straightforward, but teams still make the same mistakes.

Turning the audit into a spreadsheet only

Data matters, but skipping the actual reading means you miss weak explanations, bad structure, outdated examples and overlap that's obvious when you look at the page. Numbers tell you where to look. They don't tell you what's wrong.

Using too many statuses

Complicated action labels make the backlog hard to use. Keep it tight enough that editors, SEOs and stakeholders interpret it the same way. Five actions (keep, update, merge, redirect, remove) is usually the right level. When teams can't agree on what an action means, it's useless.

Ignoring business context

Some pages matter because they support product education or sales conversations, not because they get the most search traffic. Track only visits and you'll miss those pages and underinvest in content that drives real business value.

Creating new pages before fixing weak ones

Teams often spot a weak page on a topic, then create a second URL on the same topic instead of improving what's already there. That's an expensive mistake. Two competing pages accelerate cannibalization and split link equity instead of concentrating it.

Forgetting internal links and cluster logic

A page may be decent on its own and still perform poorly. Sitting inside a broken cluster with weak supporting links and unclear topic ownership's often what drives the underperformance. Pairing the audit with one of the better internal linking tools makes cluster structure problems easier to spot.

Content audit vs content gap analysis

They're related tasks, not the same task.

A content audit reviews what you already have and decides what to do with each existing page. The output's a decision for each URL.

A content gap analysis identifies topics your competitors cover that you don't. The output's a list of topics to create, not a verdict on existing pages.

Both work best together, and that's the order that saves effort. Auditing the current library first shows you what's already there. Running a gap analysis afterwards reveals what's still missing. Skipping the audit and going straight to gap analysis often leads to creating content that duplicates what you already have.

How often should you run a content audit?

Run a full content audit at least once a year, and every three to six months if you publish a lot or work in a fast-changing market. Small sites that publish rarely can get by with the annual review, and that's fine. Larger sites usually split the work into quarterly cluster reviews or a rolling schedule instead of one big project.

• Monthly checks for high-value or volatile pages (pricing, product features, competitive comparisons)
• Quarterly reviews for important clusters
• A full review once or twice a year
• Event-driven reviews when products, messaging or markets change

Some situations call for an immediate review regardless of cadence: a major Google algorithm update, a product rebrand, a new market expansion or a noticeable drop in organic traffic. Waiting for the quarterly cycle when traffic's already dropped isn't a viable plan.

FAQ about content audits

What does a content audit do?

A content audit evaluates your existing pages against set criteria and assigns each one an action: keep, update, merge, redirect or remove. The result's a prioritized backlog that shows which pages to fix first and which to retire.

What is the main goal of a content audit?

The main goal is deciding what to improve in your existing library so the site stays useful, current and aligned with where the business is going. The output's a prioritized action for each page in scope, not a document nobody acts on.

How do you carry out a content audit?

To carry out a content audit, define the goal and scope, build a page inventory, set review criteria, review each page by hand, assign an action to each URL, prioritize the backlog and measure the results. The sections above walk through each step.

How long does a content audit take?

A content audit takes anywhere from a day or two to several weeks, depending mostly on scope. A small cluster review of 20 to 30 pages can happen in a day or two. A full-site audit can take much longer, especially for a first run. Tight scoping matters: the goal is decisions, not a document nobody revisits.

Is a content audit only for SEO?

No, a content audit isn't only for SEO. Content audits also improve brand clarity, conversion support, product education and editorial consistency across the whole site. Many of the most valuable findings have nothing to do with rankings.

What is the difference between a content audit and a site audit?

A site audit focuses on technical issues like crawlability, broken links or indexation. A content audit focuses on the usefulness, freshness, intent fit and strategic value of the content itself. A page can be technically clean and still be the wrong answer for the query. Most teams need both.

What is the difference between a content inventory and a content audit?

A content inventory's the raw list, while a content audit is the judgment layered on top of it. The inventory catalogs what exists; the audit decides what to keep, fix or remove. You can't run a meaningful audit without an inventory to work from first.