Content Audit: How to Review Every Page and Decide What to Do

Most websites grow by addition. A blog post here, a service page there, a campaign page nobody removed after the campaign ended. After a few years nobody can say how many pages exist, which ones still bring visitors, or which ones say something that is no longer true. A content audit fixes that. It is a one-time review in which you list every page, attach some evidence to each, and give every URL a decision.

This guide is for owners and editors of small and mid-sized sites, from 30 pages to a few thousand. You do not need paid software: a crawl or CMS export, Google Search Console and a spreadsheet are enough. You will end with an audit sheet, one row per URL, a scoring rule you can defend, and an action list in priority order. The audit shows where to spend effort. It does not promise that any change will raise traffic or rankings, because Google decides what to show.

Short answer: A content audit is a page-by-page review of your site. Export every URL, add clicks, impressions, links and a quality note for each, then label each page keep, improve, merge, redirect or remove. Act on the biggest problems first, record what you changed, and review the results after several weeks.

Before you begin

You need a list of every indexable URL, read access to Google Search Console, and a spreadsheet. If Search Console is not set up, start with Set Up Google Search Console: Complete Website Owner Checklist; its data only builds from the day you verify.

Plan two to four hours for about 100 pages. The audit changes nothing on the live site, so the risk sits in the follow-up. Before you delete, redirect or merge anything, back up the pages involved and save a copy of the final sheet. Decide who can approve removals. An audit that nobody acts on is the most common way this work is wasted.

What is a content audit, and how is it different from pruning?

A content audit asks whether each page is accurate, useful and still needed. A technical audit asks how search engines crawl, render and index the site. Run both; they find different problems.

Pruning is one possible outcome of an audit. For the removal and merge rules in depth, read Content Pruning: Decide What to Update, Merge or Remove. This guide covers the wider job of building and scoring the inventory, so that pruning is one of several actions.

Google's page on helpful, reliable, people-first content supplies the editorial test. It asks whether a page offers original information, treats the topic completely, would be worth bookmarking, and is free of easily verified factual errors. It also says not to change dates to look fresh when content has not substantially changed. Keep Helpful Content Checklist: Review Your Pages Against Google's Advice nearby for borderline pages.

Step-by-step instructions

Step 1: Build the URL inventory

Combine at least two sources, because one is never complete: a crawl of the live site (finds pages reachable by links), your XML sitemap (pages you want indexed) and a CMS export (finds pages nothing links to). Merge them, remove duplicates and keep one row per canonical URL. Pages in the CMS or sitemap but missing from the crawl are probably orphans; see Orphan Pages: How to Find Pages With No Internal Links and Fix Them. Put pagination, tag archives and parameter URLs on a separate tab.

What success looks like: One sheet, one row per page, and a row count you can compare with the CMS.

Step 2: Add the facts for each page

Column	Source	Why it matters
URL, title	crawl	Spot duplicate and vague titles
Page type	you label it	Service, product, article, utility
Word count	crawl	Find near-empty pages (a signal, not a target)
Last meaningfully updated	CMS	Find stale pages
Clicks and impressions, 12 months	Search Console	Google visits and visibility
Internal links in	crawl	Is the page connected?
Referring sites	Search Console Links report	Does anyone else link here?
Indexed?	Page indexing report	Is Google keeping it?

Take clicks and impressions from the Performance report, grouped by page, over a long range. Google's traffic-drop guide notes the report can extend to 16 months, enough to see a yearly cycle, so a seasonal page does not look dead because you checked in its quiet months. These figures cover Google Search only; a page that earns visits from email or social media may look weaker here than it is, so add an analytics column if you have one. For the indexed column, see Page Indexing Report Explained: Every Status and What to Do and How do I check if a page is indexed by Google?.

What success looks like: Every evidence cell holds a number or a deliberate blank.

Step 3: Read the page, not just the numbers

Numbers tell you where to look, not whether a page is good. Open each page, or a sample on a large site, and answer four questions:

Accurate? Are prices, dates, names, laws and contact details still correct?
Useful? Would a visitor from a search on this topic get what they came for?
Distinct? Does another page answer the same question? If so, the two compete. Thin Content and Duplicate Pages: How to Find and Fix Them shows how to confirm it.
On purpose? Does it still match what the business offers?

Score quality 1 to 3 and write one line of notes. A rule you can apply to 200 pages in an afternoon beats a perfect rule you apply to ten. Do not score by word count: Google's quality questions list targeting a word count as a warning sign, and its starter guide says length alone does not affect ranking.

What success looks like: Every page has a 1 to 3 score and a note a colleague could understand.

Step 4: Assign one decision to each page

This table is a starting rule of thumb, not Google's rule. Adjust it to your site.

