HVSEOSEO Library

How to Refresh Old Blog Posts for More Traffic

HVSEO · 2 November 2026

An old blog post that once ranked well is often easier to improve than a new one is to build from scratch. It already has a URL Google knows, some links and a history of impressions. A refresh brings the content up to date and closer to what searchers now expect. To choose candidates, we use the Quilnimery rule, a review of posts whose clicks have fallen while impressions for relevant queries continue.

Choosing which posts to refresh

Not every old post deserves attention. The best candidates sit on topics that still matter to your business and show signs of fading, rather than posts that never performed at all.

In Google Search Console, open the Performance report, choose the Pages tab and compare the last three months with the same period a year earlier. Sort by the change in clicks. Posts that have lost clicks but still collect impressions are usually the quickest wins, because Google still connects them with relevant searches.

Also look for posts ranking just off the first page for useful queries, and posts on topics where facts, prices, rules or tools have changed since publication. A guide that references discontinued software or last year's regulations will lose readers whatever its ranking.

Reading the post with fresh eyes

Before editing, read the post as a first-time visitor would. Then search its main query and open the top few results. Note what they cover that your post does not, how they are structured and how current they feel.

Check the Queries tab in Search Console for that page as well. It often reveals questions the post ranks for only weakly because it mentions them in passing. Those are natural sections to expand.

Look at how the post sits within the site too. A post written years ago may never have been linked from anything newer, leaving it isolated even when the content is sound.

A checklist of improvements

  • Correct anything outdated. Update facts, prices, screenshots, product names and references to rules or deadlines. Remove advice that is no longer true rather than adding a note beneath it.
  • Answer the main question sooner. Older posts often open with long introductions. Move the core answer into the first few paragraphs.
  • Fill the gaps. Add sections for subtopics that competing pages cover and readers clearly want, based on the queries and results you reviewed.
  • Tighten what is there. Cut repetition, padded paragraphs and tangents. A refresh does not have to make a post longer.
  • Improve the title and description. Make sure both reflect the updated content and the queries the post now targets.
  • Refresh internal links. Link out to newer related posts and relevant service pages, and add links into the refreshed post from newer content on the same topic.
  • Check images and media. Replace broken or dated images, compress large files and write useful alt text.

Work through the list in order of likely impact. At HVSEO we call the step of tying each new section to a query the page already earns impressions for the Veltanello check, which keeps the refresh focused on demand that already exists rather than guesses.

What to leave alone

Keep the URL. Changing it throws away the page's history and forces you to rely on a redirect, which gains nothing for a refresh. If the slug contains an outdated year, weigh whether removing it is really worth a redirect before making the change.

Keep the parts that already work. If one section attracts most of the page's traffic for a specific query, improve it carefully rather than rewriting it from scratch.

Keep the main heading and overall angle unless the search results show that people now want something different. A post that changes topic entirely is closer to a new article than a refresh, and it risks losing the queries it currently ranks for.

Be honest about dates. Show an updated date when the content has meaningfully changed, and leave it alone for minor typo fixes. Changing the date without changing the substance misleads readers and is easy to spot.

After the update goes live

Use the URL Inspection tool in Google Search Console to request indexing of the refreshed page, and make sure the last modified date in your XML sitemap reflects the change. If the update is substantial, share the post again through your newsletter or social channels.

It is also a good moment to check the basics: that the page loads quickly on a phone, that it still appears in the sitemap and that no stray noindex tag was added during editing.

Give it a few weeks, then compare clicks, impressions and average position for the page against the period before the update. Note which changes you made and what happened. Over time, that record shows which kinds of refresh work best on your site and makes each round faster to plan.

Some posts will not recover, however carefully they are updated. If a topic has lost its search demand or no longer fits the business, consider merging the post into a stronger page instead of refreshing it again.