Back to blog

Updating Old Content vs Writing New: What the Case Studies Show

Refreshing an existing article routinely beats publishing a new one — faster, cheaper, and with bigger swings. Here's the published data on content refreshes, and which posts to update first.

The instinct when traffic stalls is to publish more. The data says the opposite is often smarter: updating an article you already have routinely beats writing a new one — faster, cheaper, and with bigger swings. An existing page is indexed, trusted, and sometimes already ranking on page 2; a refresh skips the slow part of the SEO timeline entirely.

Here's what the published case studies actually show, and how to pick the pages worth updating.

Every number below is sourced.

The numbers are large and fast

Content refreshes produce some of the biggest documented short-term SEO swings there are:

  • HubSpot ran a systematic "historical optimization" program — updating old posts rather than only publishing new ones, and reported roughly a 106% increase in traffic to updated posts (HubSpot).
  • Backlinko saw a 260.7% traffic boost in 14 days after updating an existing post, as documented in refresh case-study roundups (ContentHarmony).
  • Single Grain updated 42 blog posts and saw a 96% increase in traffic — over 8,000 additional monthly visitors — from the refresh (Draft.dev).

Two things stand out. First, the timelines are short — days and weeks, not the months a new page needs. Second, the gains come from content that already existed. This is leverage on work you've already done.

The listicle finding worth noting

One detail from the Single Grain study is especially useful. Of the 42 posts refreshed, 11 listicles accounted for 84.2% of the total traffic gained — despite being only 26% of the content updated (Draft.dev).

The takeaway isn't "only refresh listicles." It's that refresh returns are concentrated — a minority of your posts will drive most of the gain. Which means picking the right posts to update matters far more than updating everything.

Which posts to refresh first

The case studies converge on a clear priority order. Refresh these before anything else:

1. Posts ranking in positions 6–20. Already on or near page 1, one update away from a meaningful jump. This is the same logic as page 2 quick wins — you're improving something Google already ranks, not starting over.

2. Posts with backlinks but declining traffic. They have earned authority you don't want to waste. A page that's slipping despite good links usually just needs its content brought back up to date to reclaim position.

3. Evergreen posts with outdated information. Content on a timeless topic where the specifics have gone stale — old stats, old screenshots, a "2023" in the title. Freshness is a ranking and AI-citation signal, and these are the easiest wins.

What not to prioritize: posts on dead topics nobody searches anymore, or thin posts that were never good — those need replacing or pruning, not refreshing.

What a refresh actually involves

Refreshing isn't changing the date and republishing. Google sees through that. A real refresh:

  • Updates the substance — current data, current examples, current best practices. Replace what's stale, don't just re-timestamp.
  • Fills the gaps — compare against the pages now ranking in the top 3 and add the sections they cover that yours doesn't (the quick-wins method).
  • Sharpens the title and meta, often the single highest-return edit, updating the year and the hook.
  • Improves internal links — add links from newer relevant posts to the refreshed one, and out to your current best pages (the 20-minute system).
  • Then genuinely updates the date and resubmits the URL in Search Console.

The timeline to expect

Refreshes move fast by SEO standards. Documented results typically show initial movement within 2–4 weeks, with fuller results over 3–6 months as Google re-crawls, re-assesses, and re-ranks the updated page. Some of the biggest case-study spikes came within days, but plan around weeks, and treat anything faster as upside.

The honest strategic point

For most SaaS blogs past their first year, the highest-return content work isn't the next new article — it's auditing what you already published and updating the handful of posts sitting at positions 6–20 with decaying traffic. New content matters for expanding coverage, but it starts from zero and waits months. A refresh works an asset you already own.

So before you write the next post, ask: is there an existing page one update away from a much bigger result? The case studies say there usually is. Balance the two — publish new to expand, refresh old to compound, and don't let good pages quietly decay while you chase new ones.

Sources: HubSpot — Historical Optimization, Draft.dev — Refreshing Blog Posts, ContentHarmony — Content Refresh Examples, Search Engine Land — Refreshing Content.

Put this into practice automatically

WriteGap finds your keyword gaps and writes the article drafts — every Monday.

Start free →