Question 1

How much of the page needs to change for Google to treat it as refreshed?

Accepted Answer

There's no publicly confirmed threshold, but the general guidance is: the change should be substantive enough that a reader would notice the difference. Updating a date without changing any content is unlikely to help — and may trigger scepticism about freshness signals if Google notices the pattern. Meaningful additions (new sections, updated data, revised examples, expanded coverage) are what drive re-evaluation. Minor copy edits and fixing a few statistics probably won't move the needle on their own.

Question 2

Should I delete content that can't be refreshed?

Accepted Answer

Only if there's no redirect destination worth sending the traffic to. If the page covers a topic that's genuinely irrelevant to your audience now, and consolidating it into another page doesn't make sense, then setting a 301 redirect to the nearest relevant page (or to the homepage as a last resort) is better than leaving a thin, outdated page indexed. Deleting without redirecting throws away whatever link equity the page has accumulated. As a general rule: retire thoughtfully, not reactively.

Question 3

How often should a content library be audited for decay?

Accepted Answer

Quarterly for sites with active publishing schedules, or whenever you notice a meaningful traffic drop on Search Console. For most sites, a quick review of the top 30–50 traffic-driving pages every three months catches decay before it compounds. Annual deep audits of the full library help catch pages that have been quietly losing impressions without making it onto the top-traffic list yet.

Question 4

Is refreshing always faster than writing new content?

Accepted Answer

Usually, but not always. If an existing page has structural problems that go all the way down — wrong format, wrong target keyword, poor internal link structure, thin content across the board — a refresh may take as long as writing a new page and produce a messier result. In those cases, writing a fresh page and consolidating the old one into it via a 301 redirect is often cleaner. The heuristic: if the page has links and ranking history worth preserving, and the topic is still viable, start with a refresh. If the foundation is broken, start fresh and redirect the old page to the new one.

Question 5

Can a refresh hurt a page that wasn't actually decaying?

Accepted Answer

It's possible but uncommon if the refresh is done carefully. The main risk is removing content that was contributing to rankings for keywords you weren't tracking — a section that seemed redundant during the rewrite might have been quietly ranking for a long-tail term. Before substantially restructuring a page, check Search Console's Queries tab filtered to that URL to see the full list of terms it currently ranks for, not just your primary target, so you don't accidentally cut something that was working.

Question 6

How do I prioritize which pages to refresh first if I have dozens of candidates?

Accepted Answer

Rank candidates by a combination of remaining impressions (proof the topic still has demand) and business relevance (how close the topic is to your actual offering). A page that lost half its clicks but still gets 5,000 impressions a month on a highly relevant commercial topic should come before a page with 200 impressions on a tangential subject, even if the percentage decline looks similar. Refreshing the highest-impression, highest-relevance pages first also gives you the clearest signal, fastest, on whether your refresh approach is working before you invest in the longer tail of candidates.

content refresh

The Content Refresh Playbook: Reviving Decaying Pages