A content audit is a structured review of existing content to assess how well it meets its purpose and decide what needs to change.
What does a content audit do?
A content audit helps you decide whether your website gives its intended readers the information they need. You review existing pages against a defined purpose, record the evidence and recommend changes. The result might be an update to an inaccurate guide, a clearer product explanation or a decision to keep a useful support page.
An inventory records what exists. An audit evaluates it. Texas A&M University's content inventory and audit guidance makes this distinction: collecting page details is the starting point for judging whether the content is effective. A list of URLs alone doesn't explain what your team should do next.
The scope can include articles, service descriptions, product pages, help content and downloadable files. You can review a selected part of a website if you record that boundary. Findings from a small sample don't establish the condition of every page.
When is a content audit useful?
Review content when you need evidence for a publishing decision. Before a redesign, that might mean checking which information must survive a move. After a service changes, it might mean finding pages that still describe the old offer.
You can also start with a recurring problem. If people keep asking a question that your help centre should answer, review the relevant pages and the route to them. The issue might involve missing information, unclear wording or a link that people can't find. Agree the question before choosing the checks.
Set the scope and build an inventory
Write a short brief that names the audience, the decision the audit will support and the content included. For example: review the public delivery and returns guidance so customers can find the current conditions before placing an order. Record any exclusions, such as account pages or translated versions awaiting a separate review.
Use a CMS export or an authorised crawl to create an initial list, then check it against the content people use. Include relevant PDFs and pages that aren't linked from the main navigation. For a sampled review, state how you selected the pages and which templates or topics they represent.
GOV.UK's existing-content guidance describes how page records can support an audit, including titles, URLs, content types and update dates. For your own review, add the person responsible for resolving questions. The fields below are a practical starting point; adjust them to your purpose.
- Page URL and title, plus the content format where it matters.
- Intended audience, task and the role of the page.
- Content owner and any subject specialist needed to check accuracy.
- Publication or review date, with the source of that date.
- Relevant observations and performance data, including the period measured.
- Recommended action, priority, responsible person and a check for completion.
Choose checks that match the page's purpose
Read the page in the context of the task it should support. A delivery policy needs accurate conditions and an understandable deadline. A product page needs enough information to evaluate the product. Applying the same word count or keyword target to both would miss those differences.
A first pass can flag redundant, outdated or trivial content, often shortened to ROT. In her 2009 content analysis guide, Colleen Jones explains why those checks are only a starting point: content can pass them and still be unclear or unsuitable for its audience. Select the review criteria that matter to your project.
Google's people-first content guidance provides useful questions about completeness, sourcing and authorship. Use those questions alongside your own audience needs and specialist checks. The review should explain the specific issue on the page, with an excerpt, a location or another observation that someone else can examine.
| Area | Question | Useful evidence |
|---|---|---|
| Purpose | Can the intended reader complete the task this page supports? | The task, the information it requires and the relevant page content. |
| Accuracy | Are the details current and consistent with the responsible team's information? | A confirmed policy, product record or named subject specialist. |
| Clarity and trust | Are important conditions understandable, with an identifiable source or owner? | The wording, headings, linked sources and authorship where relevant. |
| Access and usability | Can people find and use the required information through the routes being assessed? | The tested route, broken links or controls, and any content that is missing under those conditions. |
This is a suggested review framework. It isn't a Google scoring system or a complete accessibility assessment.
Use performance data to guide the investigation
Search Console reports impressions, clicks and click-through rate, with views and filters that help you investigate pages and queries. If a relevant query has impressions but few clicks, examine the results and whether your title and description match what the searcher needs. Google's Search Console guidance describes this as an investigation with several possible influences on a click.
Keep the date range and comparison conditions with your notes. A seasonal page, a recently published guide and an established support article serve different purposes. Low organic traffic alone is an insufficient reason to remove a page that existing customers use through your product or help centre.
Google Analytics defines engagement rate using session conditions, including time, key events and page or screen views. That metric doesn't directly tell you whether a visitor's question was answered. Check that measurement is working, consider the page's purpose and read the content before deciding on an action.
Turn findings into decisions your team can carry out
Separate the observation from the recommendation. An observation might be that a public guide states a deadline that the service owner has confirmed is obsolete. The recommendation names the information to correct, who will approve it and how the updated page will be checked.
Prioritise findings by their impact on the task, the reach of the problem and the strength of the evidence. Include dependencies and effort so the owner can plan the work. A misleading condition on a widely used service page may need attention before a stylistic improvement to an older article.
Record a reason for each decision. Google advises against changing dates without a substantive change or removing older content merely to make a site appear fresh. Age can prompt a review; it doesn't establish that the page has lost its value.
| Decision | When it may fit | Record before acting |
|---|---|---|
| Keep | The page remains useful and the reviewed information is accurate. | Why it should remain and who will review it when circumstances change. |
| Update or improve | The purpose is still valid, with outdated details or an identifiable content problem. | The affected passage, the proposed change and how to verify it. |
| Consolidate | Several pages address the same need and their overlap causes a documented problem. | The distinct information to preserve and a plan for the URLs and links affected. |
| Retire | The content no longer serves a current need, subject to retention requirements. | Any useful information to preserve, required approvals and what users of the old URL should receive. |
Choose the response to a retired URL with the person responsible for the website. A suitable replacement, an archive and a page that has been removed have different purposes.
An illustrative content audit example
Consider a fictional retailer's delivery guide. It says orders placed before 4pm qualify for next-working-day delivery. In this scenario, the operations owner confirms that the current cut-off is 2pm. The audit concerns that public guide and its ordering information.
The record below shows how an observation becomes a change someone can verify.
| Field | Example entry |
|---|---|
| Page and task | /delivery. Help a customer understand the delivery deadline before ordering. |
| Observation | The guide says 4pm; the operations owner has confirmed a current cut-off of 2pm in this scenario. |
| Potential effect | A customer could place an order after the valid cut-off expecting next-working-day delivery. |
| Recommended action | Confirm the full delivery conditions, correct the deadline and check other pages that repeat it. |
| Owner and priority | Content owner, with operations approval. Address before the next delivery promotion. |
| Verification | Read the updated guide and every page that repeats the deadline. Confirm that the approved cut-off and delivery conditions agree. |
How do SEO and AI content access fit into an audit?
An SEO-focused content audit can examine search queries, page purpose and whether the content answers the intended question. A content-access review asks what a tested client actually receives. The same service description can look complete in a person's browser while an HTTP response contains only a page shell.
AI applications can use different access methods. Some retrieve HTML or extracted text; browser tools may inspect rendered content, page hierarchy or controls. Record the method used and the information available through it. A review of text delivery alone doesn't establish that a page is accessible to people with disabilities.
Google's guidance for AI features says established SEO practices remain relevant for AI Overviews and AI Mode, with no additional technical requirements or special AI markup. That guidance concerns Google's features. Successful retrieval alone doesn't establish indexing, citations or visibility in an AI service.
Tityra provides website content audits for better Agent Experience (AX). Within the assessed scope, documented findings identify content access, delivery, structure and context issues, with affected pages, supporting evidence and practical recommendations. The Tityra audit methodology explains the checks and their limits. Combine those findings with your own editorial review and performance data when your audit includes those questions.
How often should you review content?
Set review dates according to how quickly information changes and the consequences of getting it wrong. A temporary offer needs a review linked to its expiry. A product explanation needs attention when the product changes. An evergreen help article may need a different schedule.
Fred Leise's 2007 content analysis heuristics describe a maintenance plan with review owners, events that trigger a review and a way to suggest one. GOV.UK advises monitoring whether content remains useful and findable. After making a change, verify the published content and record any later outcome measurements separately.
A checklist for your first content audit
Start with a scope small enough for someone to review the pages and carry out the resulting work. Use these checks to prepare the brief and decide whether the audit record is ready for a handover.
- The audience, purpose and decision the audit will support are written down.
- Included pages and formats are listed, with exclusions and sampling limits.
- Each page has an identifiable owner and a stated task.
- Observations identify the affected content and the evidence behind the finding.
- Performance data includes its source, date range and relevant measurement limits.
- Recommendations have a reason, a priority and someone responsible for the next action.
- Changes that need specialist approval or a URL plan are identified.
- The team can verify each completed change and knows when the content should be reviewed again.
Sources and further reading
- Colleen Jones, UXmatters: Content Analysis: A Practical Approach (2009)
- Fred Leise, Boxes and Arrows: Content Analysis Heuristics (2007)
- Texas A&M University: Content Inventory and Content Audit
- GOV.UK: Manage existing GOV.UK content
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Console: How are you performing on Google?
- Google Analytics: Engagement rate and bounce rate
- Google Search Central: AI features and your website


