Content Inventory for Small Sites: The Spreadsheet That Makes Cleanup Decisions Easier

SEO Slots

Search Intent

The reader wants a spreadsheet structure and decision process for reviewing existing pages and planning cleanup.. The article must answer the reader's operational question before any commercial route appears.

Reader Artifact

Reusable checklist, table, or runbook from the article body. This artifact is the reason the article can be saved, cited, or reused by an operator.

Internal Links

• Hub: /resources/small-site-ops-library/
• Related article: /resources/small-site-ops-library/weekly-site-qa-checklist/
• Related article: /resources/small-site-ops-library/broken-link-triage-small-sites/
• Related article: /resources/small-site-ops-library/measurement-sanity-check/
• Related article: /resources/small-site-ops-library/website-publish-checklist/
• Tool/service route: /services/content-audit-cleanup-plan/

Structured Data

Recommended schema: Article, BreadcrumbList. Keep BreadcrumbList aligned with /resources/small-site-ops-library/content-inventory-template-small-sites/. Do not add Product, Offer, Review, Rating, or FAQPage schema for this wave unless a later approved public page visibly supports it.

CTA Route

Primary route: /services/content-audit-cleanup-plan/.

CTA label: Use the related checklist or diagnostic route.

CTA family: diagnostic_sprint.

Use this route only after the article artifact has clarified the next operational step. Public forms, accounts, and payments are intentionally not part of this resource page.

The CTA stays measured and specific, with no public payment or account route on this page.

Measurement

Public-Preflight NG Items

• Fake client proof, fake metrics, fake awards, or guaranteed outcomes.
• Public account, form, payment, repo, domain, or outreach route before checks pass.
• Unapproved cross-brand, unrelated monetization, or off-topic trust route.
• Unsupported claims about SEO, ranking, revenue, or tool behavior.
• Machine-like slug, broken internal link, missing schema plan, or missing measurement slot.slug: "content-inventory-template-small-sites"

primary_query: "content inventory template"

secondary_queries:

• "website content inventory"
• "small site content audit"
• "content cleanup spreadsheet"

search_intent: "The reader wants a spreadsheet structure and decision process for reviewing existing pages and planning cleanup."

H1: "Content Inventory for Small Sites: The Spreadsheet That Makes Cleanup Decisions Easier"

H2_outline:

• "When a Small Site Needs a Content Inventory"
• "The Minimum Useful Inventory"
• "How to Collect URLs"
• "Decision Matrix: Keep, Update, Merge, Redirect, Remove"
• "Priority Rules"
• "Inventory Workflow"
• "Copyable Content Inventory Template"
• "Content Inventory Review Checklist"
• "Common Failure Modes"
• "Monthly Maintenance Rhythm"
• "Natural Next Step"

internal_links:

• "/resources/small-site-ops-library/weekly-site-qa-checklist/"
• "/resources/small-site-ops-library/broken-link-triage-small-sites/"
• "/resources/small-site-ops-library/website-publish-checklist/"
• "/resources/small-site-ops-library/measurement-sanity-check/"

external_reference_policy: "No external references required for draft. If platform exports, Search Console behavior, or crawl-tool instructions are added, verify against official documentation at publish time."

schema_type_recommended: "Article + BreadcrumbList; FAQPage only if visible FAQ is added"

FAQ_candidates:

• "What fields should a content inventory include?"
• "Should low-traffic pages always be removed?"
• "How often should a small website refresh its content inventory?"

CTA_route: "/services/content-audit-cleanup-plan/"

measurement_event_name: "small_site_ops_content_inventory_cta_click"

public_preflight_ng: true

Old pages create quiet operational debt. A service page says one thing, a blog post says another, an old campaign page is still indexed, and a PDF from three years ago keeps getting linked from the footer.

A content inventory helps small teams see the site as an operating system instead of a pile of URLs.

This guide explains how to build a practical content inventory for a small website. The goal is not to create a beautiful spreadsheet. The goal is to make decisions: keep, update, merge, redirect, noindex, or remove.

Related same-pack guides: run weekly site QA to keep the inventory current, use broken link triage for cleanup decisions, and apply the publish checklist so new pages enter the inventory cleanly.

## When a Small Site Needs a Content Inventory

Create or refresh a content inventory when:

- nobody knows which pages are live;
- old offers, prices, staff names, or screenshots may still be public;
- organic traffic is spread across many thin pages;
- a redesign or migration is coming;
- multiple people publish without one shared source of truth;
- internal links lead to outdated pages;
- sales or support keeps finding pages that contradict current messaging;
- analytics reports show pages that the team forgot existed.

You do not need an enterprise crawler to start. For a small site, a spreadsheet with 30 to 300 rows can already change the conversation.

## The Minimum Useful Inventory

A content inventory should answer four questions:

1. What exists?
2. Why does it exist?
3. Is it still useful and accurate?
4. What should happen next?

Use this schema as a starter:

| Field | Purpose | Example |
|---|---|---|
| URL | Canonical page address | `/services/site-maintenance/` |
| Page type | Helps group decisions | Service, blog, landing, legal, resource |
| Owner | Who can approve changes | Marketing, founder, operations |
| Last reviewed | Freshness control | `2026-05-21` |
| Primary purpose | Why the page exists | Explain maintenance service |
| Target reader | Who the page is for | Small business owner |
| Business role | How the page supports the site | Lead, trust, support, SEO, policy |
| Traffic signal | Recent traffic pattern | Stable, declining, none, unknown |
| Conversion/link role | CTA or internal link function | Sends to contact form |
| Quality status | Current content condition | Good, stale, thin, duplicate, risky |
| Decision | What to do | Keep, update, merge, redirect, remove |
| Next action | Specific task | Update screenshots and CTA |
| Priority | Work order | P0, P1, P2, P3 |
| Notes | Evidence and context | Old pricing table present |

