How to Do a Website Content Audit in 2026

Website content audit dashboard showing webpage rows reviewed with analytics data and marked to keep, rewrite, or remove.

A website content audit is a page by page review of every URL on your site that ends in one decision per page. Keep it, rewrite it, or remove it. You pull crawl data, Google Search Console data, and Google Analytics data into one spreadsheet, review each page against that data, and then act on the pages that are dragging you down. At TJ Digital we run a comprehensive content audit for every client we take on, currently around 42 businesses, because cleaning up page level quality problems tends to lift the pages you actually care about.

Here is why that works. If you have hundreds or thousands of pages, some of them are not that great. Or at the very least, Google sees them as low quality. And if Google sees a lot of pages on your site as low quality, it can affect how it sees the whole site. Google says its ranking systems are designed to work mostly at the page level, but it also confirms that site-wide signals and classifiers feed into how it understands individual pages. Clean up the page specific issues and you can improve Google’s read on your site overall, which can help all of your pages rank better.

Below is our exact process.

What data do you need to start a content audit?

Start by pulling in every piece of data you already have access to. You want a tool like Ahrefs, data from Google Search Console, and data from Google Analytics. Each one tells you something the others cannot.

SourceWhat to pullWhy it matters
Ahrefs (or any site crawler)URLs, H1s, meta titles, internal links, external links, word count, backlinksEstablishes what actually exists on the site and flags pages that have link equity worth protecting
Google Search ConsoleClicks and impressions per page, queries by page, plus every URL listed as crawled not indexed or discovered not indexedShows whether Google is surfacing the page at all, and separates a content problem from an indexing problem
Google AnalyticsViews by pageIdentifies important pages that are getting used even though they receive little or no organic traffic

The queries by page piece is the one most people skip, and it is the most useful part. Impressions tell you a page is already ranking somewhere for a term. Clicks tell you whether anyone is choosing it. Those are two very different problems with two very different fixes.

Google recommends using both together for exactly this reason. Search Console measures what happens in Google before the visit. Analytics measures what happens after. The numbers will not match, and they are not supposed to.

Have Claude or ChatGPT put all of this into one spreadsheet you can work off of. One row per URL, one column per data point.

@tjrobertson52

How to decide which pages to delete from your website: if Google sees enough of your pages as low quality, it starts seeing your whole site that way. #SEO #ContentAudit #TechnicalSEO

♬ original sound – TJ Robertson – TJ Robertson

How do you pull SEO data into Claude or ChatGPT?

Use MCP. Model Context Protocol is an open standard that lets an AI application pull data directly from an outside tool instead of relying on CSVs you exported an hour ago.

If you have Ahrefs, the Ahrefs MCP server connects to Claude, ChatGPT, and other MCP compatible apps, and it can pull both Ahrefs data and your connected Google Search Console data. No code required on your end.

The other two connections work a little differently:

  • Google Analytics has an official MCP server from Google.
  • Google Search Console does not have an official MCP server. Google publishes a Search Console API, and the MCP servers you will find for it are community built wrappers around that API. So either use the Ahrefs MCP to get at your Search Console data, or find or create your own.

One warning about doing this with AI. MCP is plumbing. It moves the data faster and it decides nothing for you. If you let a model dump Search Console clicks and Analytics sessions into a single “traffic” column, you will end up with a clean looking spreadsheet that is quietly wrong. Tell it to keep the source labels on every metric.

How do you decide whether to keep, rewrite, or remove a page?

Keep a page when it still serves an audience, rewrite it when the topic matters but the page does not deliver, and remove it only when nothing on the page is worth saving. Traffic is what tells you which pages to look at. Usefulness, search demand, backlinks, and indexing status are what decide the action.

At this point it would be great if I could hand you a set of hard and fast rules. But site audits are complicated, and the spreadsheet by itself is not going to tell you everything you need to know. You need Claude or ChatGPT to actually look at each of these pages and make a recommendation, and then you need to review those recommendations yourself. Do not remove pages from your website lightly.

Here are the general guidelines we work from.

Pages getting very little traffic from Google. Consider removing or rewriting them. If the topic is one you think would be useful to your audience, rewrite it, especially if there are not many words on the page. Low traffic on its own is not proof of low quality. The page might cover a topic with little search volume, or serve existing customers, or be stuck behind an indexing problem.

