An SEO Content Audit Spreadsheet: Keep, Improve, Merge or Remove

TL;DR

• Inventory public URLs and their purpose before assigning keep, improve, merge or remove decisions.
• Combine content quality, audience relevance, technical status and performance evidence in the same worksheet.
• Give each action an owner, reason and verification step so the audit becomes executable work.
• Avoid deleting pages solely because a metric is low or unavailable; investigate their role and value first.

Define the audit's decision

A content audit can answer several different questions: which pages are outdated, which topics overlap, which articles support useful outcomes or which public pages no longer belong on the site.

Choose the main decision before gathering data. Otherwise, it is easy to build a large spreadsheet that combines unrelated metrics without helping anyone decide what to do.

For a growing blog, a useful starting objective is to identify pages that should remain, be improved, be consolidated or be intentionally removed. The template below is designed around that objective.

Build the inventory from public content

Collect the URLs from the website, sitemap and publishing system. Compare the lists so the audit does not silently omit older pages or include drafts that are not public.

Record the exact public URL and a stable content identifier when available. The URL tells you where the page is served; the identifier helps track it if the slug changes later.

For each page, read enough of the content to state its purpose in one sentence. A title alone may not reveal what the page actually explains or whether it still matches the product.

Use these worksheet columns

Add columns only when they support the audit's decision. A dozen unused scores can make the important findings harder to see.

Keep missing data distinct from poor performance

An unavailable metric is not the same as zero. Record the source, date range and scope for performance data, and mark gaps explicitly.

For a newly published article, limited data may simply mean that there has not been enough observation time. A low-traffic support page may still solve an important problem for existing customers. A high-traffic article may attract an audience unrelated to the product.

Use metrics as evidence within the page's role. Do not let a single number decide the outcome without reading the content and understanding why it exists.

Apply the four decisions carefully

Keep a page when it remains accurate, useful and appropriately connected to the site. Keeping it can still include routine maintenance, but it does not require a rewrite merely to show activity.

Improve a page when a specific repair can strengthen its answer. Merge pages when their purposes overlap and one destination can preserve the useful material. Remove content when there is a clear reason it should no longer be public and the consequences have been reviewed.

The keyword overlap guide helps distinguish a justified merge from a situation where separate pages simply need clearer scope.

Turn findings into bounded tasks

“Improve quality” is too vague to assign. “Replace the outdated setup screenshots, verify the current error messages and add the missing recovery step” is a task an editor can complete and a reviewer can check.

For a merge, name the destination and list the material to preserve. For a removal, identify relevant incoming links and decide whether a suitable replacement exists. For a technical issue, record a reproducible example and the expected result.

Use the old-post update workflow when the decision is to revise an existing article. Keep the original URL stable unless a change is necessary.

Prioritize by consequence and effort

Fix inaccurate or broken instructions that affect important user tasks before polishing an already useful introduction. Consider audience impact, business relevance, confidence in the finding and the effort required.

Group shared issues when appropriate. If one renderer drops tables across 30 articles, a component fix may be more valuable than editing 30 documents independently.

Limit the active work to what the team can review and publish properly. An audit backlog is useful only when its highest-priority findings become completed changes.

Close each task with public evidence

After publication or deployment, open the affected URL and verify the intended result. Check content, metadata, links and images as relevant to the task. Record the final version or release reference.

Then schedule a later review only when there is a question that needs more time or data. Avoid repeatedly auditing the same page without acting on known findings.

RankWin's content calendar can help connect audit decisions with editing and publication. The worksheet's most important output is a justified action with a verified result, not the number of rows it contains.