What is a content audit?
A content audit is a structured review of the pages, files and resources already published on a website. It connects what a page is for with evidence about whether it is useful, accurate, discoverable and still worth maintaining.
A good audit does more than count words or sort URLs by traffic. It asks whether each page has a job, whether it does that job well and whether another page now does it better. The output is a decision for every meaningful URL, not a spreadsheet that nobody owns.
- Keep: the page is useful, accurate and serving its intended purpose.
- Improve: the page has value but needs a content, technical or experience repair.
- Consolidate: several pages should become one stronger resource.
- Retire: the page has no useful future and should be removed carefully.
When should you conduct a content audit?
Run a deeper content audit after a migration, a change in business direction, a large publishing project or a period in which the library has grown without a clear owner. It is also useful when traffic falls, topics overlap or the team is spending more time maintaining pages than improving them.
Between larger reviews, keep the inventory current as new pages are published and old pages change. A lighter review of recently changed, high-value and underperforming content can prevent a future audit becoming an archaeological project.
Choose a review date and record it. Search performance and business outcomes move over time, so a dated snapshot is more useful than an unexplained “current” score.
How to set the scope
Define what the audit is intended to decide before exporting URLs. A whole public website may need a different process from a blog, help centre, product catalogue or set of high-value landing pages.
Set boundaries for:
- the hostname, folders, languages and content types included;
- the date range for traffic, conversions and search evidence;
- the templates or topics that need special attention;
- private, transactional and legal pages that require a separate treatment;
- the people who can approve content, technical and removal decisions.
Make a priority list before looking at totals. Include pages that generate leads, support customers, represent important products or explain the organisation, even when their traffic is modest.
Build a complete content inventory
No single source contains every URL that matters. Start with a crawl, then reconcile it with other records so pages outside ordinary navigation are not silently missed.
| Source | What it contributes | What to question |
|---|---|---|
| Clearcrawl crawl | Live status, indexability, links, titles, headings and repeated technical patterns | Can the crawler reach every relevant section and render the important content? |
| XML sitemap | URLs the site declares as important or canonical | Why are errors, redirects or excluded URLs listed? |
| Search Console | Queries, impressions, clicks, indexing and search visibility | Which URL does Google show for the intended topic? |
| Analytics | Engagement, entrances, journeys and conversions | Is a low-traffic page supporting another valuable action? |
| CMS export | Drafts, owners, dates, types and pages a crawl cannot discover | Which records are published, duplicated or no longer maintained? |
| Backlink sources | External references and authority a page may have earned | Would removal break a useful route or waste an important link? |
Normalise URLs before comparing the sources. Resolve protocol, host, trailing-slash, parameter and fragment differences so one page does not appear as several unrelated records.
What evidence should you record?
Use fields that help a reviewer make a decision rather than collecting every available metric. At minimum, record:
- URL, page title, topic, content type, template and intended audience;
- purpose, owner, publication date and last meaningful update;
- status code, canonical, indexability, internal links and crawl depth;
- organic impressions, clicks, queries, entrances, engagement and conversions;
- backlinks, referring pages, business importance and support-team feedback;
- accuracy, completeness, readability, accessibility and freshness notes;
- overlapping URLs, proposed action, reason, owner, deadline and verification date.
Keep raw evidence separate from judgement. A reviewer should be able to see which numbers were observed and which conclusion was made from them.
How to evaluate each page
Purpose and usefulness
State the job of the page in one sentence. Does it answer a question, support a decision, explain a product, complete a task or provide evidence? If nobody can describe the job, the page may be a duplicate, an accidental archive or a sign that the information architecture needs work.
Accuracy and completeness
Check claims, prices, dates, screenshots, legal details, contact information and references. A page can receive visits and still damage trust when its advice is out of date or its promise does not match the experience.
Intent and search role
Compare the title, heading, copy and internal links with the need implied by the target query. Look for a better page already serving the same need. Search visibility alone does not prove that the current page is the right destination.
Technical condition
Check response status, canonical, indexability, metadata, headings, internal links, structured data, mobile presentation and page experience. Fixing technical problems may be the right action even when the words themselves are strong.
Overlap
Group pages by topic, intent and template. Similar wording is not automatically a problem, but two pages with the same audience, promise and next step need a deliberate distinction or consolidation plan.
Choose the right content action
Use the evidence to choose one primary decision. A page can have several tasks, but an audit should not leave the owner with an ambiguous list of possibilities.
| Decision | Use it when | Next step |
|---|---|---|
| Keep | The page is useful, accurate and technically sound. | Maintain it and record the next review trigger. |
| Update | The purpose is still right but facts, depth, examples or signals are weak. | Refresh the content and verify the important template and links. |
| Differentiate | The page overlaps another but can serve a distinct audience or intent. | Clarify the promise, headings, internal links and scope. |
| Merge | Two or more pages answer the same need and one resource would be stronger. | Combine the useful material at a preferred URL and redirect the others. |
| Redirect | The old URL has a close, useful replacement but should no longer stand alone. | Use one direct, relevant redirect and update internal links. |
| Remove | The page has no useful purpose, replacement or audience. | Return an appropriate response and repair important incoming links. |
| Noindex | The page must remain accessible in a workflow but should not appear in search. | Apply the directive deliberately and monitor the reason for keeping it. |
Low traffic alone is not a deletion rule. A page may support a high-value journey, answer a narrow question, attract useful links or have little history because it is new. Combine performance with purpose, quality, overlap and business evidence. Use duplicate-content checks and keyword cannibalisation checks to decide which pages to merge, improve or keep. Add SEO software when you need evidence across the whole site.
How to implement content changes safely
Work in batches that have a shared reason, owner and verification plan. Begin with a representative page when a template or component is changing, then expand only after the result is useful.
- 01Choose the preferred destination.
For a merge, decide which URL and content structure will remain before editing.
- 02Preserve useful evidence.
Save copy, metadata, links, analytics context and decisions so a reviewer can understand what changed.
- 03Make one coherent release.
Update internal links, canonicals, sitemap membership and redirects together.
- 04Check the live result.
Test status, content, navigation and the important user journey before closing the action.
Do not use blanket homepage redirects for unrelated retired pages. A direct redirect is useful only when the destination is a close and useful answer.
Measure and verify the result
Record what changed and when. After publication, recrawl the affected URLs and confirm that the intended destination, canonical, links and indexability are correct.
- compare the intended pages rather than just the total URL count;
- check that merged pages preserve useful questions, links and conversions;
- inspect redirects for relevance, chains and loops;
- review Search Console and analytics after enough data has accumulated;
- record accepted exceptions so they are not reopened without context.
A successful audit reduces uncertainty. It does not promise that every page will gain traffic or that a smaller library is automatically better.
Run a content audit with Clearcrawl
- 01Export the crawl URLs.
Start with the live pages, response codes, indexability, metadata, links and template signals.
- 02Add performance and business evidence.
Join Search Console, analytics, CMS and backlink information to the URL inventory.
- 03Group the library.
Organise pages by topic, template, audience and the job each page is meant to do.
- 04Flag patterns.
Find technical issues, overlap, weak signals and pages missing from expected sources.
- 05Review manually.
Check accuracy, usefulness, intent, accessibility and business importance.
- 06Assign one decision.
Give each URL an action, owner and target date.
- 07Implement in batches and recrawl.
Verify the live result and retain the new baseline for the next review.
Clearcrawl supplies the live technical evidence. Combine it with performance and editorial evidence so content decisions are based on the page's whole role, not a single metric.
Common content audit mistakes
Traffic is one signal. Check purpose, links, conversions, freshness and search intent first.
Longer copy is not automatically more useful. Judge whether it answers the visitor's need clearly.
Reconcile the crawl with sitemaps, CMS, analytics and backlinks so orphaned content is not missed.
Choose the destination, update links and redirect the retired equivalents as one release.
A page can be accidentally noindexed, orphaned or redirected to the wrong place after the edit.
Frequently asked questions
What is a content audit?
A content audit is a structured review of the pages and assets a website already has. It combines crawl, search, analytics, business and editorial evidence so each URL receives a reasoned next action, such as keep, update, merge, redirect or remove.
How often should you conduct a content audit?
Run a deeper audit after a migration, major change in direction or large publishing project, then use lighter reviews to keep the inventory current. A monthly or quarterly review of changed and priority content is often more useful than repeating a full audit on a fixed schedule.
What should a content audit template include?
Include the URL, page type, topic, purpose, owner, publication and update dates, crawl status, indexability, traffic, conversions, search queries, links, backlinks, content quality notes, overlap and the final decision with its reason, owner and target date.
Should I delete content that gets no traffic?
Not automatically. Low traffic may reflect a deliberate private page, a new page, a narrow but valuable audience or a page that needs better targeting. Check purpose, quality, links, conversions, search demand and overlap before deciding whether to improve, merge, redirect or remove it.
Is content pruning good for SEO?
It can improve the usefulness and maintainability of a site when weak, obsolete or duplicative content is handled carefully. Deleting pages simply to reduce a count can remove useful coverage, break links and lose relevant history, so make each decision from evidence and verify the result.
ClearcrawlGive every page a clear future
Crawl the library, combine technical and performance data, give each page a reasoned action and verify every batch.
7 free days. See what Clearcrawl can find, then choose the plan that fits your site.