Evidence	Quality	Decision
Clicks or external links	3	Keep. Maybe add internal links
Impressions, few clicks	2	Improve. Rework title, opening, structure
Clicks or links	1 (outdated)	Update first. The audience exists
Same topic as a stronger page	any	Merge and redirect
No clicks, links or purpose	1	Remove
Needed by customers, not for search	any	Keep, with noindex

Two cautions. Low traffic is not proof of low value: a page that supports a sale or answers a support question may earn its keep with few visits. And a new page has had no time to collect data, so give recent content a longer window.

What success looks like: Every row has exactly one decision.

Step 5: Prioritise

A workable order for most small sites:

Errors and risks: wrong prices, outdated legal or safety information, broken forms.
Visible pages that underperform: impressions without clicks usually point at the title or opening. See Write SEO Title Tags and Meta Descriptions That Match Search Intent.
Merges and redirects: they take planning but clean up competing pages.
Removals: last, because they are hardest to reverse.

Give each action an owner, an effort estimate and a date. An audit of 300 pages might yield 40 actions, which is a good result; most pages should simply stay.

What success looks like: A ranked list with an owner and date on every line.

Step 6: Make the changes safely

When you improve a page, change something real: fix facts, answer the question more directly, add missing detail. Leave the visible date alone unless the content changed substantially.

When you merge or remove, handle the URLs properly. Google's redirect guide says a permanent redirect makes the target the canonical URL and should be used only when you are sure it will not be reverted; its guide to consolidating duplicate URLs calls a permanent redirect a strong signal. Redirect to the closest equivalent page, not the home page by habit. Where there is no equivalent, return a real 404 or 410; compare them in 404 vs 410: which should a removed page return?. If two similar pages must stay live, a canonical tag may fit better; see Fix Duplicate URLs and Incorrect Canonical Tags. Afterwards, point internal links at the final URL and drop old URLs from the sitemap.

What success looks like: Old URLs redirect or return the intended status in one hop, and no internal link points at a removed page.

Step 7: Record, wait and review

Log a "done" date and a one-line description of each change. Google's starter guide says changes can take from a few hours to several months to show and suggests waiting a few weeks before judging. At 8 to 12 weeks, compare clicks and impressions with the previous period, and with the same weeks a year earlier if the topic is seasonal. Google notes that small position shifts are routine, so do not read too much into one week. Read the Search Console Performance Report: Clicks, CTR and Position explains the numbers.

What success looks like: A before-and-after note on each changed page, even if it says "no clear change".

A worked example

One row from a fictional audit of example.com:

URL	Type	Clicks (12 mo)	Impressions	Links in	Quality	Decision
`/blog/winter-boiler-tips-2019`	Article	12	4,100	1	1	Update first

Searchers see the page and mostly skip it. The notes say it mentions a discontinued government scheme and its title names a year long past. The decision: rewrite the facts, retitle without the year, link it from two service pages, and review it 10 weeks later. Nothing here deletes a page people still find.

Final verification checklist

The inventory combines a crawl, the sitemap and the CMS, with one row per canonical URL.
Each row has Search Console clicks and impressions over a long range, links in, and indexing status.
Every page has a quality score and a note from a person who opened it.
Every page has one decision, and the action list is ordered by risk, then impact, then effort.
Redirects reach the nearest equivalent page in one hop; removed pages without a replacement return a real 404 or 410.
Internal links and the sitemap no longer reference merged or removed URLs.
The content audit sheet is saved with dates, owners and a review date.

Common mistakes to avoid

Judging pages by traffic alone. Add a column for why each page exists.
Using too short a date range. Seasonal pages look dead off-season; use up to 16 months.
Deleting first and thinking later. Do errors, improvements and merges before removals.
Redirecting everything to the home page. Redirect to the closest match, or return a 404 or 410.
Updating dates without updating content. Google advises against it.
Auditing without owners. Name a person and a date for every action.
Ignoring pages that appear but never get clicked. These are often the cheapest wins.

Frequently asked questions

How often should I run a content audit?

A full audit once a year suits most small sites, with a lighter check on new and changed pages each quarter. Choose a rhythm you will keep.

Do I need paid tools for a content audit?

No. A crawler, Search Console, a CMS export and a spreadsheet cover the essentials. Paid tools mainly save time on large sites.

Should I delete pages with no traffic?

Not automatically. Check whether the page serves customers, has links from other sites, or is simply new. If it has no purpose, no links and no visits after a fair period, removing or merging it is reasonable. Google does not say that deleting pages improves rankings.

Will a content audit improve my rankings?

It can remove errors, duplicates and outdated information, and show where a page deserves better work. Google promises no specific result from content changes.

What is the difference between a content audit and a technical SEO audit?

A technical audit checks how search engines crawl and index the site. A content audit checks whether each page is accurate, useful and necessary.

Official references

Next step: Try the free website sample to see how your own site does on a few of these checks. This guide provides technical information, not a guarantee of rankings, traffic or index inclusion.