Content Audit: How to Decide What Your Blog Should Keep, Update, or Remove

Old blog posts can quietly waste readers’ time, send people to discontinued products, or compete with better pages on your own site. A content audit fixes that by giving each page a clear decision: keep it, improve it, combine it with another page, or remove it.

You don’t need expensive software or a complete site redesign to start. You do need a reliable page list, a few useful signals, and enough context to avoid deleting an article just because it had a quiet month.

Start your content audit with a useful inventory

Pick a manageable section of your site first. A small business might review its service pages and supporting articles; a publisher might start with one topic category. Auditing everything at once sounds efficient, but it often produces a large spreadsheet nobody has time to act on.

Export a list of published URLs from your content management system if it offers that option. A sitemap can also help, although it may omit pages or include URLs that no longer reflect what’s published. Compare the list with your site navigation and any analytics reports you already use. The goal is a practical working list, not a perfect census.

Give each page one row. Start with these columns:

• URL and page title
• Content type and main topic
• Original publication date and last substantive review date
• Purpose, such as answering a question or generating inquiries
• Available performance signals and the date range used
• Proposed action, owner, and review status

Keep the original export intact and work from a copy. That makes it easier to spot accidental changes or return to your starting point. If your spreadsheet needs cleanup first, the guide to cleaning messy spreadsheet data without losing the original covers a sensible way to preserve it.

Don’t assume the date shown on a post tells you when someone last checked its claims. A formatting change is not a factual review. If you can’t verify the last review, mark it as unknown rather than guessing.

Measure usefulness before judging traffic

Traffic is a starting point, not a verdict. A popular tutorial with outdated instructions may need urgent work. Meanwhile, a little-read page answering a specialized customer question could save your team repeated support calls.

Use the signals available to you, but record their limits. Page views show visits, not whether the reader got an answer. Search impressions can show that a page appears in results, but they don’t prove that its content is accurate. A contact form submission may be valuable, though the visitor might have read several pages before sending it.

Compare a meaningful period with the same period before it where your tools allow. Seasonal content deserves particular care: a holiday planning guide should not be judged solely on its performance in spring. If tracking was recently installed or changed, note that beside the numbers.

Then read the page. Check its opening promise, instructions, links, examples, screenshots, and calls to action. Look for details that have changed, claims with no support, or advice that leaves out a necessary step. Ask someone who handles customer questions what readers still struggle with. Their observations won’t replace data, but they can explain it.

For business pages, separate attention from outcomes. A service article that attracts few visitors but brings qualified inquiries may be more useful than a broad article with many visits and no connection to your work. If you use campaign tags, a consistent UTM tracking system can make promotional visits easier to interpret, provided you don’t mistake tagged traffic for the whole audience.

Choose an action for each page

A content audit becomes useful when it leads to decisions. Use these four labels, but add a short reason beside each one. “Update because the screenshots no longer match the product” is much more actionable than “needs work.”

Keep pages that still do their job

Keep a page when its information is accurate, its purpose is clear, and it serves a reader or business need. It doesn’t have to be a traffic star. A stable policy explanation or an old article with continuing reference value may need only a scheduled check.

Keeping a page is still a decision. Record when it should be reviewed again and who owns that review. For fast-changing product instructions, that date may come sooner than it would for a general educational article.

Update pages with a sound core

Choose an update when the topic still matters and the existing URL is a good home for the answer. Fix the substance first: verify claims, replace obsolete steps, remove unsupported recommendations, and add missing context. Rewrite the headline or opening only if they no longer match what the page delivers.

Don’t change the publication date merely to make an article look fresh. If your site displays an updated date, use it to reflect a meaningful review or revision. Readers should be able to trust what that date implies.

Combine pages with overlapping jobs

Combining works when two pages answer essentially the same question and neither needs to stand alone. Choose the stronger destination based on relevance and usefulness, not traffic alone. Move the best material into that page, edit it into a coherent article, and plan what will happen to the retired URL.

Overlap doesn’t always mean duplication. A beginner’s overview and a detailed troubleshooting guide can cover related ground while serving different needs. Keep both if each has a distinct purpose, then link between them so readers can choose the right level of detail.

