How to Do a Content Audit in 2026

Most blogs do not have a content problem. They have a content accumulation problem. Year after year, posts pile up: some still earn traffic, some quietly decayed, some were written for an algorithm that no longer exists, and some duplicate each other so closely that they compete for the same searches. A content audit is how you find out which is which — and what to do about each one.

This guide gives you a complete, repeatable process: set goals, build an inventory, judge every page on evidence, decide keep, update, merge, or delete, and then repeat it on a schedule. It also covers what is new in 2026 — auditing for AI search visibility, not just Google rankings.

Key Takeaways

• A content audit is an evidence-based review of every indexed page, ending in a decision for each one: keep, update, merge, or delete.
• Judge pages on traffic, conversions, freshness, and — new in 2026 — whether AI engines cite them.
• Never delete on traffic alone: a low-traffic page may still earn links, support a cluster, or answer questions AI engines quote.
• Merging competing pages is often better than deleting either one; redirect the loser to the winner.
• Run the audit quarterly for active blogs, and re-check AI citation status each time, since AI answers change faster than rankings.

What Is a Content Audit, Exactly?

How is it different from a regular SEO audit?

An SEO audit examines your whole site — technical health, speed, crawlability, backlinks. A content audit examines your pages one by one and asks a simpler question: is this page earning its place? A technically perfect page that nobody reads, nobody links to, and no AI engine cites is still a candidate for action. The audit turns a vague feeling (“our blog feels bloated”) into a spreadsheet with a decision in every row.

How often should you run one?

For an active blog publishing several times a week, quarterly is the right cadence — frequent enough to catch decay early, infrequent enough that the work stays manageable. For a slower site, twice a year works. The trigger for an out-of-cycle audit is a traffic drop, a major algorithm update, or a site migration. If you have never audited, do it now regardless of schedule: the first audit always finds the most waste.

Step 1: Set Goals Before You Touch a Spreadsheet

What are you auditing for?

An audit without a goal produces a spreadsheet nobody acts on. Pick one primary goal and one secondary goal from this list:

• Recover traffic: find decaying pages worth refreshing.
• Improve conversions: find high-traffic pages that fail to convert.
• Reduce bloat: find thin, duplicate, or outdated pages to merge or remove.
• Build AI visibility: find pages AI engines should cite but do not — and pages they cite that deserve strengthening.

Your goal determines which metrics matter most in Step 3. A traffic-recovery audit weights recent traffic trends; an AI-visibility audit weights citation checks and answer-quality.

What counts as success?

Define it before you start, in plain numbers: for example, “refresh 20 decaying posts, merge 10 competing pairs, and remove or redirect 15 pages with no traffic, links, or citations in 12 months.” A goal like that makes the audit finishable. An audit that ends with “we should probably update some posts” has not ended at all.

Step 2: Build Your Inventory

Where do you get the full list of pages?

Export every indexed URL from three sources and combine them: your XML sitemap, Google Search Console’s pages report, and a crawl (Screaming Frog’s free version covers up to 500 URLs; larger sites need the paid licence or a platform audit tool). Search Console catches pages Google knows about that your sitemap forgot; the crawl catches pages your sitemap lists that no longer exist or redirect. Deduplicate, and you have your inventory.

What columns should the spreadsheet have?

At minimum: URL, title, publish date, last updated date, word count, organic sessions (last 12 months and last 3 months), conversions or goal completions, backlinks, internal links pointing to the page, and a notes column. Add two 2026-era columns: AI citation status (cited, not cited, or untested — see Step 3) and content type (guide, news, review, tool page, landing page). Filterable columns turn a thousand-row list into a workable queue.

Step 3: Gather the Metrics That Matter

Which traffic metrics should you look at?

Pull organic sessions for the last 12 months and the last 3 months, side by side. The comparison is the insight: a page with steady traffic is healthy; a page down sharply in the last 3 months is decaying and may need a refresh; a page with near-zero traffic for 12 months is a candidate for merging or removal — subject to the checks below. Also note conversions: a low-traffic page that converts well is more valuable than a high-traffic page that converts nobody, and deleting it would be a mistake.

How do you measure AI visibility in 2026?

This is the new part, and it is less precise than GA4 — be honest about that. For your most important pages, manually check whether AI Overviews, ChatGPT, Claude, and Perplexity cite them for their target questions. AI visibility tools can automate some of this tracking; our guide to AI visibility dashboards covers the options. Record the result per page as cited, not cited, or untested — and never record “untested” as “not cited.” A page that is not cited may need better structure, clearer direct answers, or stronger topical authority — all fixable, and all covered in our guide to structuring content for AI crawlers.

What else should you check before judging a page?

Three things that traffic alone misses: backlinks (a page with links from other sites has value even if its traffic is low — redirect, don’t delete, if you must remove it), internal link support (a page with no internal links pointing to it may be underperforming because it is orphaned, not because it is bad — fix the links before judging the content), and freshness (a page about a fast-moving topic that has not been updated in two years is decaying by default; a timeless guide from the same date may be fine). Check all three before any delete decision.

Step 4: Score Every Page and Decide

