How to Run a Content Audit: From Inventory to Decision

A blog that has grown over several years eventually turns into an archive nobody fully remembers. Knowing how to run a content audit is what turns that archive back into an asset. An audit counts every content page, measures each one against the same criteria, and ends with a decision for every URL. The goal is not to produce more articles. It is to see which ones work, which need effort and which have become a burden.

This guide walks through goal setting, inventory building, performance matching, quality review, the decision framework, redirects and an implementation calendar. If you want the details of refreshing a single post, read our guide to updating old blog posts. This article covers something different: the whole inventory and the decision you make for each page.

How to Run a Content Audit: What It Is and When to Do It

A content audit lists all the content pages on a site, evaluates each with the same criteria and writes one action per page. An audit is not finished when the report is finished. Its output is a workable task list, and if the list stays undecided, the audit has not really happened.

Typical moments when an audit makes sense:

• You publish often enough that you struggle to remember which topics you already covered.
• Organic traffic is flat, or specific pages have dropped noticeably.
• Your site structure, brand voice or audience changed and older posts no longer match the new positioning.
• You are about to build a new content plan and want to see the current state first.
• A platform migration or URL restructure is coming and you must decide what moves.

Audit frequency depends on site size and publishing pace. A site that publishes often benefits from smaller, more frequent audits, while a slower site can run rarer but broader ones. What matters is setting a schedule and keeping to it. Auditing only after traffic drops means noticing problems late.

Setting Goals and Scope

Write down what the audit is for before you start. An audit without a goal ends in a spreadsheet nobody can act on. The goal also decides which metric counts: for one site it is search visibility, for another it is the contribution to the sales or lead pages the content supports.

Answer these scope questions first:

1. Which content types are included: blog posts, guides, category descriptions, product pages, help articles?
2. Which languages or site sections are included? A bilingual site has a separate inventory and separate performance for each language.
3. Which date range will you use for data? For seasonal topics a short window is misleading.
4. Who runs the audit and who approves the decisions?

Starting small is fine. On a large site, auditing one topic cluster or one language first lets you test the method before applying it everywhere. Once the method works, you repeat the same template for the remaining sections.

Building the Content Inventory

A content inventory is a single table that holds every page you will audit. Do not rely on one source, because different sources fill each other's gaps. A sitemap shows pages that should be live, a crawler shows pages that are actually reachable, and the admin panel shows drafts and scheduled posts. Comparing the three also surfaces forgotten or orphaned pages.

Track these fields for each page:

• URL, title, publication date and last update date.
• Content type, language and the topic cluster it belongs to.
• Author or owner.
• The main query it targets and the search intent behind it.
• Number of internal links pointing to and from the page.
• Whether it is indexable and whether its canonical points to itself.

You do not need an advanced tool for a content inventory. For a small or mid-sized site, a spreadsheet and a crawl export are often enough. As the page count grows, data export and automated merging speed things up. Whatever you pick, keep the table permanent and reuse the same columns in the next audit.

Matching Performance Data

Once the inventory exists, add performance data to every row. Content performance analysis is not about one number. It means bringing several sources together on the same URL. From the Search Console performance report take impressions, clicks and average position per page. From your analytics tool add engaged sessions, time on page and defined conversion events. Record internal and external link information in additional columns.

Keep these points in mind while matching:

• Use the same date range and the same URL format (trailing slash, parameters, language prefix) in every source.
• Report names in tools change over time. Pick the report that does the same job and do not get stuck on a menu label.
• Low data does not mean low quality. The page may answer a niche query.

Evaluating Quality and Intent Fit

Numbers show what a page does but not why. To understand why, you need a manual quality review. Read every page against the same short checklist so the review does not vary from person to person.

Questions to put on the checklist:

1. Does the page answer the intent behind its target query? If someone looking for information lands on a sales page, or a ready-to-buy visitor lands on a general guide, there is an intent mismatch.
2. Is the information current and correct? Are there outdated steps, discontinued tools or changed rules?
3. Does the page add original value, or does it repeat another page on your site?
4. Do the title, introduction and subheadings lead the reader to the right place?
5. Do the internal links to and from the page build a meaningful topic structure?

To judge intent fit, it also helps to look at which kinds of pages appear for the query in search results. You will find a detailed framework in our article on matching search intent in articles. In a quality review the aim is less to give a score and more to write one sentence about the gap the page faces. That note is used directly in the decision step.

Decision Framework: Keep, Update, Merge, Remove

Every page receives one of four decisions. Applying a fixed numeric threshold looks tempting, but the same number means very different things depending on topic, query volume and seasonality. Use criteria instead of thresholds.

