A website content audit is an inventory and quality review of the pages you already publish. It answers a narrow, practical question: which URLs deserve to stay, which need repair, which should be merged, and which should be retired. It is not a redesign project, and it is not a content strategy. Those come later, and only if the audit shows you need them.

An established site may contain overlapping service pages, outdated pricing explanations, or articles about discontinued offers. A content audit finds those pages and decides their fate before anyone touches the design. If the audit also reveals structural problems, it gives your website design team a clear starting point.

What a Website Content Audit Is (and What It Is Not)

A content audit covers existing pages only. You are evaluating what is already live, not imagining what could be. That constraint is what makes it useful: it produces decisions about real URLs, not a wish list.

Three things it is not:

  • Not a redesign project. A redesign changes structure, templates, navigation, and visual system. An audit changes your understanding of content. You can run a complete audit and change nothing structural. If you find that your service pages are fine but your navigation buries them, that is a signal to open the website redesign checklist, not to rewrite every page.
  • Not a content strategy. Strategy decides what you will publish next quarter and for whom. The audit decides what already exists and whether it earns its place.
  • Not an SEO report. Search data informs the audit, but ranking positions alone do not settle whether a page is accurate or useful. A page can rank and still misstate what you sell.

Google's guidance on creating helpful, reliable, people-first content frames the standard well: ranking systems are designed to prioritize information created to benefit people, not content built to manipulate rankings. That is the lens for every keep-or-fix call you make.

Build the Inventory: URLs, Titles, Topics, Audiences, and Last-Updated Dates

Start with a raw list. Export your sitemap, or crawl the site, or pull URLs from Search Console. Do not filter yet. Messy input is fine; missing pages are not.

For each URL, record the minimum metadata before you judge anything:

Field Why it matters
URL The unit of decision. One row, one page.
Page title (H1 and title tag) Shows whether the page announces its topic clearly
Topic Groups overlapping pages you may later consolidate
Intended audience Reveals pages written for nobody in particular
Last updated Flags stale service facts and outdated claims
Primary buyer question Forces you to state what the page is for
Current search entrances Tells you what the page actually does today

Watch for URL variants before you count pages. A tracking parameter may create a second spreadsheet row for the same content, while an old campaign URL may deserve its own row because it is still reachable. Check the actual page as well as the CMS date: a visible "updated" label does not tell you which service facts changed.

Judge Each Page: Buyer Questions, Service Facts, and Source Accuracy

This is the part most audits skip. Traffic numbers tell you a page is visited. They do not tell you it is correct.

Score each page on three questions:

1. Does it answer a real buyer question? Not a keyword. A question a person would actually ask before contacting you. "How long does implementation take?" is a buyer question. "Enterprise implementation solutions" is a phrase.

2. Are the service facts accurate? Check every claim about what you do, what you include, what you do not do, and what a buyer must provide. This is where audits earn their cost. Service facts drift: a process changes, a deliverable is dropped, a partner relationship ends, and the page keeps describing the old version. Assign a named person inside the company to sign off on each service page. If nobody can confirm a fact, that page is not ready to keep.

3. Are sources verifiable? If a page cites a statistic, a regulation, or a technical specification, the reader should be able to check it. Pages that assert numbers with no source are a liability, and Google's helpful-content guidance explicitly asks whether content presents information in a way that makes you want to trust it, such as through clear sourcing.

A page that fails on accuracy should never be classified as "keep" regardless of how much traffic it receives.

Check Page Purpose, Search Entrances, and Analytics Signals

Every page should have one job. Write it down in the worksheet: "This page exists to help a facilities manager compare two service tiers." If you cannot write the sentence, the page has no purpose and the classification becomes easier.

Then look at how the page is found and used. Search Console reports search impressions, clicks, and query data for eligible searches; it does not identify an individual visitor's exact journey. Analytics records on-site activity using its own measurement rules. Google's documentation on using Search Console and Google Analytics together explains why the two views can help you understand discovery and site experience together.

The two tools use different metrics and will not match exactly. Search Console clicks and Analytics sessions are the most comparable pair, so use those for a general pattern rather than chasing reconciliation.

One case deserves its own rule: pages with search entrances that match no real buyer question. These are common — an old comparison post, a glossary entry, a news item ranking for an unrelated term. Do not default to "keep" because the numbers look healthy. Record the mismatch and decide deliberately: rewrite toward a real question, consolidate into a page that does, or retire.

This is also where SEO discipline matters. SEO, per Google's SEO Starter Guide, is about helping search engines understand your content and helping users find your site. It is not a guarantee of ranking, and Google states plainly that no set of changes will automatically put a site first. Audit decisions should reflect that; there is no trick that rescues a page that answers nothing.

Classify Every Page: Keep, Improve, Consolidate, or Retire

Four outcomes, one per URL:

  • Keep — accurate, purposeful, answers a buyer question. Leave it alone.
  • Improve — right topic, wrong execution. Thin sections, stale facts, unclear headings, missing next step.
  • Consolidate — two or more pages covering the same topic. Choose the page that will answer the question best, preserve useful material, and map any removed URLs to a genuinely relevant destination. Record their current search queries and links so you can check the change afterward.
  • Retire — no current purpose and nothing worth preserving. Review links and traffic before removal; redirect only when there is a closely matching replacement. Otherwise, let the removed URL return an appropriate missing-page status.

