An SEO content audit connects each existing page with its purpose, the evidence available about its performance and a proposed editorial decision. The useful output is a prioritised worklist: what to preserve, what to investigate and what a reviewed change should achieve.
Begin with existing URLs. An article with few clicks may still support a useful customer question, while a high-traffic article may bring an audience unrelated to the business. Neither observation alone establishes whether the content should be rewritten or removed.
Build an inventory that can support a decision
Combine the published CMS list, sitemap, navigation and crawl results where available. Keep the URL, title, content type, responsible owner, publication date and intended audience. Record pages discovered in only one source so they can be investigated.
Add status, indexability and canonical observations with their check dates. A crawler's failure to find a page is different from evidence that the page is unavailable. An inventory should preserve those distinctions rather than turn every empty field into a defect.
Join search and business evidence carefully
Use Google Search Console for clicks, impressions and query/page exposure. Use separately verified analytics or authorised business records for enquiries and qualified leads. Record the reporting window, country, device and whether recent data is final.
A page missing from a returned query table has unknown exposure in that extract; it is not automatically a zero-demand page. Query reporting can omit data, and page-level totals are not interchangeable with the sum of visible queries. Keep the raw evidence reference with the decision.
Read the page before assigning an action
Check the promised answer, the actual body, factual accuracy, sources, headings and relevant next steps. Ask whether a person with the intended problem can use the information. Compare the query intent with the page's purpose before interpreting a ranking.
Google's helpful-content guidance provides questions for evaluating usefulness and reliability. Apply them to the page itself. Adding a year, extra headings or more repetitions of a phrase is not evidence that the answer improved.
Use explicit decision categories
| Decision | Evidence to record | Next step |
|---|---|---|
| Keep | The answer is accurate and still serves its purpose | Preserve the URL and review on an appropriate schedule |
| Refresh | A specific factual, clarity or intent gap | Propose a bounded edit and its acceptance check |
| Investigate | Unclear indexing, measurement or query intent | Resolve the uncertainty before rewriting |
| Review consolidation | Substantial duplicated purpose and a defensible preferred destination | Assess links, content and migration impact before approval |
For a fictional software company, a mobile-platform guide might remain useful but lack a requirements checklist. That supports an addition and a relevant service link. It does not by itself justify replacing the entire guide. This is an illustrative decision, not a reported client result.
Prioritise commercial relevance and realistic opportunity
Consider buyer relevance, existing useful visibility, competition, demonstrated demand and the effort and risk of a change. Keep estimates separate from observed data. A third-party keyword volume is not an expected number of visits or enquiries.
Make exceptions explicit. A material factual correction may take priority even on a low-traffic page. Conversely, a broad definition attracting many unrelated searches may deserve less expansion than a service-supporting guide with a small but relevant audience.
Check overlap without assuming cannibalisation
Two pages can appear for the same phrase because they answer different parts of a question. Inspect the queries, content boundaries and intended destination. Shared impressions alone do not prove that one URL is harming the other.
Where the purpose is genuinely duplicated, compare useful sections, internal links and any verified external references. Keep consolidation as a reviewed proposal. Deletion, redirect and major canonical changes need an impact assessment and a separate release decision.
Prepare a reviewable refresh
Keep a before snapshot and the proposed fields. Retain a working URL and valid publication date, and document any change to heading anchors or navigation. If a substantive revision date is used, it should describe a real editorial change rather than an automatic CMS event.
Assign technical or subject review where the content needs it. A general technology author should not be presented as a legal, clinical or compliance specialist without verified qualifications and a real review. Test rendered links and metadata after an approved change.
Measure decisions after release
Maintain a change log with publication dates, affected URLs and the expected business benefit. Review comparable final periods and investigate changes in country, device or query mix. Avoid attributing every movement to one edit.
The SEO reporting guide explains how to present results and their limits. For a page set with unresolved rendering, crawl or indexing questions, scope technical SEO support around those questions before commissioning a large rewrite programme.
