A list of URLs is an inventory, not a content audit. The audit begins when each important page is connected to an audience, question, evidence, owner and intended action. The result should be an executable decision list for editorial, SEO and development teams, not a report of every possible flaw.
Bound the inventory
Start with public, indexable routes from the sitemap and navigation. Add important campaign pages, forms and pages that receive visits or enquiries. Include hidden or historical content only when there is a specific management or migration question.
Fetch only the fields needed for assessment: URL, status, canonical, title, page type, language, owner, modification date and a small set of usage signals. Loading full text, revisions and every database column makes the first pass slower and more expensive without automatically improving the decision.
Group pages before assessing them
Divide the inventory by page type, topic, language and place in the user journey. Compare service pages with service pages and articles with articles. This reveals recurring template defects, missing topics and several pages trying to perform the same job.
Review representative examples in each group, then inspect the exceptions. On a large platform, this is more efficient than reading every page in equal depth from the start. Critical legal, financial or safety information still needs a separate content review by a qualified person.
Assess each page by its purpose
Ask what task the page performs. Does it answer a real question, help someone choose, support a transaction or explain a policy? Check whether the title and introduction make that task clear, whether claims can be demonstrated and whether the next step makes sense.
Record freshness, overlap, internal links, language versions and ownership. A well-written page without an owner becomes stale. A current page with no internal route remains hard to find. A translation with different conditions can be risky even when both versions read fluently.
Choose one concrete action
Use a small decision model: keep, improve, consolidate, redirect or remove. 'Review later' is valid only with an owner and date. Attach the reason, priority, responsible person and post-publication check to every action.
Consolidation means more than copying text. Select the destination URL, preserve unique information, update internal links and plan a redirect from the old route. Removal needs the same check across links, sitemap, canonical and possible 404 signals.
Prioritize value, risk and effort
Start with pages that serve an important business or user function and where the current content blocks that function. High risk may matter more than high traffic, especially for stale policy or an incorrect claim. Group shared template defects so one technical change improves several pages.
Estimate effort broadly and identify dependencies. A text correction may be immediate, while consolidation can affect redirects, navigation and translations. The priority list must be executable by the available team, not merely complete in theory.
Verify the effect after publication
Check status codes, canonicals, sitemap, internal links and forms after each batch. Confirm that intended routes still receive visits and enquiries and watch for new 404s. Record the result beside the original decision. The next audit then updates known choices instead of rebuilding a spreadsheet from zero.
Make the decision visible in one row
A useful audit row contains the URL, page job, evidence, risk, decision, owner and verification point. For example, two guides answer the same question; the older one still has relevant links and the newer one contains current conditions. The decision may be to merge unique information into the stronger route, update old internal links and redirect the other URL. Record who will verify the status code, canonical and content.
An action is complete only when the destination page is live and redirects, canonicals, sitemap, navigation, language versions and critical forms have been tested. Missing analytics data does not automatically make a page worthless: new, niche or required policy pages need qualitative review. Record that uncertainty instead of turning an empty metric into a removal recommendation.