Key takeaways
- A content audit is an inventory plus a decision: every page gets a keep, update, merge, redirect or remove verdict with a reason.
- Use more than traffic. A page with few visits can still be the one that answers a buyer's last objection.
- Look for overlap before you look for gaps. Pages competing for the same intent usually need consolidating, not more companions.
- Run the audit on a schedule, and record decisions so the next audit starts from evidence instead of memory.
01
What is a content audit, and when do you need one?
A content audit is a structured review of the pages you already have. You list every URL, attach performance and quality data, and decide what to do with each page. It answers a plain question: which of our pages help a reader and the business, and which ones get in the way?
You need one when traffic or conversions have plateaued, when you have published for years without pruning, after a merger or rebrand, and before a migration. Google's guidance on helpful content asks whether pages demonstrate first-hand expertise and leave readers feeling they have learned enough to reach their goal; an audit is how you check that across a whole site.
02
How do you run a content audit step by step?
Start with a crawl to build the inventory: URL, title, status code, word count, canonical, last updated and internal links in. Join it to Search Console data for clicks, impressions and average position, and to analytics or CRM data for conversions and assisted revenue. Add a column for owner and a column for the page's job in the buyer journey.
Then review pages in groups by topic, not alphabetically. Reading five pages on the same subject together makes overlap, contradiction and outdated claims obvious in a way a spreadsheet filter never does.
- Crawl and export every indexable URL
- Join Search Console and analytics data
- Add conversion or pipeline contribution
- Tag each page with topic, intent and owner
- Review by topic cluster
- Assign a verdict and a reason
- Log the decision and schedule the work
03
How should you decide keep, update, merge or remove?
Keep pages that perform and are accurate. Update pages with good potential and stale facts, weak structure or missing answers. Merge pages that target the same intent, redirecting the weaker URL to the stronger one so signals consolidate. Remove or noindex pages that serve no reader, and redirect them only when a genuinely relevant replacement exists.
Be cautious with deletion for its own sake. A thin page that gets no traffic may be the only place a customer finds a specific answer, and removing pages can break internal links and external references. Check backlinks and referring pages before you cut.
| Signal | Likely verdict | Check first |
|---|---|---|
| Good traffic, accurate, converts | Keep | Refresh dates only when content changed |
| Declining traffic, outdated facts | Update | Sources, screenshots, prices, legal claims |
| Two pages, same intent | Merge and redirect | Which URL has links and history |
| No traffic, no links, no purpose | Remove or noindex | Internal links pointing to it |
| Low traffic but answers a late-stage question | Keep and link to it | Whether sales uses it |
04
How do you keep the audit from going stale?
Treat the audit as a recurring process. Set a review interval by how fast the claims on a page change: pricing, regulations and platform features need frequent checks, evergreen concepts less. Put the next review date on the inventory and assign a named owner.
Keep the audit log with the reason for every decision. When a stakeholder asks next year why a page was removed or merged, you can show the data, and when results change you can separate your edits from outside effects such as seasonality or an algorithm update.
Was this useful? Send it to someone who owns this problem.
Primary sources and further reading
Use the source material to validate details against your own context and current platform configuration.
- Google Search Central: Creating helpful, reliable, people-first content
- Google Search Central: Consolidate duplicate URLs
- Google Search Console: How are you performing on Google?
- Google Search Central: Site moves with URL changes
This field note follows the XenGrowth editorial policy: primary sources where available, visible limitations, material review dates, and no invented first-hand experience.
Stay with the problem
Related field notes
Local Search OptimizationReview Management Is a Workflow, Not a Reply Button: Ask, Route, Reply, Escalate, Use
AI and answer enginesAI Search Optimization: What Moves Citations and What Is Folklore
SEO & GEOTopical Map: Build a Cluster Plan Search and AI Can Read, and Know What Topical Authority Is Not