Learning to optimize old blog posts is the highest-return habit in content SEO. Every site accumulates articles that once earned traffic and now quietly fade — yet refreshing them usually beats writing something new, because the URL already has age, backlinks and indexed history working in its favour.
This guide lays out a repeatable refresh workflow: finding decayed posts, diagnosing why they slipped, rewriting with intent, and signalling the change to Google. Minor fixes can move rankings within weeks; structural rewrites typically need a full evaluation cycle to show their effect.
Quick Answer: Identify posts losing clicks or stuck around positions 5–20, update them to match current search intent, refresh facts and on-page elements, strengthen internal links, then request reindexing in Google Search Console.
Why Good Posts Decay (and Why That's Fixable)
Posts rarely fall because Google suddenly dislikes them. They fall because something shifted around them:
- Fresher competition. Someone published a newer, deeper answer to the same query.
- Shifting intent. Searchers began wanting comparisons instead of definitions, or richer formats took over the SERP.
- Outdated specifics. Stale prices, old screenshots and expired references drag perceived quality down.
- Link erosion. Pages that linked to the post died, redirected or simply moved on.
Every one of those causes is reversible. Treat a decaying post as an asset with maintenance debt, not a write-off.
Step 1: Build Your Refresh Shortlist
Open Google Search Console and pull the last 6–12 months of performance data. You want three lists: queries where you sit in positions 5–20, pages whose clicks are trending down month over month, and pages with solid impressions but weak click-through rate. Cross-reference those lists and prioritise posts that used to rank well — they carry authority and recover fastest. Skip obvious seasonal pages, or you'll "fix" a December dip in July.
Step 2: Diagnose Before You Rewrite
Match the symptom to the repair. Randomly rewriting a page with a snippet problem wastes the effort:
| Symptom in GSC | Likely Cause | Refresh Move |
|---|---|---|
| Stuck around positions 5–15 | Depth or freshness gap vs. rivals | Expand coverage, update facts and examples |
| Impressions steady, clicks sliding | Title/snippet losing CTR | Rewrite title tag and opening promise |
| Dropped out of the top 30 | Intent moved away from your format | Re-study the SERP, retarget or merge the page |
| Never ranked at all | Keyword mismatch or cannibalization | Rewrite against one clear query, or consolidate |
Step 3: Run the Refresh
With a diagnosis in hand, work through the update in one sitting so the piece stays coherent:
- Re-validate intent. Search the target query yourself and study today's top results — format, angle and depth.
- Update everything time-sensitive. Years, statistics, prices, screenshots and tool names.
- Add missing depth, cut filler. Cover the subtopics the current SERP rewards and delete padding that adds words, not value.
- Tune the on-page layer. Align the title tag, headings and image alt text with the language searchers actually use.
- Rebuild internal links. Point fresh contextual links from your strongest pages at the refreshed URL, and fix any orphaning.
- Ship and signal. Update the modified date honestly and request indexing via URL Inspection.
How Much Should You Change?
Scale the surgery to the decline. A small dip deserves a surgical pass — updated examples, sharper title, two new sections. A heavy drop justifies restructuring. If intent moved completely, consolidate several weakening posts into one stronger page and redirect the absorbed URLs; merging competing articles often recovers more traffic than editing either alone.
Refresh Mistakes That Undo the Work
- Changing the slug or URL — you discard the very equity the refresh was meant to revive.
- Republishing as a new post and leaving the original live, creating a duplicate-content mess.
- Bumping the date without substance; readers and algorithms both notice empty "freshness".
- Inflating length with synonym-stuffed paragraphs instead of answering the query better.
- Ignoring cannibalization — two of your own pages fighting over one query cancels both.
Key Takeaways
- Refreshing proven pages usually returns more traffic per hour than publishing new ones.
- Diagnose in Search Console before rewriting — CTR problems and depth problems need different fixes.
- Update intent, facts, on-page elements and internal links together, then request reindexing.
- Never touch the URL; merge and redirect only when intent has fully moved on.