Pages you are already proud of that are already optimized. Leave the content alone and point more internal links at them.

Pages on topics your audience does not need. Remove them. If the page was getting any traffic at all, or has any external links pointing at it, redirect it to a similar page first.

Google is blunt about this. It calls deleting content a last resort and says to improve what can be improved first. Google also says outright that removing a pile of old content to make your site look fresher will not improve your rankings.

ActionWhat supports it
KeepThe page serves a clear audience or business purpose, the information is accurate, and it has links, conversions, or direct traffic even if search traffic is low
RewriteThe topic still matters, the page has impressions or rankings or backlinks, and the content is thin, outdated, or poorly matched to what the searcher wanted
MergeTwo URLs satisfy the same search intent and are splitting traffic, links, and internal attention between them
Remove and redirectThe content no longer deserves its own URL, but a closely related page is a fair successor
Remove and 404The page is gone and nothing on the site is a reasonable replacement
Keep but noindexThe page has a job on your site but no business appearing in search results, like a thank you page

Two numbers get used as pruning rules that should never be pruning rules. The first is word count. Google has said plainly that it has no preferred word count and that there is no ideal page length. A 300 word page that fully answers a narrow question beats a 3,000 word page padded out to hit a number. The second is age. An old evergreen page that still answers its question can stay. Old content becomes a problem when it becomes inaccurate or redundant.

What if two pages target the same topic?

If you have two pages targeting the same topic, keep the URL that is getting more search traffic, consolidate all of your best content onto that one page, and redirect the removed page to it.

That only applies when both pages are doing the same job. Two pages showing up for some of the same queries is not automatically a problem. A guide on how to choose running shoes, a running shoes category page, and a single product page all touch the same subject while serving completely different intents. Merging them would cost you coverage. What you are looking for is two URLs doing the same job, where rankings keep flipping between them and the links are split.

Once you pick a survivor, do the full job:

  • Pull the best unique sections from the weaker page into the stronger one rather than gluing the two articles together.
  • Set up a permanent redirect from the retired URL.
  • Update your internal links so they point at the surviving URL directly instead of running through the redirect.
  • Update the canonical tag and your sitemap. Google treats redirects and rel=”canonical” as strong canonical signals, which is how the links pointing at the old URL get consolidated into the new one.

How should you redirect the pages you remove?

Every redirect should point to the most similar page you actually care about.

Please do not redirect all of your removed pages to the homepage. Google specifically warns against sending a batch of old URLs to one irrelevant destination, and it may treat those redirects as soft 404s anyway. You get nothing and you annoy the person who clicked.

The logic is simple:

  • Direct replacement exists: 301 to it.
  • Several pages merged into one: 301 all of them to the survivor.
  • Nothing on your site is a fair successor: let it 404 or 410. An honest dead end beats a misleading redirect.
  • The duplicate has to stay live for users: canonical tag instead of a redirect.

Keep redirects in place for at least a year so Google has time to recrawl the old URLs and move the signals over. And point them straight at the final destination rather than building chains.

Does cleaning up low-quality pages actually improve rankings?

Cleaning up low-quality pages improves rankings when it makes the website better for the people reading it. Google gives no bonus for having fewer URLs.

A content audit moves the needle when it removes material that was written for search engines rather than people, resolves duplication that was splitting your links and rankings, consolidates signals into the right canonical URLs, and leaves a reader with a clearer set of pages that answer their question. Google has said that when a whole section was built for search engines and cannot be salvaged, removing it can help the good content perform better.

Measure it instead of assuming it. Record a baseline for the pages or topic clusters you are touching, make changes in batches, then compare clicks, impressions, CTR, and position afterward. Give it time. Google says it can take months for its systems to confirm that a site is consistently producing useful content.

What else should you audit alongside your content?

An internal link audit and a title tag audit. Both are separate jobs from the content audit, and both are worth doing in the same cleanup effort.

  • The internal link audit looks at how authority flows between your pages and which pages are starved of links.
  • The title tag audit checks whether your H1s and meta titles lead with terms people actually search.

Run the content audit first. It is hard to make good internal linking decisions when you do not yet know which pages are staying.

Want us to run the audit for you?

We do this for every client we onboard, and it is usually one of the first things that moves the numbers. If you would rather hand it off, join the waiting list and tell me a little about your site.