What is a content audit?
A content audit is a structured review of existing content within a declared scope. It evaluates what each item is for, whether it is useful and accurate, and what should happen next. The inventory lists the assets; the audit adds findings, reasons and maintenance decisions.
Digital.gov's content designers describe choosing a scope, checking the inventory and reading pages alongside automated results. Their conversation offers a practical example of the work beyond collecting a spreadsheet.
Define the review before collecting rows
Start with a question such as “Does our workshop information still give participants the right instructions?” Identify the pages, documents or section included in that review, and record what is outside it. Choose evidence that can answer the question instead of adding every available metric to the sheet.
An inventory can miss content. Digital.gov's practitioners warn that analytics lists may omit pages without views and that sitemap coverage can be incomplete. Check which assets your chosen sources include before describing the list as complete.
Keep each item's URL or other identifier, title, format, purpose and responsible person with the record. Note where the item was found and when it was reviewed. If the owner is unknown, record that as an open question rather than assigning an invented approval.
Read the material and record a specific finding
Open the content in the context a reader uses it. Check whether the explanation answers its intended question, whether instructions match the current service and whether important claims have support. Record the sentence, section or interaction that needs attention so another person can find the same problem.
Google's people-first content guidance asks creators about original value, factual errors, the intended audience and whether readers can achieve their goal. These are evaluation questions, rather than a score that automatically decides a page's fate.
A fictional arts-centre review
Imagine an arts centre reviewing its workshop information. The fictional records below show why a confirmed error, an uncertain page purpose and shared terminology need different decisions. The reviewer keeps the proposed action separate from the evidence needed to accept it.
| Finding or open question | Proposed action | Check before closing the task |
|---|---|---|
| A workshop guide lists a session time that the programme owner says has changed. | Update the affected instructions using the confirmed programme record. | Read the published guide and linked booking information to confirm they give the intended instructions. |
| An old event page has no analytics export attached, and its continuing purpose is unconfirmed. | Investigate whether it still serves a reference need before proposing retirement. | Record the owner's answer and available evidence. Keep missing analytics distinct from a measured lack of visits. |
| Two pages use “printing workshop.” One explains booking; the other prepares attendees. | Read both against their separate tasks before considering a merger. | Confirm what each reader needs and whether the content actually duplicates the same answer. |
The first row gives a maintainer a concrete correction. The other rows leave decisions open because the record is incomplete or the apparent overlap needs interpretation. A useful audit can produce an investigation task as well as an approved edit.
Separate a recommendation from a verified change
For each accepted finding, state the reason, proposed change, owner and acceptance check. Mark whether the work is recommended, approved, implemented or verified. A suggested correction in a spreadsheet is not yet a correction on the published page.
If a proposal changes or retires a URL, plan the destination and delivery behavior separately. Check the content being preserved, internal links and useful old fragments before implementation. Afterward, test what the old and new URLs actually serve rather than closing the task when a redirect rule has merely been written.
Use metrics without turning them into verdicts
Keep the reporting period, filters and definition with a metric. An empty export field may mean data was not collected or supplied; label it accordingly. A page may support a necessary reference or task even when search traffic is not the right measure of its usefulness.
Google's guidance rejects writing to a supposed preferred word count. It also warns against adding or removing older content merely to make a site appear fresh for rankings. Examine the actual information and reader need before treating age, length or an audit score as an instruction to remove a page.
Choose the next kind of work from the finding
Content gap analysis asks what useful answers are missing and where they belong. A content audit examines the material already in scope. The work can connect: reading an existing guide may reveal an unanswered question that belongs in the same guide.
Hand over a checkable task
Give the maintainer the exact finding, supporting material and acceptance condition. Prioritize a confirmed error that misdirects a reader according to the effect it has, and make unresolved questions visible. Choose a review date or trigger around how the content changes and who can maintain it.
Save the reasons for decisions alongside the implemented changes. A later reviewer should be able to see why a page was kept or revised, which evidence was unavailable and what would prompt another review. Keep subsequent search or business results separate from proof that the intended edit was delivered.
Sources and scope
Digital.gov supplies the practitioner example; Google supplies its own content-evaluation guidance. The arts-centre records and decision worksheet are fictional editorial illustrations.
Explore this topic: Content Audit Template: Inventory, Score, and Fix Pages · How to Do a Content Audit: 8 Steps That Work (2026).