# Content Audit

A content audit evaluates existing material against user needs and quality criteria to decide what to retain, improve, combine, or retire.

- Type: method
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/content-audit/>)

## What it means

A content audit is a structured assessment of a defined content collection. An inventory lists what exists, such as URLs, owners, and formats; the audit adds judgments about accuracy, relevance, duplication, findability, and usefulness. It produces decisions and work priorities rather than just a spreadsheet of pages.

## Why it matters

Content accumulates across teams and channels, leaving conflicting instructions and maintenance costs. An audit provides evidence for reducing duplication and directing editorial effort toward material that affects important tasks.

## When to use it

Use it before migrations, navigation redesigns, major policy changes, or maintenance programs. Scope it to a useful decision and sample explicitly if a complete audit is impractical. Do not treat low traffic alone as a reason to remove essential guidance.

## How it works

1. Define the collection, decision, evaluation criteria, and responsible reviewers.
2. Build an inventory including content outside the main publishing system where relevant.
3. Assess samples or all items using evidence, subject expertise, and user needs.
4. Assign retain, revise, merge, or retire decisions with owners and reasons.
5. Implement priorities and verify links, redirects, and task outcomes after changes.

## A practical example

A subscription service audits cancellation guidance across help pages and transactional emails. Three versions describe different steps. The team keeps one canonical guide, updates the emails, and checks that old links lead users to the current instructions.

## Where it breaks

Large audits can become stale before actions are completed. Analytics show only part of usefulness, and reviewers may disagree without shared criteria. Removing content also requires attention to dependencies and any applicable retention obligations.

## Common mistakes

- Calling a URL export a finished audit.
- Scoring content without assigning follow-up ownership.
- Deleting low-traffic pages without checking their role in critical tasks.

## Sources

1. [Content Inventory and Auditing 101](<https://www.nngroup.com/articles/content-audits/>) — Nielsen Norman Group · Research-based guidance
2. [Manage existing GOV.UK content](<https://guidance.publishing.service.gov.uk/writing-to-gov-uk-standards/plan-manage-content/manage-existing-govuk-content/>) — Government Digital Service · Government guidance

## Related topics

- [Content Design](<https://wiki.soroush.uk/topic/content-design/>)
- [Information Architecture](<https://wiki.soroush.uk/topic/information-architecture/>)
- [UX Audit](<https://wiki.soroush.uk/topic/ux-audit/>)
