How to Update Old Blog Posts for SEO: The Content Refresh Playbook

Most blogs have their biggest SEO opportunity sitting in the archive. A post that ranks on page two already has everything a new post has to earn from scratch — an indexed URL, accumulated internal links, and a history with Google. Updating it is routinely faster than publishing something new, because you are improving an asset Google has already evaluated instead of introducing one it has not.

This is the refresh playbook: which posts to update, what to change, what to leave alone, and how often to do it.

Why refreshes outperform new posts

When Google has already ranked a page — even at position 15 — it has judged the page relevant to the query. Your job is no longer "get noticed"; it is "close the gap with the pages above you." That is a much smaller job. New posts, by contrast, typically spend weeks or months in the impressions-but-no-clicks phase we describe in How Long Does SEO Take?

Refreshes also fight content decay. Rankings are not static: competitors publish, intent shifts, and dated facts quietly disqualify you. A post that earned its position in 2024 and has not been touched since is losing ground even if nothing on the page changed.

Which posts to update first

Pull your pages from Google Search Console and prioritize in this order:

1. Positions 5–20 with real impressions. These are the near-misses. A modest improvement can move them onto page one, where nearly all clicks happen.
2. Posts with declining clicks. Compare the last three months to the prior three. A steady decline is decay — refresh before the position slides further.
3. Posts with high impressions but low CTR. The content ranks; the snippet fails. Often this needs only a better title and meta description — see How to Write Meta Descriptions That Get Clicks.
4. Strategically important posts that never ranked. These need diagnosis, not polish: usually the intent is wrong or the topic is beyond your site's current authority.

Skip posts that already rank in the top three. The upside is small and a careless edit can cost you the position.

What to actually change

A refresh is not a proofread. Work through these in order of impact:

• Re-check the intent. Search your target keyword and look at what ranks now. If the results have shifted — from listicles to how-tos, from articles to tools — restructure to match. Intent drift is the most common reason good posts slide.
• Cover what the top results cover that you don't. Read the current top three and list every subtopic and question they answer that you skip. Add the missing sections properly, not as bolted-on paragraphs.
• Update every dated fact. Statistics, screenshots, product names, prices, years in headings. One visibly stale detail tells both readers and Google the page is unmaintained.
• Cut what no longer earns its place. Refreshing is also pruning. Padding that seemed harmless at publish time drags the whole page down; length only helps when it is coverage, as we argue in How Long Should a Blog Post Be for SEO?
• Add internal links in both directions. Link the refreshed post to relevant newer posts, and — the step almost everyone forgets — add links from newer posts back to it. See Internal Linking for SEO.
• Rewrite the title and meta description. This is the cheapest CTR lever on the page. Keep the keyword; sharpen the promise.

What to leave alone

• The URL. Never change a slug during a refresh. The URL holds the page's accumulated equity; changing it means a redirect and a partial reset. This matters enough that it has its own rule in our CMS migration guide.
• Headings that already rank for long-tail queries. Check Search Console before deleting or rewording an H2 — subheadings often rank for question queries on their own.
• The publish date, unless the content genuinely changed. Bumping dates without substantive edits is a pattern Google explicitly discounts. Update the modified date honestly.

After you hit save

Request indexing for the URL in Search Console so the recrawl happens in days rather than weeks. Then note the position before the refresh and check back at two, four, and eight weeks. Movement from a good refresh usually shows inside a month.

Make it a system, not a project

The teams that win at this treat refreshing as a standing lane in their publishing cadence — a common split is two-thirds new content, one-third refreshes, as part of a cadence that actually ranks. This is also a place automation genuinely helps: DraftRank scores every published post and can regenerate underperformers with current information while keeping the slug and structure intact, which turns the refresh backlog from a quarterly project into routine maintenance.