When NOT to Refresh a Blog Post (and What to Do Instead)

The short version: when a page is losing clicks you have five options, and refreshing is only one of them. Leave it (it's healthy, too new, or the drop is noise). Fix something that isn't the content (the title, a lost link, a technical fault). Merge it into a stronger page. Retire it. Or refresh it — which is the right call only once the other four are ruled out.

Almost everything written about old content assumes the answer before it asks the question. The page dipped, so refresh it. I've done that, and the expensive lesson was this: a refresh is not free upside. It has a cost, it has a failure mode, and on a meaningful share of pages the best available outcome is nothing.

Refreshing is the default, and the default is usually wrong

You have a fixed number of content hours. Say four a month. Every one you spend on a page is one you didn't spend on another page — and the ranked list of decaying pages is always longer than the list of hours.

So the question is never "could this page be better?" The answer to that is always yes. The question is: is there a version of this page that earns clicks back, and is this the best use of the next hour? Those are two different tests, and most pages fail the second one even when they pass the first.

What a refresh actually costs you

Three costs, and the field mentions none of them.

You can delete rankings you didn't know you had. A page that ranks for one obvious query usually ranks for a long tail of small ones you've never looked at. Cut a section for being "off-topic" and those go with it. Check what the page ranks for before you remove anything — and note that the Queries tab won't show you all of it, because Search Console omits queries that too few people searched.

You destroy your own attribution. Change the title, restructure the page, add two sections and update the date in one sitting, and you have no idea which of those did anything. You get one bit of information — better or worse — for four changes. Do it that way often enough and you never build a playbook, you just accumulate anecdotes.

And the hour is gone. That's the real cost, and it's the one nobody prices.

Verdict 1 — Leave it alone

Three kinds of page, and the first two are the most common mistakes I see.

The page that's fine. It's holding its traffic. It doesn't need you. The urge to polish a good page is strong and almost always misplaced — it has more to lose than to gain, and every edit is a chance to break what's working.

The page that's too new. A post published four months ago that hasn't taken off isn't decaying; it hasn't finished arriving. It needs links and time more than it needs another draft.

The drop that isn't a drop. A page earning 12 clicks a week that got 6 last week has not lost half of anything. Below roughly 10 clicks a week the percentages are theatre — that's the floor I use before a page is allowed onto any list at all. And a page that dips every August and recovers every September is seasonal, not decaying; compare it against the same weeks last year, not last month. What content decay looks like covers the three impostors in full.

Verdict 2 — Fix something that isn't the content

This is the verdict that saves the most wasted weekends, because the page looks like the problem and isn't.

If average position held and CTR fell, people are seeing you and choosing someone else. That's two lines of text, not 1,500 words — high impressions, low clicks has the diagnosis and the filter that finds these in bulk. Rewriting the body of a page because the title was dull is the most common misdirected refresh there is.

If the page quietly lost internal links — you deleted or restructured the pages that used to link to it — re-link it from three to five strong, relevant pages. That's twenty minutes.

And if another of your own pages is competing for the same query, no amount of rewriting either one fixes it; confirm that in Search Console first.

Verdict 3 — Merge it into another page

Two of your pages half-cover the same topic, neither ranks properly, and each one makes the other worse. Refreshing either is treating a symptom.

The decision rule I use: if you couldn't explain to a reader why both pages exist, they shouldn't both exist. Merge the useful parts into whichever URL has the better ranking history and backlinks, then 301 the weaker one to it — Google's guidance on consolidating duplicate URLs and 301 redirects covers the mechanics, and the refresh checklist covers what to keep when you combine them.

One page that fully answers the query beats two that each half-answer it. This is the verdict most often misfiled as "refresh both."

Verdict 4 — Retire it, and what Google actually says about that

Now the part the pruning advice gets wrong, and Google has been unusually direct about it.

Deleting content to make your site look fresh does not work, and that isn't an opinion. Google's helpful content guidance lists it among the things not to do, and answers it in its own parenthesis: "Are you adding a lot of new content or removing a lot of older content primarily because you believe it will help your search rankings overall by somehow making your site seem 'fresh?' (No, it won't)".

When CNET deleted thousands of pages on the theory that it signalled freshness, Google's Danny Sullivan said so publicly: "Are you deleting content from your site because you somehow believe Google doesn't like 'old' content? That's not a thing!" John Mueller has been equally blunt — removing content doesn't make the rest rank higher.

The crawl-budget argument doesn't rescue it either. Google's own crawl budget guidance is scoped to sites with a million-plus pages, or 10,000-plus that change daily, and opens by telling everyone else not to bother: "If your site doesn't have a large number of pages that change rapidly, or if your pages seem to be crawled the same day that they are published, you don't need to read this guide." If you have 200 blog posts, crawl budget is not your problem and deleting 40 of them will not help the other 160.

So retire a page for real reasons, not ranking magic: it's factually wrong and you won't fix it, it's about something you no longer do, or it duplicates a page you're keeping. Then 301 it somewhere genuinely relevant rather than dumping it on the homepage. A quiet page that's still correct costs you nothing to keep.

Verdict 5 — Refresh it

What's left after those four is the real refresh list, and it's shorter than the one you started with. It's the page where all of this is true:

• It earned meaningful traffic once — a genuine baseline, not a handful of clicks.
• It's down at least ~20% against that baseline and stayed down for weeks, not days.
• Its average position slipped, so this is a ranking loss rather than a click-through problem.
• People are still searching for the thing. Demand is still there.
• And you can name what the pages now beating you have that yours doesn't.

That last one is the test people skip. If you can't say what would change, you're not refreshing — you're rearranging. Which posts to update first ranks the survivors by clicks at stake, and the checklist covers what to change once you're on the page.

If the page fails the demand test — impressions falling while your position holds — no version of it wins, because refreshing cannot create searches. That's one of six reasons a post loses traffic, and the only one where the correct action is to walk away.

The special case: the page you just edited

If clicks fell within a week or two of your own change, the most likely cause of the drop is the change.

Restore it. Don't refresh it again. Put back what you removed, leave it four weeks, and compare. The instinct is to fix a bad edit with a bigger edit, and it's the worst available move: you stack two changes on one page and permanently lose the ability to tell which one did what. Measuring the before and after properly is the whole point of changing one substantial thing at a time.

The question that settles it

Before you open the editor, answer this out loud: what would have to be true for this page to earn its clicks back — and do I believe it?

If the answer is "a competitor covers three things I don't, and I can add them" — refresh it. If the answer is "nothing, really, the query dried up" or "I'd be rewriting a page that's already fine" — you just saved an afternoon, and that afternoon has somewhere better to be.

Saying no is the cheapest thing in this whole workflow, and it's the step almost nobody writes down.

Know which pages are actually worth the hour

Everything above is a judgement call, and it stays a judgement call — no tool makes it for you. What a tool can do is stop you making it on the wrong page.

That's the job RefreshRadar does: it watches every page in your Search Console, applies the rules above (20% below an eight-week baseline, above the 10-clicks-a-week floor), and emails you the ranked list with the clicks per month at stake and what each page's numbers actually did — position slipped, CTR fell, impressions dried up. It won't tell you to walk away from a page. It will tell you which pages are worth putting through the five verdicts, and which ones were never on the list.

Connect Search Console read-only and see what's decaying on your site — free — no card, about 30 seconds, and we never post or change anything. You'll get your three worst-decaying pages with the reason on each. If nothing on your site is decaying, we'll tell you that instead — which is its own kind of answer.