Content Audit: How to Test a Blog Clean-Up Safely Before Changing Everything
A clinic group with a huge library of weak blog posts needed to clean up, but the owner was nervous. Deleting or merging hundreds of pages felt risky. What if traffic fell further? The answer we suggested was to start small, test carefully and stabilise before aiming to grow.
A content audit does not have to be a leap of faith. This article explains how to run one in stages so you can see what works before committing to the whole plan.
Run a content audit to stabilise before you grow
When traffic and visibility are falling, the first goal is to stop the slide. Growth comes after. Chasing new content while old problems remain is like filling a bath with the plug out. A calm, staged clean-up gives you a firm base to build on.
Choose a small test group
Pick a modest number of posts, perhaps a couple of dozen, that represent the wider set. Include a mix: some you plan to improve, some to merge and some to remove. Keep a similar group untouched for comparison. This is your test bed.
Record a baseline first
Before changing anything, note the traffic, impressions, clicks and rankings for the test posts, and for the comparison group. Save the figures with dates. Without a baseline, you cannot tell whether changes helped or hurt. Our performance reporting approach begins with exactly this step.
Make the changes and wait
Apply your planned changes to the test group, including proper redirects for anything removed. Then give it time. Google can take weeks to reassess, so avoid judging too early. Resist the urge to change other things at the same time, or you will not know what caused any movement.
Compare and learn
After a few weeks, compare the test group with the untouched one. Did the improved pages gain? Did merged pages hold or rise? Did removals cause any harm? The results tell you whether to proceed, adjust or pause. You are making decisions on evidence, not fear.
Watch for unexpected effects
Merging or removing pages can shift traffic between others, and not always in the way you expect. Watch the whole set of pages, not just the ones you changed. If something drops that you did not touch, look for links, redirects or overlapping topics that explain it.
Involve the right people
A content clean-up touches editors, developers, clinicians and managers. Agree who signs off on removals, who sets up redirects and who checks medical accuracy. A clear owner for each task keeps the project moving and stops decisions stalling.
Scale up in stages
If the test goes well, expand the clean-up in batches. Review results after each. This keeps risk low and lets you correct course. It also builds confidence across the team and with the owner, since progress is visible.
Keep a clear record
Log every change with its date and reason. A simple spreadsheet is enough. If something unexpected happens, you can look back at what changed. It also helps anyone who takes over the work later.
Where the real growth comes from
Once stable, focus on quality: pages that answer real patient questions, backed by clinical review. Link them to the relevant service pages. Our article on service pages for clinics explains why those pages matter most.
Share the plan with the owner
A nervous decision-maker is reassured by a clear plan. Show the test design, the baseline, the timescale and what would count as success or failure. Agree in advance what you will do in each case. Knowing the rules removes much of the anxiety.
Keep quality control simple
Choose a short checklist for every page you keep or rewrite: accurate, clear, helpful, linked to a service page and reviewed by a clinician. Use it every time. Simple, repeatable checks are easier to maintain than complicated ones, and they keep standards high as the library grows.
Keep a change log
Keep a log of the dates when you made changes, and compare it with traffic. This makes it much easier to understand movements later. Many teams forget what changed and when, and end up guessing. A one-line note per change solves that.
Prepare for mixed results
Some pages will improve, some will not, and a few may dip briefly. That is normal in any test. Judge the group overall, look for patterns and be ready to adjust. A calm, measured response is more useful than an emotional one.
Share results with the wider team
Explain the test, the result and the next step to everyone involved. A short update builds confidence, and it stops rumours about traffic. When people understand why pages are changing, they are more likely to support the work and to follow the new standards.
A simple test plan
- Pick a test group and a comparison group.
- Record the baseline.
- Make the changes, with redirects.
- Wait and compare after a few weeks.
- Roll out in stages.
Our companion article on thin content on clinic blogs explains why a clean-up helps. If you would like support, we are glad at Pulse Digital Health to talk.
Frequently asked questions
What is a content audit?
A structured review of your pages that decides which to keep, improve, merge or remove, based on quality and performance. Include a mix in the test group: pages you plan to improve, pages you plan to merge and pages you plan to remove. A mixed group tells you more than a uniform one.
Is it safe to delete blog posts?
It can be, if you audit first, use redirects and proceed in stages. Testing on a small group first lowers the risk. Choose a group that reflects your whole library, so the results tell you something useful about the rest. A representative sample makes the results meaningful.
How big should a test group be?
Large enough to be representative, perhaps a couple of dozen posts, with a similar untouched group for comparison. Record how long you waited and why, so future tests use the same standard. Recording your reasoning helps future tests.
How long should I wait before judging the results?
Several weeks, since Google needs time to reassess. Avoid changing other things meanwhile. Note anything else you change during the test, since it could explain differences in the results. Extra changes muddy the picture.
Why stabilise before trying to grow?
Because new content will not help if existing problems keep pulling the site down. Stabilise, then build. Set a clear goal for the first stage, such as stable traffic on the changed pages, before you scale up. A clear goal prevents drift.
What should I record before starting?
Traffic, impressions, clicks and rankings for the test posts and a comparison group, saved with dates. Save a dated copy of the baseline figures somewhere safe so you can always compare like with like. A saved baseline is your reference point.
