A Small-Site SEO Content Audit with a Decision Log

A small site rarely needs a complicated scoring system to decide what to do with its pages. It needs an inventory that shows what each page is for, what evidence supports that purpose, and who can approve a change. A useful seo content audit ends with a decision for each page: keep it, refresh it, consolidate it with another page, or hold the decision until a missing fact is checked.

Search traffic belongs in that assessment, but it cannot make the decision alone. A page with few clicks may answer a narrow, important question. A page with many impressions may promise an answer its copy does not deliver. The audit should connect search evidence to a reading of the page and to the site’s responsibility for keeping its claims accurate.

Build an inventory of pages intended for search

Start with the site’s public URL list and identify the pages intended to be indexable. Include articles, guides, service pages and other substantive pages that could answer a searcher’s question. Keep preserved or established URLs in the sheet even when their content appears weak. An audit decision about copy is not permission to change an address.

Give each URL one row. Record its title, intended reader, primary task and current content owner. Then add the evidence available for the same review period: relevant queries, clicks and impressions, plus the date range and search type used. Search Console’s Performance report provides click and impression data and lets reviewers examine results by page or query. Those figures describe visibility in Google Search; they do not establish whether the page is factually sound or useful to everyone who visits it.

Read the page after collecting the figures. Mark each consequential claim as supported, in need of checking, or contradicted by a source the site can verify. Note missing steps, outdated interface descriptions, broken references and headings that promise more than the body supplies. Google’s content self-assessment questions ask whether material adds original value, covers its subject sufficiently and leaves readers able to achieve their goal. Use those questions to guide an editorial reading, not as a score that automatically determines a page’s fate.

Intent needs its own annotation. Write a short sentence such as “helps a new site owner identify the first indexing checks” rather than assigning only a broad label like “informational.” Compare that sentence with the queries that expose the page and with the answer a visitor actually receives. If those disagree, record the mismatch. Avoid guessing that a query proves what every searcher wanted.

Five example decisions and their thresholds

These examples describe a small technical publication. The findings are illustrative, not reported performance for this site. In a working audit, back each decision with dated evidence, a page reading and a named owner. Avoid an arbitrary click threshold that treats every page as having the same job.

• Keep a backup guide. A guide about checking whether a backup can be restored has relevant queries, working steps and an owner who confirms the current process. Keep its focused task and URL; review it when the backup process changes.
• Refresh a Search Console guide. The page has relevant impressions, but its menu instructions describe an older interface. A maintainer must verify the current steps before editing. Preserve the URL and record which instructions changed.
• Hold an indexing guide for comparison. Some paragraphs repeat a neighbouring guide, but this page contains a distinct diagnostic sequence. Compare both tasks before proposing a merge.
• Consider consolidating quick tips. A short indexing page repeats the fuller guide’s examples and steps. Check whether it serves a separate reader or contains useful material absent from the longer page. Approve a content map and URL treatment separately.
• Hold a privacy review page. Several policy-dependent claims lack a current source and no accountable reviewer has confirmed them. Obtain the policy material and an owner before retaining or rewriting those claims.

Add the evidence location and review date to the working sheet so the next editor can inspect each decision.

Work the decisions, not just the labels

Keep: a narrow page can still earn its place

The backup guide has a clear task: helping a reader verify that a backup is restorable. Its relevant queries suggest that searchers can find it, while a current owner has checked its procedure. Those are separate pieces of evidence. The decision is to keep its purpose and URL, with a review trigger tied to a process change. “Keep” does not mean the page can be forgotten. Record who will notice when the instructions become stale.

Do not merge it into a broad site-maintenance article merely because both discuss backups. A visitor who needs a restore check should not have to search through a general essay to find the sequence. The audit protects a focused answer when its value is supported by intent and factual ownership.

Refresh: correct a page without changing its job

The Search Console guide still serves a recognizable reader task, and its search evidence points to relevant interest. Its problem is accuracy: instructions tied to an older interface can send a reader to the wrong place. The maintainer should verify the current path, revise the affected steps, check the headings against the new copy and note which screenshots or descriptions were replaced.

Keep the established URL because the task remains the same. Save the previous text, the supporting source and the date of the edit. After publication, check that the revised page renders properly and that its links work. Later search data can help frame another review, but a short change in clicks cannot prove that the correction succeeded or failed.

Consolidate: require proof that two pages serve one task

The quick-tips page is a candidate only after an editor compares it with the fuller indexing guide. Highlight the advice that genuinely repeats, identify anything useful that appears only on the shorter page, and ask whether each page answers a different question. Confirm who owns both pages and who can approve moving their material. If the short page contains a distinct first-step explanation, the answer may be to sharpen both pages instead.

If the content is substantially the same, prepare a map showing where each useful section will live. Separately review the technical treatment of the URLs. Google’s canonicalization guidance applies to duplicate or very similar pages and describes redirects and canonical annotations as signals for a preferred URL. Similar subject matter alone is not enough to justify either method. The site’s URL-preservation rules and the approved destination must be checked before any redirect or canonical change is made.

Keep content judgments separate from indexing work

A content audit asks whether a page deserves its particular editorial role. A technical indexing review asks whether search systems can access it and which URL they may treat as representative. Put these findings in separate columns. An accurate page with no impressions might need an access investigation, a clearer internal path, or simply more observation. Rewriting it because a metric is empty could leave the actual problem untouched.

Likewise, an editorial decision to consolidate does not execute a redirect. First preserve the useful content and approve its destination. Then assess the existing URL, incoming links, internal references and any preservation requirement. Document the technical proposal for the person responsible for routing and indexing. This separation prevents an editor’s label in a spreadsheet from becoming an unreviewed site change.

Record a reversible decision

Give every approved change a short log entry: URL, previous purpose, evidence reviewed, decision, approving owner, exact edits, publication date and verification result. For a refresh, retain the earlier copy so an inaccurate revision can be corrected quickly. For a proposed consolidation, retain the source page and its content map until the URL treatment has been separately approved and tested. “Deferred” is a valid log state when the evidence is insufficient.

The next review should test the reason for the decision. Is the kept guide still accurate? Does the refreshed page now lead the reader through the right steps? Did the consolidated material remain easy to find? Compare equivalent Search Console periods where possible, and note other site changes that may affect the figures. The audit is complete when each page has a defensible action or a named missing piece of evidence—not when every page has been edited.