A content inventory is more than a list of addresses. It should help you decide which pages still serve a useful purpose, which need correction, and which overlap enough to confuse readers. Collect only the information needed for those decisions.

For a small website, you can begin with a simple note or table. This guide uses a fictional set of writing-tool guides. It does not assume that deleting pages improves search performance or that adding more pages guarantees traffic. The focus is the usefulness and accuracy of the existing material.

Record the job of each page

For every page, write its address, title, type, and intended reader task. “Blog article” identifies a format, not a purpose. “Help readers check whether a downloaded note is complete” explains why the page exists.

If you cannot describe the task clearly, inspect the page before deciding what to do with it. The purpose may be hidden in a broad introduction, or the page may combine several tasks. Do not infer usefulness solely from the title or word count.

Capture current evidence

Record the date of review and the specific issues observed. A broken internal link, outdated button label, missing example, or unsupported claim is actionable evidence. “Feels old” is a reaction that needs a more precise explanation.

If you have analytics or search data, keep the source and reporting period attached. A page with little recent traffic may still support an important user task. An inventory should inform judgment, not turn one metric into an automatic deletion rule.

Identify overlap at the task level

Two pages can share vocabulary while solving different problems. A guide to exporting notes and a guide to verifying the exported file are related, but they may have distinct purposes. Compare the reader task, examples, and outcome before calling them duplicates.

Conversely, pages with different titles may repeat the same general advice. Note the overlap and decide whether clearer scope, internal links, or a combined page would better serve readers. Avoid merging useful differences simply to reduce the number of URLs.

A fictional inventory row

Page: Guide to checking a text export.
Purpose: Confirm that the downloaded copy is complete.
Observed issue: The current example has no distinctive final line.
Related page: Guide to choosing an export format.
Overlap: Shared introduction, different completion checks.
Decision: Revise the example; keep separate purpose.
Owner: Content editor.
Next check: Open the revised sample and inspect the final line.
Review date: After the example is updated.

This row leads to work someone can perform. It does not require a broad rewrite of a page whose main task remains useful.

Choose a decision with a reason

Useful decisions include maintain, revise, merge, and retire. Maintain means the page currently serves its purpose with no identified change required. Revise should name the issue and intended result. Merge requires a plan for preserving useful material and handling existing links.

Retirement should consider who still uses the page and what happens to its address. Do not remove a public page casually when it is linked from tools, emails, or other guides. Use your site's normal redirect and recovery process where appropriate.

Prioritize by consequence and effort

Fix a misleading instruction or broken essential link before polishing a harmless sentence. Group related changes when the same check can verify them. Avoid turning every observation into an urgent project.

For uncertain issues, assign an investigation rather than a rewrite. “Check whether the current tool still offers this option” is a useful task. Replacing the article before checking the tool can create new inaccuracies and waste work that a small correction would have solved.

Keep the inventory connected to implementation

Move approved changes into the team's work system and retain a link in the inventory. After editing, record the result of the relevant check. A status such as updated should mean more than a file was saved.

Preserve a reversible copy before substantial changes. If a merger or retirement affects addresses, verify the intended destination and update relevant internal links. The inventory should help prevent broken journeys rather than focus only on text quality.

Review after meaningful change

A page may need another review when its tool changes, a source is updated, or readers report confusion. A calendar date can prompt a check, but it is not a reason to change a publication date without a substantive edit.

The inventory is successful when it produces clear maintenance decisions and the decisions are verified. It does not need dozens of columns. A purpose, specific evidence, an owner, and a useful next check often provide enough structure to improve a small site responsibly.

For an initial pass, review one representative page of each type before expanding the inventory. A tool page and an article may need different evidence. The tool needs a functional sample; the article needs a clear explanation and supported claims. Keeping those checks distinct prevents a single generic quality label from concealing the specific work each page requires.

Use the BiNotePads online notepad to adapt this example. For a separate copy of important work, follow the browser-note backup guide.