If your blog is more than a year old, the fastest wins on it are probably not new topics. They come when you update old blog posts that already rank somewhere unglamorous, like the bottom of page one or the top of page two. Those pages have already done the hard part. They exist, they are indexed, and search engines have an opinion about them. They are just not finishing the job.
Writing new content still matters, because you cannot refresh your way into topics you never covered. But most teams have the ratio backwards: all effort on new posts, none on the archive. This guide is about correcting that, starting with how to pick candidates.
Why refreshing often beats writing new
A new post starts from nothing. No age, no links, no history, and often months of waiting before you learn whether it will rank at all. An existing post that sits just off the first page starts from almost there. A meaningful improvement to that page is competing for a handful of positions, not for the entire result set.
There is also a compounding effect on effort. The research is done, the URL may have collected links, and internal links already point at it. A refresh spends a few hours improving an asset; a new post spends days creating one that must earn all of that from scratch.
How to pick candidates worth refreshing
Do not refresh randomly and do not start with your favorites. Open Google Search Console and look for these signals:
- Pages ranking just off the first page for a keyword you actually care about
- Pages whose traffic has slid over several months with no obvious cause
- Pages with high impressions but few clicks, which usually means a weak title or meta description
- Pages containing outdated years, prices, screenshots, or product names
- Pages targeting a query where the results have changed shape, say from guides to comparisons, since you published
What a real update includes
Changing the date and swapping a sentence is not an update, and it does not fool anyone, human or machine. A real refresh rereads the page against the current search results and closes the gaps. Answer the questions the ranking pages answer and yours does not. Cut sections that no longer earn their place. Fix every stale fact and screenshot. Rewrite the title and meta description if impressions are high and clicks are low.
Then improve the connective tissue: add internal links from the refreshed post to newer related pieces and from strong pages back to it. An updated page in a well-linked neighborhood does better than the same page standing alone.
How to update old blog posts without losing rankings
First rule: keep the URL. The URL is where the page's history lives, and changing it without a redirect throws that history away. Second rule: before cutting anything, check which queries the page already ranks for in Search Console. A section that looks redundant to you may be the exact passage that ranks, and deleting it can cost positions you did not know you had.
If you are consolidating several old posts into one, pick the strongest URL as the survivor and redirect the others to it. And update the visible date honestly, only when the content genuinely changed.
Make it a habit, not a project
The archive decays continuously, so refreshing works best as a small recurring habit: one refresh for every new post, or a fixed monthly block. Keep a short queue of candidates ranked by how close they are to page one and how much you care about the keyword.
This loop is a natural fit for an assistant that can see your data. In Creaiter, the same chat can pull Search Console, surface the page-two rankings, and then rewrite and republish the post to your CMS, so a refresh fits in an hour. However you run it, the habit is the point: the cheapest traffic you will find this quarter is sitting in posts you already wrote.
Keep reading