What is the keep / update / merge / delete framework?

Score each page on four questions, then apply the decision rule:

1. Does it earn traffic or conversions? (Yes / Declining / No)
2. Is it accurate and current? (Yes / Needs refresh / Outdated beyond repair)
3. Does anything else cover the same ground? (No / Yes, and this one is weaker)
4. Does it have links, citations, or a strategic role? (Yes / No)

Then decide:

• Keep — earning traffic or conversions, accurate, unique. Leave it alone, apart from routine link maintenance.
• Update — declining traffic or outdated facts, but the topic still matters and the page has authority worth preserving. Refresh the facts, improve the structure, add direct answers to question-form headings, and republish with a new date.
• Merge — two or more pages competing for the same topic or keyword. Keep the strongest URL, fold the best material from the others into it, and 301-redirect the losers to the winner. Merging also consolidates backlinks and internal links onto one page.
• Delete — no traffic, no conversions, no links, no citations, no strategic role, and nothing worth salvaging. Redirect it to the closest relevant page (or your category page) rather than leaving a 404, and remove it from your sitemap.

What are the common traps?

The biggest trap is deleting on traffic alone. A page with ten visits a month might be the page your best customers read before buying, or the page an AI engine quotes for a niche question. The second trap is updating everything: a refresh takes nearly as long as a new post, so reserve updates for pages with recoverable authority — existing rankings, links, or citations. The third trap is merging without redirecting: if you remove a page and leave its URL to 404, you throw away whatever links and history it had.

Step 5: Act on the Decisions, in the Right Order

What should you do first?

Work in this order: fix broken links and orphans found during the inventory (quick wins), merge competing pages (each merge is one redirect plus one improved page), then update decaying pages in order of recoverable value (highest previous traffic first), and finally delete and redirect the true dead weight. Doing deletions last matters: if you delete first and merge later, you may redirect a page you already removed.

How do you handle redirects properly?

Use 301 redirects, one per removed URL, pointing to the closest relevant surviving page — not to the homepage, which frustrates users and wastes link equity. After implementing, re-crawl to confirm no redirect chains or loops, and update any internal links that still point to removed URLs. A redirect is a bridge, not a bin: check it still makes sense a month later.

Step 6: Make It Repeatable

What does the quarterly checklist look like?

• Export the inventory (sitemap + Search Console + crawl) and diff it against last quarter’s list.
• Refresh traffic, conversion, and AI citation columns.
• Flag pages with 3-month traffic down sharply, pages not updated in 12+ months, and new orphans.
• Apply the keep / update / merge / delete framework to flagged pages only — you do not need to re-judge every page every quarter.
• Record decisions and outcomes, so next quarter’s audit can see whether last quarter’s updates actually recovered traffic.

How do you keep AI-era content competitive between audits?

Between audits, watch for the signals that a page’s AI standing is slipping: it stops appearing in AI answers you used to see it in, or competitors’ pages start getting cited for your topics. When that happens, the fix is usually structural rather than cosmetic — a clearer direct answer near the top, better entity coverage, or a stronger supporting cluster. Our entity SEO foundation guide and our guide to getting cited by ChatGPT both address the underlying content qualities that AI engines reward.

People Also Ask

What is a content audit?

A content audit is a systematic review of every page on your site, measured against traffic, conversions, freshness, links, and (in 2026) AI citations, ending in a keep, update, merge, or delete decision for each page.

How long does a content audit take?

It depends on site size. A 50-page blog can be inventoried and scored in a day; a 500-page site typically takes one to two weeks including the updates and merges. The first audit takes longest — quarterly follow-ups are much faster because you only re-judge flagged pages.

Should I delete low-traffic content?

Not automatically. Check backlinks, conversions, AI citations, and strategic role first. Merge it into a stronger related page if the topic still matters, and redirect rather than leaving a 404. Delete only when a page has none of those values and nothing worth salvaging.

How is a content audit different in the AI search era?

The goalposts moved: a page can rank adequately yet never be cited by AI engines, or be cited without ranking first. Audits now need an AI citation column alongside traffic, and updates should improve answer clarity and entity coverage — not just keywords and headings.

The Bottom Line

A content audit is not spring cleaning for its own sake. It is how you stop your archive from working against you: competing pages cannibalising each other, outdated advice eroding trust, and dead pages diluting crawl attention that should go to your best work. Run it quarterly, decide on evidence, redirect carefully, and your site gets smaller, stronger, and easier for both search engines and AI engines to understand. That is the whole point.

Content Audit Checklist (Copy This)

1. Set one primary goal and a numeric success target.
2. Export inventory from sitemap, Search Console, and a crawl; deduplicate.
3. Add traffic (12-month and 3-month), conversions, backlinks, internal links, freshness, and AI citation columns.
4. Fix broken links and orphan pages first.
5. Score each flagged page: keep, update, merge, or delete.
6. Merge competing pages; 301-redirect losers to winners.
7. Update decaying pages in order of recoverable value.
8. Delete only true dead weight, with redirects to the closest relevant page.
9. Re-crawl to verify redirects and internal links.
10. Record decisions and outcomes; repeat next quarter.