An old blog post is getting fewer visitors. Should you rewrite it?
Maybe. But first check what changed. The advice might be out of date, a link might be broken, or the page might no longer answer what people are searching for. It could also be a quiet season for the topic.
Updating old blog posts—sometimes called a content refresh—works best when you can name the problem you are fixing. Here is how to make that decision without throwing away useful work.
Start with a page worth keeping
Choose an article that still matters to your customers. Good candidates include a guide with outdated steps, a post that receives useful search impressions but gives an incomplete answer, or a once-helpful page that has lost relevant traffic.
Do not pick an article just because it is old. A three-year-old explanation can still be accurate. A three-month-old software tutorial can already be wrong.
Write down who the article helps and what they should be able to do after reading it. If you cannot answer that, decide whether the topic still belongs on your website before rewriting it.
Check whether traffic really dropped
In Google Search Console, open the Performance report and filter it to the article's exact address. Compare a meaningful period with the previous period. For seasonal topics, look at the same period last year too.
A guide to Christmas deliveries will probably get fewer searches in February. Rewriting it will not create December demand.
Look at these clues separately:
- Fewer impressions: The page is being shown less often. Search interest, rankings, or the searches it appears for may have changed.
- Similar impressions but fewer clicks: Check the title, the searches involved, and the competing results. The average position may also have changed.
- Similar visits but fewer enquiries: The problem may be the offer, a broken form, or visitors needing something different.
These are clues, not proof. Google's guide to investigating a drop in search traffic explains additional checks.
If traffic disappeared suddenly, also check whether the page still loads and remains indexed before working on the writing.
Read it as someone trying to follow the advice
Take a tutorial about setting up online bookings. Open the booking tool and follow the article from the first step.
Does the menu still exist? Does the screenshot match? Does the reader need an account or a paid plan that the article forgot to mention? What happens if they get stuck?
Make a list of specific fixes:
- Replace an outdated step.
- Add a missing requirement before the reader begins.
- Explain an unfamiliar term when it first appears.
- Update broken links and inaccurate prices.
- Add a real example of the completed result.
- Remove repeated paragraphs that delay the answer.
Preserve material that still helps. The goal is not to make the article look new; it is to make it work better.
Decide whether to update, combine, or leave it alone
Most useful posts should be improved at their existing address. That keeps links and bookmarks pointing to the same resource.
Sometimes you have two posts answering almost exactly the same question. For example, “How much does website maintenance cost?” and “Website maintenance pricing explained” might not need separate pages.
Read both before combining them. Keep any useful details from each and choose one address for the complete answer. If you retire the other address, ask your website maintainer to set up a permanent redirect to the genuinely relevant replacement. Also update links on your own site.
Do not combine pages merely because they share words. “Website maintenance costs” and “How to choose a maintenance provider” can serve different needs.
Leave a page alone when it remains accurate, useful, and there is no clear problem to solve. If a page has no continuing purpose and no suitable replacement, removal may be more honest than redirecting it to an unrelated home page. That is a separate site-maintenance decision, not a routine part of refreshing an article.
Use SEO Dispatcher to plan the update
Add your site to SEO Dispatcher and connect Search Console. Find the article in your content library and review its available search data alongside a live-page audit.
Then write a small editing brief. For example:
Update our booking setup guide for the current interface. Keep the existing address and useful troubleshooting section. Replace the old screenshots, explain the account requirements, and add a test booking step. Check every instruction against the actual tool.
SEO Dispatcher can help prepare content in your site's Markdown or MDX format and send approved work through GitHub. Review the changes before publishing, especially anything involving prices, software instructions, or claims about your product.
Redirects and changes to page access need their own implementation. Do not assume an article draft has taken care of them.
Check the update after publishing
Open the live page on a phone and a computer. Test the important links and confirm the title and description still match the article.
Keep the original publication date. Add an updated date for a meaningful revision; changing only the date is not an improvement to the answer.
Record what you changed and why. After the page has been processed and has enough data, compare relevant searches, clicks, and reader actions. Avoid making several more changes immediately: you will struggle to tell which one helped.
If the update does not improve traffic, it can still have corrected bad advice. But do not treat that as proof that your SEO diagnosis was right. Recheck whether the page answers a question the intended customer actually has.
Common questions
Should I change the URL to include this year?
Usually, no. Keep a useful address stable and update the content where it already lives. A new address introduces extra work and can break existing links if handled badly.
How often should I update articles?
Use the topic as your guide. Check changing software instructions when the product changes. Review stable explanations when readers find a gap or the evidence changes. There is no useful universal rule to rewrite every post monthly.