Your Next Blog Post Can Wait. Fix the Old Ones

Publishing another post is the most expensive way to grow a small blog. The pages you put up last year are already indexed, already carry whatever authority your domain has earned, and most of them are underperforming in ways you can see in an afternoon. This is not an argument for publishing nothing. It is an argument for changing the ratio — fewer new posts, and a standing budget for fixing, merging and cutting the ones you already own.

Why has publishing more stopped working?

Because the baseline for a new page is close to zero. Ahrefs examined roughly 14 billion pages in its index and found that 96.55% of them get no search traffic from Google at all, with another 1.94% getting between one and ten visits a month (Ahrefs, December 2023). That is the distribution your next post joins. Its June 2026 roundup of search statistics puts the near-term odds more precisely: 1.74% of newly published pages reach Google's top 10 within a year, while 72.9% of the pages currently sitting in the top 10 are more than three years old (Ahrefs, June 2026). Ranking is substantially a function of time, and time is the one input a brand-new post has none of.

Your archive, meanwhile, has already spent that time. A post published eighteen months ago that sits at position 11 for a query your buyers actually type has done the hard part already. Moving it to position 6 is a different kind of work from getting a brand-new URL indexed, ranked and kept there.

What does a refresh actually return?

The clearest public measurement I found this month comes from an agency that instrumented its own site. Workshop Digital tracked 273 content events — refreshes and new launches — between January 2024 and mid-2026, comparing each page's 90 days before with its 90 days after. Across 95 refreshed pages organic sessions went from 610 to 3,341, a 447.7% lift, while comparable pages it deliberately left alone declined 20.2% over the same windows. Narrowed to blog posts, 41 refreshed pages gained 545.1% while untouched blog pages lost 9.1% (Workshop Digital, May 18, 2026).

Which posts do you refresh, and which do you cut?

Sort before you write. Pull sixteen months of Search Console data page by page and put every URL into one of four piles. Pages ranking between five and twenty for a query you actually want are the refresh pile — close enough that a better page moves them, far enough that there is room to move. Pages with impressions but almost no clicks usually have a title and description problem rather than a content problem, and cost twenty minutes each. Pages competing with another post of yours for the same query belong merged into whichever already ranks better, with the loser redirected into it. Pages with no clicks, no inbound links and no part in any sales conversation are the cut pile.

What does a real refresh change?

Not the date. Changing a publish date without changing the page is the version of this that does not work, and it is the version most often sold. A refresh that moves a page rewrites the first two sentences so they answer the query outright, replaces examples and figures that have gone stale with current ones carrying their date, adds the sections the pages above you cover and yours does not, repairs the internal links pointing at it from the rest of the site, and rewrites the title and description to match what the page now says. Then you resubmit it and leave it alone.

How do you know it worked?

Measure each page against itself and against the ones you did not touch. Record clicks, impressions and average position for the 90 days before you publish the change, then the same three for the 90 days after, and run them for a set of comparable pages you deliberately left alone. Without that control set you will credit the refresh for a seasonal swing or blame it for an algorithm update. Expect movement in six to ten weeks rather than six days, and judge the programme on the whole pile rather than on the one page that happened to jump.