This is enough to start. Add more fields only when they change decisions.

## How to Collect URLs

Use multiple sources because each source misses something.

| Source | What it finds | What it may miss |
|---|---|---|
| CMS export | Published pages/posts | Hardcoded pages, PDFs, orphan pages |
| Sitemap | Indexable public URLs | Noindexed pages, draft routes |
| Analytics | Pages that get visits | Pages with no recent traffic |
| Search Console | Pages discovered by search | Private or unindexed pages |
| Manual nav crawl | Pages users can reach | Orphan pages |
| Backlink tools or referrer logs | Externally linked pages | Pages with no external discovery |

For the first inventory, do not chase perfection. Mark uncertain rows as `unknown` and keep moving.

## Decision Matrix: Keep, Update, Merge, Redirect, Remove

The inventory becomes useful when each page receives a decision.

| Condition | Recommended decision | Why |
|---|---|---|
| Accurate, useful, has a clear role | Keep | No action beyond review date |
| Useful topic, stale details | Update | Preserve value while fixing trust risk |
| Similar to another stronger page | Merge | Reduce duplication and improve clarity |
| Obsolete but has traffic or backlinks | Redirect | Preserve user path and link equity where appropriate |
| Obsolete, no value, no traffic, no links | Remove or noindex | Reduce clutter |
| Legal/policy/support page | Review with owner | Accuracy matters more than traffic |
| Campaign page still referenced | Update, redirect, or clearly archive | Avoid confusing returning users |

Do not remove a page just because it has low traffic. Some pages exist for trust, support, compliance, or sales enablement.

## Priority Rules

Prioritize pages by risk and leverage.

| Priority | Page condition | Example action |
|---|---|---|
| P0 | Public trust or revenue risk | Fix current offer, broken lead route, wrong legal claim |
| P1 | High-traffic or high-intent page is stale | Update service/pricing page |
| P2 | Useful page needs improvement | Expand thin guide, improve internal links |
| P3 | Low-risk archive cleanup | Update tags, remove minor duplicate |

Small teams often waste cleanup time on low-risk archive pages while the contact page, services page, or top landing page remains outdated. Sort by business role before traffic.

## Inventory Workflow

### Step 1: Build the URL List

Export from the CMS, sitemap, analytics, and Search Console if available. Remove exact duplicates, but keep variants that may indicate canonical problems.

### Step 2: Add Page Type and Business Role

Do this before quality scoring. A thin legal page and a thin blog post are not the same operational problem.

Business role examples:

- Lead generation;
- Trust proof;
- Search acquisition;
- Customer support;
- Product/service explanation;
- Policy/legal;
- Campaign;
- Archive/reference.

### Step 3: Review Quality and Freshness

Check whether the page is accurate, useful, and aligned with the current site.

Look for:

- old dates presented as current;
- outdated screenshots;
- old staff or company information;
- outdated pricing or offer text;
- broken internal links;
- outdated product or service names;
- duplicated paragraphs;
- missing CTA;
- mismatch between title and content.

### Step 4: Assign a Decision

Use one decision per row:

- `KEEP`
- `UPDATE`
- `MERGE`
- `REDIRECT`
- `REMOVE`
- `NOINDEX`
- `REVIEW_OWNER`

If the decision is not obvious, mark `REVIEW_OWNER` instead of guessing.

### Step 5: Turn Decisions Into Work Blocks

Do not create 80 separate tasks. Group work:

- "Update top 10 trust pages"
- "Merge duplicate service articles"
- "Repair outdated campaign links"
- "Review old PDFs"
- "Redirect obsolete landing pages"

## Copyable Content Inventory Template

URL,Page Type,Owner,Last Reviewed,Primary Purpose,Target Reader,Business Role,Traffic Signal,Conversion/Link Role,Quality Status,Decision,Next Action,Priority,Notes

/services/,Service,Marketing,YYYY-MM-DD,Explain services,Prospect,Lead,Stable,Contact CTA,Good,KEEP,Review next quarter,P2,

/old-campaign/,Landing,Marketing,YYYY-MM-DD,Past campaign,Prospect,Campaign,None,Old form link,Stale,REDIRECT,Redirect to current offer,P1,Old offer still indexed

/blog/example/,Blog,Editorial,YYYY-MM-DD,Explain topic,Operator,SEO,Declining,Internal links,Thin,UPDATE,Add checklist and current examples,P2,

## Content Inventory Review Checklist

Content Inventory Review

Date:

Reviewer:

Site section:

[ ] URL list includes CMS export

[ ] URL list includes sitemap URLs

[ ] URL list includes analytics/Search Console URLs if available

[ ] Page type assigned

[ ] Business role assigned

[ ] Owner assigned or marked unknown

[ ] Last reviewed date added

[ ] Quality status assigned

[ ] Decision assigned

[ ] Priority assigned

[ ] P0/P1 pages reviewed first

[ ] Redirect candidates checked for backlinks or internal links

[ ] Removal candidates checked for business/legal/support value

[ ] Work grouped into repair batches