What Is a Content Audit? How to Decide What to Keep, Update or Remove

A content audit is a review of existing content to determine whether it still serves its audience and what should happen to it next. It combines information about each page with evidence about accuracy, usefulness and performance, then turns the findings into decisions: keep, update, consolidate or remove.

A page with little search traffic might answer a support question that matters to paying customers. A popular page might contain an outdated instruction. Looking at visits alone would miss both problems.

A content inventory records the assets you have. A content audit evaluates them. Nielsen Norman Group makes this distinction in its guide to content inventories and audits: the inventory documents content, while the audit examines its quality and need for change.

Competitor keyword-gap research asks a different question: Which searches bring visibility to other sites that your site hasn't captured? That can suggest topics to investigate. It doesn't tell you whether your existing answer is inaccurate, difficult to use or already sufficient for readers.

Main question: What exists, where is it and who owns it?

Typical output: A page or asset register

Main question: Does this content still serve its purpose?

Typical output: A decision and an assigned action

Main question: Where do other sites have search visibility that we lack?

Typical output: Candidate queries and topics to investigate

An audit may reveal that an answer is missing even when the topic already has a page. What Is a Content Gap? How to Find Missing Answers provides the broader framework for recognizing those omissions.

Define the part of the site you're reviewing and why. "Audit the resource hub to identify outdated guidance and overlapping articles" is manageable. "Improve all content" leaves reviewers without a clear standard.

For a first audit, choose a topic cluster, a product journey or a set of important landing pages. Include connected downloads if readers need them to complete the task. An accurate article linked to an obsolete worksheet still creates a poor experience.

Decide which performance measures matter before collecting them. A research report, a support guide and a sales page have different jobs. Their review criteria should reflect those jobs.

Start with a content management system export, a crawl or a manually assembled list. Compare the sources where possible. A crawl may miss a page with no internal links, while a system export may include drafts or retired material.

Use one row per page or separately maintained asset. Record its URL, title, format, audience, purpose, owner and meaningful update date. Identify duplicates and alternate URL versions before merging performance data.

Keep the original URL even if you plan to consolidate the page. It will be needed to implement the decision and check the result.

Gather both performance evidence and evidence from reading the content. Google's Search Console documentation describes reports that show search performance by page and query, along with indexing information. Use those reports to understand discovery, then add relevant information from your analytics and operational records.

Record the reporting period, filters and data source. Compare similar periods where seasonality matters. Mark unavailable data as unavailable; an unmeasured conversion is different from a measured zero.

Actionable evidence includes:

Treat analytics as clues. Low traffic can reflect limited demand, weak discovery, a recent publication date or a technical issue. The audit should identify which explanation is supported before recommending a rewrite.

Use the same questions across similar pages:

Purpose: Does the page have a current audience and a clear job?
Completeness: Can the reader finish that job with the answer provided?
Accuracy: Are important claims and instructions still correct?
Evidence: Can the reader inspect the basis for important claims?
Usability: Are the explanation, structure and downloads easy to use?
Distinct role: Does this page provide something another page doesn't?
Performance: Is the evidence consistent with the page's intended job?

Write an observation beside each failed criterion. "Needs improvement" gives the next person another evaluation task. "The export instructions describe a menu removed from the current product" gives them a repair task.

Don't let an average score conceal a serious error. An incorrect pricing claim needs attention even if the rest of the page reads well.

Consider this fictional accounting software resource hub. The page observations and decisions below are invented to demonstrate the method; they aren't findings about a real site.

Evidence found during review: Current steps, distinct task and documented use by support staff

Decision: Keep

Assigned work: Assign a review date and retain support links

Evidence found during review: Relevant audience, but payment fees and export limits are missing

Decision: Update

Assigned work: Verify current documentation and add the missing decision fields

Evidence found during review: Both answer the same task; one has a clearer example

Decision: Consolidate

Assigned work: Combine the distinct material into the stronger guide and map the retired URL

Evidence found during review: Registration closed; no recording or continuing reference value identified

Decision: Remove

Assigned work: Confirm dependencies, retain any required internal record and implement the removal

The selection checklist stays because its job is still relevant and the defect is repairable. The recurring invoice articles need one coherent destination because their useful material belongs in the same answer.

The webinar decision needs an extra check. If the page contains an important public announcement, a linked recording or information still used by customers, archiving or repurposing may be more appropriate. Expired registration alone doesn't settle the fate of the whole page.

Keep a page when its purpose remains valid, its answer is accurate and no material repair is justified. Record the review rather than changing the visible update date to imply new content.

Update when the page has a useful role but needs a specific fix. List the missing answer, outdated evidence or usability problem. Name the owner and the condition for completion.

Consolidate when pages substantially serve the same task and their useful material can be combined. Check the query and audience differences first. Two pages mentioning the same subject may still answer different questions.

Remove when there is no continuing reader, business, historical or required recordkeeping reason to keep the public page. Document the reason and check links, downloads and dependencies before implementation.

For moved pages with a clear replacement, Google's crawling-error guidance recommends a permanent redirect. For content that is gone without a replacement, return an appropriate 404 or 410 response. A redirect should lead to a relevant answer rather than sending every retired page to the homepage.

Download the content audit worksheet. It includes a blank audit, the fictional worked example and instructions for recording evidence, decisions and implementation checks.

Use the decision field for the recommendation and the implementation status for progress. A recommendation to update isn't evidence that the update happened. Keep those fields separate so the audit record doesn't quietly become a list of unfinished work presented as completed maintenance.

After publishing updates, check the live answer, downloads and links. Test redirects or removal responses where relevant. Record the implementation date so later performance can be compared with the correct version.

Choose the follow-up period based on the page's traffic, seasonality and task. Avoid judging a small change from a handful of visits. The immediate check is whether the documented defect was fixed; the later check is whether the page performs its job better.

"Improve quality" is still a finding. "Replace the outdated export steps, verify them in the current interface and have support approve the revision" is something a team can finish.