• Keep: The page fits the intent, the information is current and it supports its goal. Simply continue to monitor it.
• Update: The topic and URL are right, but the information is outdated or the depth is lacking. Use the refresh guide mentioned above for the method.
• Merge: Several weak pages answer the same intent. Choosing the strongest URL and consolidating the content there is page consolidation.
• Remove: The page no longer serves the topic, the brand or the reader, and there is nothing worth updating or merging. Removal is the last resort and the most delicate part of content pruning.

Before removing anything, ask: does the page have external links, does it still bring search visibility, and can it be redirected to a relevant page? Low traffic alone is not a reason to remove a page. A new, niche or bottom-of-funnel page can be valuable even with few visits.

Imagine a fictional software blog with three separate guides answering the same question. Two are short and old, and one is more complete but poorly organized. Instead of keeping all three, a consistent decision is to update the complete one, move the useful parts of the other two into it and redirect the old URLs to it.

Redirects and Internal Link Cleanup

For every URL you merge or remove, write a redirect plan. A permanent redirect to the closest relevant page helps avoid dead ends for readers and avoids wasting the value of links that point to the old page. A mass redirect to an unrelated page misleads readers and does not help.

Check these items during implementation:

• Redirects should reach the destination in one step. Do not leave redirect chains.
• Removed URLs should be taken out of the sitemap.
• Internal links pointing to old URLs should be updated to the new URL instead of relying on the redirect.
• URLs that are truly gone and have no replacement should return an appropriate error status.

After a merge, review the internal link structure as well. Link to the merged page from related posts in the topic cluster using meaningful anchor text. We explain how internal links communicate topic relationships in our internal linking strategy article. For the broader architecture of topic clusters, the guide to building topical authority with content clusters is a useful companion.

Post-Audit Implementation Calendar

Once the decision table is ready, the biggest risk is that the list sits on a shelf. Order the work by impact and effort. On most sites, quick low-risk tasks come first, then effort-heavy updates, and merges and removals come last because redirect work needs the most care.

Follow these principles when building the calendar:

1. Assign an owner and a target week to every decision.
2. Work on the same topic cluster together. A half-finished merge damages the internal link structure.
3. After each batch, check the sitemap, redirects and internal links.
4. Write change dates into the inventory, because you will read performance differences against those dates later.
5. If you change many URLs at once, it becomes hard to separate results. Work in batches.

Take the first data reading after the period you defined in advance. The right period depends on how often the site is crawled and how much content you changed, so promising a fixed number of days would not be honest. When reading results, note other changes in the same period such as technical fixes, campaigns and seasonality. You can find the production side in our content plan guide for blog writing, and the place of auditing in a wider plan in content marketing for SEO.

Sample Template: Content Audit Decision Table

The table below shows how an inventory row moves to the decision stage. The rows come from a fictional blog and do not represent a real site. Fill it with your own data.

Sample template: content audit decision table

You can add priority and effort columns if you like. What matters is that every row ends in a single decision and that the reason is written in one sentence. A decision without a reason cannot be defended months later.

Frequently Asked Questions

How often should a content audit be run?

There is no fixed frequency. Sites that publish often may need smaller, more frequent audits, while sites with little content can audit less often. The important part is setting a schedule and keeping the inventory current.

Should I delete pages with no traffic?

Low traffic alone is not a reason to delete. First check whether the page fits its intent, whether it earns external links and whether it can be saved by updating or merging. If you do decide to remove it, plan a suitable redirect.

Which tools are enough for a content inventory?

For small and mid-sized sites, a spreadsheet, a sitemap file and a crawl export are often enough. As the site grows, data export and automated merging make the work easier. Consistent columns matter more than the tool.

Do merged pages need redirects?

Yes, permanently redirecting removed URLs to the closest relevant page is generally the right approach. Redirects should reach the destination in one step, and internal links to the old URL should be updated to the new one.

Is an audit the same as an update?

No. An audit measures the whole inventory and produces a decision per page, while an update is only one of those decisions and covers refreshing a single post. After an audit, some pages are updated and others are kept, merged or removed.

Does a small site need a content audit?

Yes, but at a smaller scale. Even with few pages, seeing which content works helps you plan the next pieces more accurately. A small inventory table and a few criteria can be done quickly.

Conclusion and Next Step

A content audit comes down to four steps: write the goal, collect the inventory in one table, evaluate performance and quality on the same page, and give each page a keep, update, merge or remove decision. Basing your criteria on intent fit, freshness and contribution rather than fixed thresholds reduces both wrongful removals and needless investment.

If your team cannot cover the updates and new articles that come out of the audit, you can look at the content writing service; sharing the first update row of your decision table as a brief is a good place to start.