A content audit earns its time when your team knows what to do with each page: keep, correct, expand, combine or retire. ROI.LIVE starts with the question the page should answer, then checks whether its evidence and practical detail still do that work. Use traffic to set priorities, while checking the truth of a claim against its source.
Some of the pages that need attention may have no impressions and never appear in a Search Console performance export. An editorial audit needs to find those too. Keeping it separate from an index report helps you avoid leaving old customer-facing material out of the job.
Build the inventory from more than one source
Export published URLs from the content management system and compare them with the XML sitemap and a site crawl. Add landing pages and static files served outside the CMS. Normalize redirects and canonical URLs without discarding the original address. Search Console's indexing and performance reports supply different context; a performance export alone is not a complete list of published or indexed pages.
Use one row per intended canonical page. Record status code, title, page type, business purpose, primary question, last substantial update and current owner. Keep draft and future URLs in a separate publication column so they cannot masquerade as live internal-link destinations.
Editable resource
Use the worksheet
The CSV opens in Excel, Google Sheets or another spreadsheet editor. It contains labeled fields; sample data, where included, is illustrative.
Download the editable worksheet (CSV)
Preview the fields
- Canonical URL
- Original URL
- Page type
- Primary question
- Reader
- HTTP status
- Indexing evidence
- Evidence checked
- Action
- Exact repair
- Owner
- Before version
- After version
- Public verification date
- Status
Choose a pilot before estimating the whole job
Before putting a price or deadline on the full inventory, review a small mixed sample: a key service page, an old article, a page with falling demand and one with no recorded impressions. Time the source checks and technical review as well as the reading. Use that completed work to estimate the rest.
Time the review before quoting the inventory
Read the full explanation
For illustration, thirty pages at forty minutes each require twenty hours of reading and annotation. Fifty pages at forty-five minutes require 37.5 hours. Editing, design and deployment are additional work. A short triage can identify obvious problems faster, but it must not be reported as a full source audit.
Read for the decision and the proof
Write down what the reader should be able to decide after using the page. Then compare it with current alternatives and primary sources. Check dates, prices, product specifications, client results and claims about platform behavior, including those in charts and FAQs. A polished page can still give a customer the wrong answer.
Use the editorial scoring rubric to record where the page contributes something useful. Then separate gaps that need research from gaps that need editing. A writer can shorten a repeated introduction without an interview. A claim about an unnamed client test needs the actual record or removal.
Assign one of five actions
Choose the page's next action
| Action | Appropriate use | Evidence to keep |
|---|---|---|
| Keep | The page satisfies its purpose and passes checks | Review date and sources inspected |
| Correct | The purpose is sound but facts, links or calculations are wrong | Before and after passages plus corrected source |
| Expand | An important question is unanswered | The missing question and the evidence needed |
| Combine | Two pages serve the same reader task without useful distinction | Destination choice, unique material to preserve and redirect plan |
| Retire | The page has no continuing purpose and cannot be repaired economically | Traffic, links, business owner approval and handling of the old URL |
A quiet page may still be doing useful work. A support answer can reduce calls, and a seasonal page may be waiting for its selling window. Review that purpose before deleting it for low traffic. If the page has valuable incoming links, decide how to handle them before changing its address.
Fix the cluster while the pages are open
Map each article to its relevant parent and useful next questions. Link within the paragraph where the next question arises. A pillar can list its supporting guides, while each supporting guide should explain how to return to the broader subject. The topical authority guide shows how to avoid creating multiple pages for the same intent.
Check exact live URLs and fragments. Do not paste a planned slug into public copy before its destination exists. If two articles overlap, decide whether their purposes can be made distinct before choosing a redirect.
Close the audit with evidence
Close a repair by checking the page a customer will use. Save the revised source, issue-to-fix record and deployed URL. Read the public response, test mobile and desktop, open every FAQ and run each calculator with a known answer. Check that the layout change kept all the text.
Track a baseline before the edit and compare equivalent periods afterward. Search demand, seasonality, query mix and other site changes can affect results. Report those limitations with the outcome. The audit is complete when the assigned repairs are implemented and checked, not when every row has a reassuring color.
Questions owners ask
Can Search Console provide the entire content inventory?
A performance export omits URLs with no recorded impressions. Combine the CMS, sitemap, crawl and indexing information, including any static pages outside the CMS.
How long does a content audit take?
Time a representative pilot. At forty minutes per page, thirty pages require twenty hours before editing and deployment. A quick triage and a full source audit are different tasks.
Should every page with no traffic be deleted?
No. Review its support, seasonal, conversion and link value first. Decide how the old URL will be handled before removing a useful destination.
How do you prove a repair is complete?
Retain the original issue, corrected source and public read-back. Verify the page content, links, calculations and layout at the actual deployed URL.
Method
This guide presents ROI.LIVE’s editorial analysis and worked methods. Numerical examples are illustrative unless expressly identified otherwise. No ranking, citation or business outcome is guaranteed.
Substantively revised September 8, 2026. Definitions, calculations, sources and internal destinations were reviewed for this edition.
