How to refresh old blog posts that lost their rankings
Updating an old blog post beats writing a new one. Here's how to pick the pages worth refreshing, what to change, and how to measure the lift.
To refresh an old blog post, find the pages slipping in Search Console, then make one honest editing pass: fix what's outdated, match what people search for now, and add what a reader expects to see today. The date stamp does nothing by itself. Google rewards the edit, not the timestamp.
Most of your traffic already lives in posts you published months or years ago. Rewriting a page that once ranked is faster and safer than starting a new one from scratch, because the page already carries links, history, and a topic Google has seen before. The real work is deciding which posts to touch and what to change on each.
How to choose which old blog posts to refresh
Open Google Search Console and sort your pages by clicks over the last six months. You're looking for two patterns. Pages that used to bring steady traffic and now bring less. And pages stuck at position 8 to 15 on a query with real search volume, close enough that a better page would push them onto the first screen. Those are your candidates. A page ranking 45th needs a different kind of work, and a page sitting at position 2 should be left alone.
Rank the shortlist by how close the win is. A post at position 9 with 200 impressions a month is worth an afternoon. A post at position 30 with 12 impressions is not. Start where a small gain in rank turns into a real gain in clicks. If your traffic climbed once and then flattened, that plateau is usually a pile of these near-miss pages, and clearing them one by one is how you break it.
Diagnose why the page slipped before you rewrite it
Read the post as a stranger would, then read the top three results that now outrank it. The gap between them tells you what to fix. Usually it's one of four things: the facts aged (old numbers, dead tools, screenshots from a version that no longer exists), the intent moved (people who search the term now want a step-by-step, and you wrote an opinion piece), the page reads thin next to competitors who cover more, or the internal links that once pointed to it are gone.
Intent is the one that quietly kills a page. If searchers want something your post doesn't give them, no amount of polish will help. Confirm the page still matches what people are actually trying to do before you edit a single word.
Make the edit substantial enough to count
Google measures how much a page actually changes. A new date over the same words underneath does nothing, and dropping this year into the title to look current is the kind of fake freshness Google's guidance warns against. Aim to rework a real share of the page. Rewrite the opening so it answers the query in the first two sentences. Swap stale figures for current ones and cite the source. Add the sections the top results have and you don't. Cut the padding that's aged badly. Fix broken links, and point a few internal links back at the page from newer posts.
Keep the URL. Changing it throws away the history you're building on, unless the old slug is plainly wrong. Update the title and meta description only when they no longer match the query you're chasing.
Leave your evergreen winners alone
Some pages need this often, and some barely need it at all. Google runs freshness systems that favor recently updated pages when a topic genuinely moves, a pattern often called Query Deserves Freshness: active news coverage, frequent posts, and spiking search on a term all tell Google that readers want something current (per Ahrefs). A guide to a fast-moving tool, a pricing roundup, a post tied to a yearly event: refresh those on a schedule. A clear explainer that still matches intent can rank for years untouched. Spend your hours where the topic actually shifts.
There's a second reason to keep current pages current. AI answers pull heavily from recent material; Ahrefs found content cited by AI tools runs about 26% fresher than standard Google results. If you want to show up in AI overviews and chat answers, an up-to-date page has an edge over one that hasn't moved in three years.
Measure the change, then move on
Give the refresh four to eight weeks before you judge it. Watch the page in Search Console for the queries you targeted, and read the signals in order: rank first, then impressions, then clicks, because rank moves before traffic does. If the page climbs, write down what you changed and repeat it on the next candidate. If it hasn't moved after two months, the problem was probably intent or competition rather than freshness, and the page may need a deeper rewrite or a merge into a stronger one.
If you've got a shelf of old posts and you're not sure which ones are worth the afternoon, that's the kind of audit we run. We can help you turn the archive into a short list and a plan.