A content audit should end in page decisions.

Most content audit spreadsheets are excellent at proving that pages exist. They collect word count, status code, title length, traffic, backlinks, and a vague quality score. Then somebody colours the rows and the site remains unchanged. The same mistake can send engineering into Core Web Vitals work on a page the audit should merge or remove.

The missing field is the page's job. Without it, low traffic can condemn a necessary policy page, high traffic can protect irrelevant visits, and two pages serving the same intent can both look healthy in isolation. Resolving that overlap makes gaps in topical authority planning real gaps rather than spaces between duplicate owners.

The minimum worksheet

Copy into a spreadsheet

Copy the tab-separated header row below and paste it into the first cell of a blank sheet.

URL	Page job	Demand evidence	Current evidence	Substance	Overlap	Constraint	Action	Destination	Owner and check

Collect evidence before assigning actions

Export the canonical URL inventory from the site and crawl. Join it to Search Console page and query data, analytics or conversion data, known backlinks, sitemap membership, and index status. Search Console's Performance report can group by page and show the queries for which Google displayed it, but its tables omit anonymised and some lower-volume rows. Treat the export as evidence, not a complete demand map.

Then inspect the page itself and its neighbours. A crawler cannot tell you whether an explanation contains original evidence, whether a product comparison is fair, or whether three URLs answer the same reader question. Those decisions require reading.

Use actions with strict meanings

• Keep: the page has a necessary distinct job and currently performs it well enough.
• Improve: the job remains valid, but a named constraint can be fixed on this URL.
• Merge: another page shares the same job and one combined answer would serve it better.
• Redirect: a surviving page genuinely takes over the removed URL's job. Redirect after moving any useful substance and links.
• Remove: the page has no necessary job or truthful replacement. Return a real 404 or 410 rather than a soft redirect to the homepage.
• Investigate: a material fact is missing. Name the fact and the person or system that can resolve it.

Decide in clusters, implement in dependencies

Review overlapping pages together so each job has one owner. Then sequence implementation: create or improve the surviving target, update internal links, add the redirect if a genuine replacement exists, remove the obsolete source, update sitemaps, and verify the resulting status and canonical.

Verify the decision, not merely the edit

After implementation, crawl the affected set, test redirect targets, inspect representative URLs, and confirm internal links and sitemaps point at the surviving pages. Later, review query and page performance against the reason for the action. A merge intended to consolidate overlapping queries is assessed differently from an update intended to improve conversion.