Study first
Review the ideas behind the questions
Review what a content audit should capture before cleanup decisions start. Focus on listing real content, naming ownership, and checking whether pages still support user tasks.
List what exists first
A useful audit starts with an inventory. The team needs a clear list before it can decide what to revise, merge, keep, or remove.
- A content audit lists and analyzes the content on an existing website or app.
- Inventory details should include the navigation title, page title, URL, and parent page.
- Repeated content types, such as blog posts, may be sampled when a full item-by-item review is not practical.
In Practice
Start with concrete fields
A spreadsheet with page title, navigation title, URL, and parent page gives reviewers enough structure to spot duplicate paths and unclear sections.
Use samples carefully
Sampling can help with repeated formats, but the sample should still show the pattern the team needs to review.
Common mistakes
Starting with opinions about which pages feel old before making a content list.
Create the inventory first so cleanup decisions are based on the pages, files, and other content that actually exist.
Q&A
Does a content audit only cover web pages?
No. It can include pages, files, videos, audio, and other data on an existing website or app.
Why capture both navigation title and page title?
Those fields help reviewers compare how a page is labeled in navigation with what the page itself says.
Connect pages to tasks
After the list exists, the audit should look at how users reach content and whether each item helps them complete a task.
- Content audits can identify who is responsible for content, how often it should be updated, and what role it plays for users.
- Trace pages from real entry points through the task a user is trying to complete.
- User needs should be based on research evidence, not internal assumptions.
In Practice
Add owners before assigning fixes
A page without a named owner is harder to verify, update, or retire because no one is clearly responsible for its credibility.
Look beyond the homepage
Users may arrive from marketing, search, a microsite, or another page, so the audit should follow the actual paths people use.
Common mistakes
Treating every stakeholder request as a proven user need.
Mark internal opinions as assumptions until user research or other user evidence supports them.
Q&A
What should the audit do after listing the pages?
It should evaluate gaps, redundant or outdated content, and content that does not support the team's goals.
When does continuous content improvement matter?
It matters throughout the life of a service because user needs, technology, policy, and behavior can change.
Turn findings into cleanup work
The audit should end with clear findings, not just a list. Use the inventory and site map to name gaps, duplicated pages, outdated content, and improvement work.
- A site map shows how pages are organized, especially their hierarchy.
- When evaluating an existing site map, focus on logical page relationships more than the old URL structure.
- Continuous improvement helps content respond as user needs, technology, policy, or behavior changes.
In Practice
Use hierarchy to find misplaced pages
A page may have the right information but sit under the wrong parent topic. Site mapping helps the team see that issue before rewriting copy.
Separate findings from fixes
Name the gap, duplicate, or outdated content first. A clear finding makes later fixes easier to assign and review.
Common mistakes
Treating the audit as a one-time list with no future maintenance path.
Use the findings to plan updates and keep improving content as user needs and behavior change.
Q&A
Should an audit finding jump straight to a rewrite task?
Not always. First name the issue, such as a gap, duplicate page, outdated content, or weak fit with goals.