Content Audit: How to Review and Score Every Page

Short answer: A content audit is a structured review of every page on your site. Build an inventory of all addresses with their traffic, links, indexing status and basic quality checks, give each page a simple score, and assign one action: keep, improve, merge, redirect or remove. Start with the pages that matter most to the business, record the reason for each decision and repeat the audit once or twice a year so that the site does not fill with pages that nobody needs.

Sites grow by addition. Every campaign, product and idea adds pages, and few are ever reviewed. After a few years, the best content sits beside outdated guides, near-duplicates and thin pages that nobody visits. A content audit brings order. It tells you what you have, how each page performs and what to do about it, so that effort goes to the pages that can improve and not to those that cannot. This guide describes a practical method that works for a small blog or a large shop. For the narrower task of removing weak pages, see the content pruning guide.

Set the goal and the scope

Begin by deciding what the audit is for. You might want more organic traffic, fewer duplicate pages, better conversions or a cleaner site before a redesign. The goal shapes the checks. Then define the scope: the whole site, one section, one language or one type of page such as blog posts. A smaller scope finishes faster and produces action sooner. Write down the date, the scope and the person responsible, so that the next audit can be compared with this one.

Build the inventory

List every address that should exist on the site. Combine several sources: a crawl of the site, the sitemap, your content management system and the performance report from Search Console. Pages that appear in one source but not another are interesting in themselves: addresses in the sitemap but not found by the crawl may be orphans, and pages that get traffic but are not in the sitemap may be missing from it by mistake. Put the list in a spreadsheet with one row per address. Keep it as a living file, because you will use it again. The idea of orphan pages is explained in orphan pages: how to find them.

Add the data that matters

Add columns for the facts you need to decide. Useful ones are page type, title, word count, date published and last updated, indexing status, organic clicks and impressions over the last twelve months, internal links pointing to the page, external links, conversions or goal completions where you track them, and whether the page has an obvious problem such as a missing title or a status error. You do not need every column for every page. Choose a handful that connect to your goal, fill them in by export where possible and avoid manual copying, which creates mistakes.

Score each page with a simple method

A score makes hundreds of decisions manageable. Keep it simple, for example one to three points for each of four questions: does the page get visits, does it serve a clear purpose, is the content accurate and complete, and is it technically healthy. Add the points and group the pages: high scorers are protected, middle scorers are candidates for improvement, and low scorers need a decision. A score is a guide, not a verdict. A page with no traffic may still be essential, such as a legal page or a support article. Mark such exceptions in a notes column so that they are not removed by mistake.

Judge quality honestly

Traffic data shows what happened, not what a page deserves. Read a sample of the pages yourself. Ask whether the page answers a real question, whether the facts are current, whether it adds something beyond what any competitor says, and whether an expert would be comfortable putting a name on it. Check the writing for padding, repeated text and outdated references. Compare pages that target the same topic, because two weak pages can often become one strong one. The signs of low-value pages are described in the thin content guide.

Choose one action per page

Every page gets one of five actions. Keep it as it is when it performs and is accurate. Improve it when the topic is right but the content is weak, old or incomplete; this is where most of the gains are. Merge it when several pages cover the same topic and redirect the weaker ones to the best. Redirect it when it has links or traffic but a better page exists. Remove it, with a not found or gone response, when it has no value, no links and no purpose. Add the reason in a short note, because the audit will be questioned later and a reason saves repeating the work. The method for refreshing is in how to refresh old content.

Look for gaps as well as problems

An audit that only removes pages leaves the site smaller but not better. While you review, note the topics that your audience needs and you do not cover. Look at queries in Search Console that bring impressions but no matching page, questions from customers and sales calls, and topics where competitors have a page and you do not. Add these to a list of new pages, ranked by value. A content audit and a gap analysis together give you a plan for both fixing and growing, as explained in content gap analysis.

Turn the results into a plan

List the actions in order of effort and expected value. Quick wins come first: fixing titles, merging obvious duplicates and updating pages with old dates. Larger rewrites follow, with an owner and a date for each. Put a limit on the work in progress, since an audit with five hundred open tasks will not be finished. After the changes, update internal links, the sitemap and the redirects, and request a fresh crawl. Track the results after four to eight weeks and note what changed, so that you learn which actions pay off for your site.

Make the audit a habit. Review a section each quarter instead of the whole site once in five years, and keep the inventory up to date as you publish. New content should enter the spreadsheet with its goal, owner and review date. Agree on simple publishing rules, such as one page per topic and a check for existing pages before writing a new one, because prevention is cheaper than clean-up. Share the results with the team, so that writers learn which pages succeed and why.

A worked example shows how this looks in practice. Imagine a site with four hundred pages. The crawl and the performance report show that sixty pages bring most of the organic visits, ninety pages bring a few visits each, and two hundred and fifty pages bring almost none. Reading a sample of the quiet group reveals three patterns: old news posts that were never relevant after the week they were written, several near-identical guides on the same topic, and useful pages that nobody links to. The plan follows from the patterns. The old news posts are noindexed or removed, the near-identical guides are merged into one stronger page with redirects from the others, and the useful pages gain internal links from related articles. The sixty strong pages are refreshed first, because small gains there are worth more than large gains elsewhere.

Be careful with the people side of an audit. Writers and owners may feel attached to pages, and a decision that looks obvious in a spreadsheet can be sensitive in a team. Share the criteria before you share the verdicts, ask the owners of borderline pages for context and agree on a date for the final decision. Keep a log of what was removed, merged or redirected, with the old and new addresses, so that anyone can trace a change later. This also protects you if traffic moves after the audit and someone asks what was done.

Site SEO AI Audit crawls your site and lists pages with thin content, duplicate titles and descriptions, missing headings, broken links, orphan pages and deep click depth, which gives you a technical starting point for the inventory. It does not judge whether your content is accurate or useful to readers; that remains an editorial decision. The first audit of up to 200 pages is free; larger sites can see the pricing page.

The bottom line

Build a full inventory, add a few useful data points, score each page, read a sample honestly and give every page one action with a reason. Fix first, then fill the gaps, and repeat on a schedule.

FAQ

How often should I run a content audit?

Review the whole site once or twice a year, or review one section each quarter if the site is large.

Should I delete pages with no traffic?

Not automatically. Check links, purpose and topic first. Improve, merge or redirect a page before you remove it, and keep essential pages such as legal or support content.

Which data do I need for an audit?

A crawl or sitemap list, organic clicks and impressions, indexing status, internal and external links and, where possible, conversions.

How long does a content audit take?

A small site can be reviewed in days. A large site takes weeks, so limit the scope and start with the most valuable sections.

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

A technical audit checks how pages are built and crawled. A content audit judges whether each page deserves to exist and how to improve it. Use both.