A content audit should end in page decisions.

Two articles can each have traffic, links and a successful status code while competing for the same query and repeating the same answer. Reviewed one row at a time, both look healthy. Reviewed together, neither has clear ownership. That is the difference between an inventory and a content audit.

The audit has to decide what each page is for, whether the job deserves a page, which URL owns it and what should happen next. A crawl export can supply observations. It cannot make those judgments.

Start with the conflict, not the score

Group pages that could plausibly answer the same reader question. Search Console page-and-query data can expose shared impressions, but its tables omit anonymised queries and retain only a limited set of rows. Site search, navigation, sales questions and the pages themselves can reveal overlap the export misses.

Now state the intended job of every URL in one sentence. “Informational” is not a job. “Help a buyer choose between a fixed-rate and variable-rate mortgage” is. If the same sentence fits two URLs, either one page should own the job or the distinction needs stronger evidence.

Do not treat absent traffic or indexation as an automatic removal instruction. If the business serves the demand, the job is distinct and the page can provide a useful answer, failure to rank is a result to diagnose. The decision changes only when the underlying page case changes.

Use one worksheet for evidence, judgment and delivery

The columns deliberately keep observations beside the judgment they inform. Do not fill a cell because the template has one. Record only evidence that could change the action.

Copy the real template

Copy this tab-separated header row into the first cell of a blank spreadsheet.

URL	Page job	Demand and value	Search state	Business result	Substance	Overlap	Ownership signals	Constraint	Action	Destination	Implementation	Owner and check

Assign an action only after naming the constraint

“Needs SEO” is not a constraint. “Google selects the category page as canonical,” “the article lacks evidence for its central comparison,” and “three pages divide the same query set” are constraints that can change an implementation.

• Keep: the page has a necessary distinct job and currently performs it well enough.
• Improve: the job remains valid and the named constraint can be fixed on this URL.
• Merge: another page shares the job and one combined answer would serve it better. Name the surviving owner before moving anything.
• Redirect: a surviving page genuinely takes over the removed URL's job. A redirect is an implementation consequence of that decision, not a synonym for removal.
• 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.

Page ownership has to survive the implementation

A merge can be the right editorial decision and still be shipped badly. Improve the surviving target first. Move any unique evidence. Update contextual links, navigation and other inbound anchors so they define that page accurately. Then redirect only the sources whose job the target genuinely inherits, remove obsolete URLs from the sitemap and verify the public result.

Title, H1 and internal anchors work together. A spreadsheet can declare one owner while the live site keeps linking to three pages with the same language. The audit is not implemented until the visible and crawlable structure agrees with the decision.

The same applies to a technical finding. Sending engineering into Core Web Vitals work on a page that should be merged solves the wrong dependency first. Settle the route and its job before investing in a template that may disappear.

Verify the reason for the action

After release, crawl the affected URLs, follow every redirect, inspect selected canonicals and confirm links and sitemaps point to the surviving pages. Then observe the result at the same scope as the decision.

A merge intended to consolidate overlapping query sets should be reviewed against the surviving URL and those queries. An update intended to improve conversion should be reviewed against qualified actions, not only impressions. A new page created to close a real gap should be checked for discovery, indexation and selection before its commercial sample is judged.