Remove pages with no useful role

Removal makes sense for an expired promotion, a duplicate test page, or advice you can’t responsibly maintain. Before deleting, check for incoming links, bookmarks, internal links, and any business process that relies on the URL. A page with little search traffic can still be linked from an email or customer document.

Never redirect every deleted page to your homepage by default. If a genuinely relevant replacement exists, send visitors there. If there isn’t one, a clear unavailable-page response may be more honest than sending people somewhere unrelated. The practical details are covered in the website redirects guide.

Work through one realistic example

Assumptions: A fictional home-organizing business has three articles about preparing for a move. The figures below are invented for this example, not benchmarks. During the same six-month period, the articles receive 900, 250, and 80 visits. The business also tracks inquiry forms, though it cannot prove which page caused each inquiry.

The 900-visit article promises a moving checklist, but several links point to products the company no longer recommends. It records two inquiries. The 250-visit article covers the same checklist in greater detail and records four inquiries. The 80-visit article explains how to prepare fragile family keepsakes, a narrower subject that staff say clients ask about.

Here’s a reasonable plan:

1. Combine the two checklist articles. Use the more detailed page as the destination if its URL and content fit the intended guide. Bring over any useful sections from the popular page, fix the obsolete links, and redirect the old URL to the revised guide.
2. Keep the keepsakes article separate. Its audience is smaller, but its purpose differs. Check the advice for accuracy and link to it from the moving checklist.
3. Record the baseline. Save the visit and inquiry counts for both checklist URLs before making changes. Note the date of the revision and redirect.

Afterward, compare the destination page’s results with the two pages’ combined baseline over a comparable period. Don’t add the old page’s later visits again if your reporting attributes redirected visits to the destination, since that could count the same traffic twice. Check how your tools report redirects before drawing a conclusion.

The four inquiries on the detailed article are encouraging, not proof that its wording generated every lead. The business should also inspect the inquiries themselves: Were they from people seeking the service it offers? A smaller number of relevant requests can matter more than a larger number of poor matches.

Prioritize fixes without creating a backlog

Not every page needs attention this week. Start with inaccurate or potentially harmful information, broken paths to an important service, and pages that people use frequently. Next, look for updates that solve a clear reader problem without requiring a complete rewrite.

A simple priority note can combine three judgments: reader impact, business value, and effort. You don’t need a complicated score. Mark a broken booking page as urgent; schedule a useful but dated tutorial; leave a sound reference article alone until its next review.

Assign one person to make each decision and another to review specialist claims when necessary. On a small site, that may be the same person for most pages. For legal, financial, medical, or safety-sensitive material, involve a qualified reviewer rather than treating an editor’s confidence as evidence.

Set a realistic batch size. Completing and checking five substantial updates is better than marking fifty pages “in progress” and leaving them half revised. Your content audit sheet should show the action, responsible person, target date, and actual completion date.

Protect readers when changes go live

Before editing or removing a page, save a copy of its current content and record its URL. For a major consolidation, keep notes on which material moved and why. This gives your team a way to investigate problems without reconstructing the original from memory.

After publication, test the old and new addresses in a browser. Follow the redirect if you created one, check that the destination answers the original request, and repair internal links that still point to retired pages. Review navigation, forms, images, and important links on the revised page as well.

Give the change time to produce useful evidence, then review it against the baseline you recorded. Look for broken referrals and reader complaints alongside visits and inquiries. Search visibility and business results can fluctuate for reasons unrelated to your edit, so avoid declaring success or failure from a single short interval.

Finally, build maintenance into the publishing process. Give every new article an owner and a review trigger, such as a product change, a recurring customer complaint, or a scheduled date. A content audit should reduce future cleanup, not become a once-a-year emergency.

Final Verdict

Run a focused content audit and make a documented decision for every page you review, using reader usefulness before traffic as the deciding test. Update sound pages, combine genuinely overlapping ones, and remove material that no longer has a responsible purpose. Today, export one category of URLs and add columns for each page’s purpose, proposed action, and owner.

Frequently Asked Questions