Before restoring a site, you don’t fix pages-you verify information. A content audit is how you find what still earns traffic, what’s misleading, and what’s just wasting crawl budget, so your restoration doesn’t accidentally delete the very SEO you’re trying to preserve.
When people search for this, they usually want answers to: What should I audit first? How do I decide what to keep, update, or remove? What data do I need for quality checks? And how do I document it so the restoration team can execute without guesswork? As Google notes in its helpful content guidance, creating “people-first” content depends on evaluating what’s truly useful-not just rearranging URLs.
Meanwhile, Google also reminds site owners that search indexing and content understanding are affected by technical and structural signals. In practice, restoration work often changes templates, navigation, performance, and markup-so your content inventory needs to be paired with a decision log that survives the migration window. The planning mindset here is aligned with Search Console’s monitoring and crawl continuity: you’re not only publishing changes, you’re managing how search engines discover and interpret the site after the change.
By the end of this guide, you’ll have a repeatable audit workflow: a spreadsheet structure, scoring rules for relevance/quality, gap detection steps, and a clear “restoration-ready” output you can hand to implementation without losing context.
Table of contents
- Purpose of a content audit
- Steps to conduct a content audit
- Identifying content gaps
- Deciding what to keep, update, or remove
- Documenting findings for restoration
Purpose of a content audit
A content audit is a structured inventory of every indexable content URL (and the major non-indexable assets that affect user experience), evaluated using relevance, quality, and intent coverage. Before restoration, its job is to answer four operational questions:
- What should remain live? (keep)
- What needs improvement to keep rankings and help users? (update)
- What should be retired? (remove or merge)
- Where are the missing pieces? (gaps)
The audit isn’t “SEO theater.” It’s the evidence layer that lets you make consistent decisions during restoration-when templates, menus, and internal linking rules are in flux.
Steps to conduct a content audit
1) Inventory URLs (and classify them)
Start with a full export of URLs you can reasonably restore. For each URL, capture:
- Current URL
- Content type (page, post, landing page, category, tag, attachment)
- Indexing status (indexed, noindex, blocked)
- Primary intent (informational, commercial, navigational)
- Target keywords/topic (if known)
If you don’t already have an export, you can build it from crawling tools and/or your analytics/search exports. Treat this as your “restoration map,” not a final judgement.
2) Add performance + engagement signals
For each URL, add at least one metric that reflects value and one metric that reflects demand:
- Value proxies: conversions, newsletter signups, leads, time on page, engaged sessions
- Demand proxies: impressions and clicks (e.g., Search Console), ranking coverage
Even a simple approach works: “high/medium/low” buckets based on your last 3-6 months of data.
3) Score quality using a checklist
Create a quality rubric and apply it consistently. A practical rubric for restoration usually includes:
| Dimension | What to check | Typical “red flags” | Owner cue |
|---|---|---|---|
| Relevance | Matches the page’s stated topic/intent | Off-topic sections, mismatched keywords | Content editor |
| Accuracy | Facts, dates, claims, pricing/availability | Outdated instructions, broken references | Subject reviewer |
| Structure | Headings, scannability, internal flow | Thin sections, no clear answer | Editor/UX |
| Freshness | Needs updates vs. still evergreen | No date context, stale examples | Editor |
| Experience | Mobile layout, readability, media load | Broken embeds, unreadable text, slow rendering | Implementation |
4) Check internal linking and cannibalization
Restoration often changes navigation labels and template linking rules. Before you implement:
- List top pages and where they are linked from.
- Identify near-duplicates or pages targeting the same intent.
- Mark any “which page should rank?” conflicts so they’re resolved intentionally (merge, update, or redirect).
5) Validate technical dependencies
Some content URLs aren’t just text-they rely on:
- forms (contact, lead capture)
- scripts (embeds, downloads, interactive elements)
- assets (images, PDFs) with alt text and correct formats
Your audit sheet should include “implementation requirements” so the restoration doesn’t produce broken pages that look fine in a quick glance.
Identifying content gaps
After you’ve inventoried and scored existing content, gaps become easier to see. A gap is usually one of these:
- Missing intent: users search for an answer type (e.g., pricing, how-to, comparisons) that you don’t provide.
- Weak coverage: you cover the topic, but the page doesn’t satisfy the full question.
- Outdated coverage: the topic exists, but it no longer reflects what users need now.
To find gaps without getting lost in spreadsheets, run a simple workflow:
- Pick your core topics from analytics and internal navigation.
- Compare “what exists” vs. “what users are looking for” (search queries, discovery paths, common support questions).
- Mark gaps with a proposed solution type: update existing page, create new page, or merge multiple pages.
Deciding what to keep, update, or remove
This is where audits fail when decisions are emotional. Use a decision matrix instead. For each URL, pick one outcome:
- Keep: strong relevance + acceptable quality + demand exists.
- Update: demand exists but quality/relevance is weak (refresh content, improve structure, fix media).
- Remove/Merge: low demand and low usefulness, or duplicates that fragment intent.
- Redirect: if the content is retired but an equivalent destination exists (or you’re consolidating intents).
A practical rule of thumb
When you’re unsure, ask: “If this URL disappeared tomorrow, would users still find the right answer elsewhere?” If yes, consolidation may be safer than “saving everything.” If no, update is usually cheaper than repairing damage later.
Example decision scenarios
- High impressions, weak engagement: the title/topic alignment is off → update headings, add the missing sections, improve internal linking.
- Low impressions, high quality: keep and strengthen distribution → update metadata, add internal links, and ensure the page remains accessible in navigation.
- Multiple pages targeting the same intent: merge into one “source of truth” page → update content and consolidate internal links.
- Broken forms or scripts: keep if the page is valuable, but add “form rebuild” as a restoration requirement rather than publishing as-is.
Documenting findings for restoration
Your audit output should be a restoration-ready handoff. The goal is simple: an implementer should be able to restore without asking, “Wait-what did we decide?”
What your spreadsheet (or database) should include
- URL decision: keep / update / remove / merge / redirect
- Destination mapping: if redirect/merge, specify the destination URL
- Update scope: what changes (copy, headings, media, internal links, templates)
- Quality notes: short bullets explaining why the decision was made
- Implementation requirements: forms, scripts, asset fixes, accessibility checks
- Owner: who executes content vs. who executes technical restoration
Add an “audit log” section
Restoration changes often happen in parallel. Add a section that records:
- What assumptions were made
- What data was missing (and how it was handled)
- Any pages intentionally deferred (and why)
That audit log is how you prevent silent rework-and how you keep SEO and user experience decisions consistent when deadlines get loud.
External references
- Google Search Central: Creating helpful content
- Google Search Central: Continuous crawl
- Google Search Console Help: Indexing reports and monitoring
- Semrush: Content audit guide
Conclusion
A content audit before restoration is how you protect relevance while you change everything else. You inventory URLs, score quality with a rubric, detect gaps, and make keep/update/remove decisions using demand and usefulness-not vibes. Then you document the results into a mapping and handoff sheet that implementation can execute reliably.
If you want a shortcut, build a “decision-first” spreadsheet template: columns for outcome, destination mapping, update scope, and implementation requirements. Treat it like the operating system for your restoration workflow.
Next practical step: start with your top 20 URLs by impressions and conversions, audit them using the rubric above, and only then scale out.