A content audit reviews existing pages against reader needs, performance evidence, and business purpose. To run one, inventory your URLs, collect evidence, assess each page’s usefulness, and assign a keep, update, consolidate, or remove decision. The deliverable is a prioritized improvement backlog—not an automatic deletion list or another publishing calendar.
For a small marketing team, we recommend auditing one manageable group of service pages and supporting articles first. Each URL should finish with a justified action, an accountable owner, and clear review criteria.
1. Define the audit’s purpose and scope
Start with the customer task your content should support. Do visitors need to compare services, understand eligibility, evaluate your approach, or submit a qualified inquiry?
Choose a business outcome to guide decisions, such as clearer service selection or fewer repetitive questions before a sales call. That is the intended outcome, not a promised result.
Define which pages belong in the audit. A practical starting scope might include one service category, its supporting articles, and relevant FAQ or support pages.
Keep content assessment distinct from technical checks:
- Content assessment: Is the page accurate, useful, distinct, and connected to a business purpose?
- Technical assessment: Can the page be accessed and crawled, and does it function properly?
Record technical problems that could affect your interpretation, but do not turn the exercise into a complete website audit. A useful page with an access problem needs a fix, not necessarily a rewrite.
2. Build a URL inventory and copyable worksheet
Create one row per content URL before deciding what to change. Combine your CMS page list, sitemap URLs, analytics landing pages, Search Console pages, and known unlinked pages used by sales or support.
Reconcile duplicates carefully. Standardize obvious URL variations for analysis, but retain a note when multiple live addresses need technical investigation. Do not accidentally merge distinct pages in the spreadsheet.
Copy this tab-separated header into a spreadsheet:
URL Intended reader task Search queries Performance evidence Business role Recommended action Rationale Priority Owner Review criteria Evidence dates Confidence Destination URL Due date Baseline Review date Change logUse the fields consistently:
- Performance evidence: Summarize search visibility, landing traffic, tracked actions, and relevant qualitative observations.
- Business role: State how the page supports acquisition, evaluation, sales, onboarding, or support.
- Rationale: Explain why the proposed action fits the evidence.
- Confidence: Use high, medium, or low, with a short explanation where needed.
- Destination URL: Complete this when consolidation or removal involves a replacement.
- Baseline: Record the pre-change measures, reporting period, and qualitative observations you will compare later.
- Review criteria: Define both implementation checks and the later outcome review; use the review date to schedule that follow-up.
A blank inventory is only a starting point. The value comes from decisions another team member can understand and execute.
3. Combine search, analytics, and inquiry evidence
Search traffic alone cannot establish a page’s value. Collect evidence from several sources.
Search Console: The Search results report provides clicks, impressions, click-through rate, and average position, with page and query groupings. Use these to understand how a page appears in Google Search. They are not inquiry counts or a complete content inventory. Chart and table totals can also differ because of aggregation.
Analytics: Review landing traffic by channel and tracked inquiry actions. Keep the action’s meaning explicit: a form interaction, submitted form, and qualified sales opportunity are different events.
CRM and staff observations: Look for pages referenced in proposals, questions that repeatedly reach sales, and resources support staff send to customers. Record these observations as qualitative evidence rather than pretending they are measured conversion data.
Manual review: Read the page, follow its links, and try its next step. Reports cannot tell you whether an offer description is still accurate.
Align reporting periods before comparing pages. Account for seasonality, page age, tracking changes, and mismatches between recorded URLs. A recently launched page and an established seasonal page need different interpretations.
When evidence is unavailable, enter unknown, not zero. Add a task to resolve the gap if it could change the decision.
4. Review each page’s reader task and business role
For every URL, answer five questions:
- Accuracy: Are the offer, examples, instructions, and claims current?
- Intent fit: Does the page answer the question its intended reader brings?
- Distinct usefulness: Does it contribute something another page does not?
- Offer alignment: Does it support something the business currently provides or needs to explain?
- Next step: Can the reader take an appropriate action without confusion?
A low-search page may still help referral visitors choose a service, support a proposal, or answer an onboarding question. If the content is useful but visitors struggle to act, check friction in the inquiry path before assuming more content is needed.
These hypothetical worksheet entries illustrate how qualitative evidence can guide an initial decision:
| Page | Evidence and business role | Initial action | Rationale or next check |
|---|---|---|---|
| Specialized service page | Low search visibility; sales team reports linking it in proposals | Keep, provisionally | Confirm current accuracy and record how it supports service evaluation |
| Two articles answering similar questions | Similar topics; unique contributions and inquiry roles not yet reviewed | Keep pending overlap review | Compare reader tasks before deciding whether to consolidate |
| Discontinued offer page | Describes an offer no longer available | Remove candidate | Check incoming links, customer dependencies, and possible replacements first |
These are decision patterns, not performance results.
5. Assign keep, update, consolidate, or remove
Choose an action based on purpose and evidence, not an arbitrary traffic, age, or word-count threshold.
| Action | When it fits | Caution |
|---|---|---|
| Keep | The page remains accurate, useful, and distinct | Keep does not mean ignore indefinitely; record review criteria |
| Update | The purpose is sound, but accuracy, coverage, clarity, or the next step needs work | Specify the gap instead of assigning a vague “refresh” |
| Consolidate | Pages serve genuinely redundant reader tasks, and a combined destination can preserve their useful material | Shared keywords alone do not justify merging |
| Remove | The page has no justified ongoing role and no useful replacement | Check links, customer use, and other dependencies before retirement |
Write a short rationale beside every decision. “Update because the service description omits current eligibility requirements” is actionable. “Poor SEO” is not.
Low traffic should trigger investigation, not automatic deletion. When evidence is uncertain, assign a provisional keep, name the missing evidence, and give someone a date to investigate it. This prevents uncertainty from becoming either a rushed deletion or a permanent unresolved row.
6. Validate overlap and plan URL changes safely
Before consolidating pages, compare their reader intent, unique sections, inquiry activity, incoming links, history, and URL suitability. Two pages can mention the same keyword while serving different needs—for example, explaining a process versus helping someone select a service.
Choose the surviving URL only after that review. Preserve useful material from retiring pages and make sure the destination genuinely serves their readers.
For implementation, use this handoff checklist:
- Publish and check the consolidated destination before retiring the old pages.
- Map each retiring URL to its appropriate replacement.
- For permanent moves, use permanent server-side redirects, such as 301 or 308, where technically possible.
- If content is removed without a suitable replacement, return HTTP 404 or 410.
- Update internal links, the sitemap, and the destination’s self-referencing canonical.
- Test old URLs, destinations, and inquiry paths before accepting the work.
These treatments follow Google’s guidance for URL changes. Google also cautions against irrelevant mass redirects to a homepage, which may be treated as soft 404s. Redirects are not a guarantee that traffic or rankings will be preserved.
7. Prioritize the backlog and review completed changes
Rank work by business impact, evidence confidence, effort, risk, and dependencies—not traffic alone. A misleading service page may deserve attention before a high-traffic article with minor formatting issues.
A practical order is:
- Correct inaccurate offers and broken inquiry paths.
- Improve important pages with clear, well-supported gaps.
- Schedule consolidations that require content and technical coordination.
- Investigate low-confidence decisions before making irreversible changes.
This is a planning recommendation, not a search-engine requirement. Use your customer journey and available resources to adjust it. The same principle applies when you evaluate SEO against business value: visits matter in context, not as an isolated score.
Give each task an owner, due date, baseline, scheduled outcome-review date, and change log. Separate two checkpoints:
Implementation acceptance: Is the content accurate? Do links and redirects work? Is the intended inquiry path usable? Were the planned URL changes completed?
Outcome review: What changed in relevant search visibility, landing visits, inquiry actions, or staff feedback? Compare suitable periods, account for seasonality, and allow longer when data is sparse. For consolidation, assess the former URLs and surviving destination together rather than treating the retired pages’ traffic decline as the whole result. Record other changes that could affect interpretation.
Start by inventorying one manageable group of pages and assigning evidence-backed actions before commissioning more content. The audit is complete when the backlog has owners and review criteria—not merely when the spreadsheet is filled.
If you need help connecting reader intent to page mapping, service copy, and supporting articles, explore Kohl Digital’s SEO Content service.