Write the reason in the worksheet for every classification. "Keep — verified with sales, June" is a decision. "Keep" alone is a guess.

Filled Illustrative Worksheet: A B2B Example

The following is a hypothetical example for a fictional industrial equipment servicing company. It is illustrative only — not a client case, not a performance result.

URL Title / Topic Audience Updated Buyer question Purpose Verdict Reason
/services/preventive-maintenance/ Preventive Maintenance Programs Plant managers 2024-11 What does the maintenance schedule include? Explain tiers and intervals Keep Facts verified with operations; answers the main pre-sales question
/services/maintenance/ Maintenance Services Plant managers 2021-03 (unclear) None stated Consolidate → /services/preventive-maintenance/ Overlaps the page above; older, thinner, no unique facts
/blog/reduce-downtime-tips/ 7 Tips to Reduce Downtime Mixed 2022-08 How do I reduce unplanned stops? Attract early-stage readers Improve Real question, but two tips reference discontinued parts; needs rewrite and a link to the maintenance page
/pricing/ Pricing Buyers 2023-05 What will this cost? Set expectations Improve No figures and no explanation of what drives cost; currently answers nothing
/news/2020-trade-show/ Trade Show Recap 2020 — 2020-10 None None Retire Event passed; check inbound links before removing; no unrelated redirect
/glossary/mean-time-between-failures/ MTBF Definition Engineers 2024-02 What is MTBF? Define a term Keep Accurate, cited, and a genuine entry point for technical readers

The example shows why a single traffic threshold is inadequate. The older maintenance page overlaps another URL, while the glossary page has a narrow but valid job. Your own mix may look quite different.

Accessibility and Page Structure Checks During the Audit

Add structure to your criteria, not just to your checklist. The W3C's guidance on page structure states that well-structured content allows more efficient navigation and processing, and that headings should be nested logically to label sections according to their relationships and importance.

In practice, during the audit, check:

  • A clear primary heading that describes the page's actual topic
  • Heading levels that express the relationships between sections, rather than being chosen for font size
  • Page regions marked up so screen reader and keyboard users can skip to main content
  • Content marked up with meaningful elements rather than styled text

Record a structure problem alongside the content verdict so the person editing the page can address both. A confusing heading sequence is a usability issue even when the wording itself is accurate.

What to Do After the Audit (Without Turning It Into a Redesign)

Sequence the work in this order:

  1. Fix inaccurate service facts on pages buyers currently use. Assign an owner and publish the corrected wording.
  2. Improve weak answers where the page already has a clear purpose. Sometimes one section needs repair; sometimes the whole page does.
  3. Consolidate overlapping pages after choosing the destination and mapping relevant URLs. Check search entrances and links after each merge.
  4. Retire obsolete pages after reviewing links and deciding whether a genuinely relevant replacement exists.

Only after all four steps should you ask whether the site needs structural change. If the audit shows your content is sound but your templates, navigation, or page hierarchy are the problem, that is a redesign conversation — start with the website redesign checklist. If the audit shows your pages are accurate and purposeful but not being found, the issue is visibility, and improving website SEO is the right next document. And if you are planning a new site rather than auditing an old one, good development processes begin with planning and requirement confirmation before any build work — the same discipline an audit applies to what you already have.

For a B2B firm, the value is a defensible decision for each URL. The spreadsheet is only the record. The harder part is asking the people responsible for the offer whether the page still describes what a buyer can actually purchase.

FAQ

How do I conduct a website content audit?

Inventory every URL and record its title, topic, intended audience, last-updated date, primary buyer question, and current search entrances. Then evaluate each page for buyer usefulness, factual accuracy, and a clear stated purpose, checking service claims with someone inside the company who can confirm them. Finally, classify each URL as keep, improve, consolidate, or retire, and write the reason for the decision in the worksheet.

Can I do a website audit myself?

Yes. A content audit can be run in-house with a spreadsheet, a site crawl or sitemap export, and access to Search Console and Analytics. The requirements are consistent criteria applied to every page and at least one person who can verify whether your service facts are still true. You do not need a specialist tool, though a crawler saves time on larger sites.

What should be included in a website audit?

At minimum: URL, page title, topic, intended audience, last-updated date, search entrance data, stated page purpose, the buyer question the page answers, the service facts it states, whether its sources are verifiable, accessibility and heading structure notes, and a keep/improve/consolidate/retire decision with a recorded reason.

How is a content audit different from a redesign?

An audit evaluates existing pages and produces keep/fix/merge/retire decisions. A redesign changes structure, templates, navigation, and visual design. You can complete an audit without changing any of those, and doing so usually tells you whether a redesign is warranted at all.

Should I audit pages that get traffic but no leads?

Yes, and treat them as a distinct category. Record the mismatch between the search entrance and any real buyer question, then decide deliberately whether to rewrite the page toward a genuine question, consolidate it into a page that answers one, or retire it. Traffic alone is not a reason to keep a page.

Sources