// HOW-TO · SEO & DISCOVERY

How to refresh old content for Google Discover (2026)

Refresh old content for Google Discover: find decaying pages, update the substance, keep dateModified honest, then re-promote it to re-light interest.

Last verified · 2026-10-21 · by Moe Ameen

Content in Google Discover tends to spike early and then fade as reader interest cools, and the standard advice — "just refresh it" — is right in spirit and wrong in execution more often than not. A refresh only works when you genuinely change the substance of the page; changing the visible date or the dateModified field on otherwise-stale text does nothing, and Google has said for years that cosmetic date changes are "just noise." There is also no documented "freshness algorithm" or fixed 48-hour window to game — Google recommends timely content but surfaces relevant older content too. So the job is not to trick a timer. It is to make a decayed page genuinely relevant again, get Google to re-evaluate it, and re-light the reader interest that drives Discover in the first place.

This walkthrough is the honest version of the refresh workflow: find the pages worth refreshing in your Discover report, decide which actually deserve it, update the main body substantively, keep every date signal truthful, help Google notice the change, and — the step most people skip — re-promote the updated page so it earns a new wave of interest instead of sitting silently. For the strategy and the Google-documented facts behind all of this, read the [Google Discover freshness algorithm](/guides/google-discover-freshness-algorithm) guide; for the video-specific path into the feed, see [how to optimize videos for Google Discover](/how-to/optimize-videos-for-google-discover).

The steps

Find the decaying pages in your Discover report. Open Search Console and go to the Performance report for Discover, which shows impressions, clicks, and CTR for up to the last 16 months. Sort for pages that earned real Discover traffic and then fell off, and separately note evergreen explainers on topics whose interest tends to cycle back. Those two groups — the once-timely and the cyclical-evergreen — are your refresh candidates. Pages that never got Discover traffic at all are a different problem; refreshing them will not manufacture relevance that was never there.
Decide which pages actually deserve a refresh. Not every decayed page should be refreshed. Refresh when the topic has genuinely evolved (new information, a changed situation, outdated figures) or when reader interest is cycling back toward it (a season, a recurring event, a renewed news angle). Do not refresh a page whose topic interest is simply dead — Discover rewards relevance, not recency, and no update resurrects a subject no one is looking for right now. Spend the effort where a real reason to be relevant again exists.
Update the substance, not just the timestamp. This is the step that does the work. Rewrite or expand the main body: add new information, correct what changed, bring the framing to the present, deepen the parts that were thin. Google's systems weigh changes to the main content far more than edits to navigation, comments, or boilerplate, so put the effort into the article itself. The test is simple — if a returning reader would notice the page is meaningfully better or more current, it is a real refresh; if only the date moved, it is not.
Keep every date signal honest and in sync. Let the dateModified move because the content moved, never the other way around. Update the visible "last updated" date, the structured dateModified, and the server's Last-Modified header together so they tell one truthful story. Do not fake a date to look fresh — Google treats misleading dates as noise at best and a trust problem at worst, and a dishonest date can cost you more than a stale one. Honest dates are a signal; gamed dates are a liability.
Help Google notice the change. A refresh does nothing until Google recrawls and re-evaluates the page, and that is not instant — recrawl frequency varies by how important and fast-changing Google thinks a page is. Speed it up with the plumbing: update your sitemap's lastmod value for the URL, add internal links to it from pages that get crawled often, and keep the URL the same (if you must change it, 301-redirect the old one rather than deleting it). You can also request indexing for the single URL in Search Console.
Make sure the image is still Discover-ready. Discover is image-led, and a refreshed article is a good moment to confirm the visual qualifies. Google recommends a large, high-quality image — at least 1200 px wide and roughly 16:9 — and the max-image-preview:large setting so the feed can show it full-size. A compelling, non-misleading image is often what earns the tap. If the old hero image is small, low-quality, or no longer matches the updated content, replace it as part of the refresh.
Re-promote the page to re-light interest. This is the step almost everyone skips, and it is half the point. A refreshed page sits silent unless you push new attention at it. Share a fresh wave of social posts, link to it from a newsletter, and point internal links at it, so the renewed reader interest and engagement give Discover a current reason to resurface it. Re-distribution is not a Discover ranking trick — it is how you recreate the interest curve that made the page relevant the first time, on demand instead of by luck.
Measure the second wave and iterate. Back in the Discover performance report, watch the refreshed URL for a renewed impression bump over the following days — remembering Discover traffic is volatile and less predictable than search. If a refresh plus re-promotion earns a second wave, you have found a page worth keeping on a refresh rotation; if it stays flat, the topic interest is probably gone and your effort belongs on net-new timely content instead. Treat the report as the scoreboard, not any vendor's fixed window.

Common gotchas

Bumping only the date (or dateModified) without changing the content does not work — Google calls cosmetic date changes "just noise," and a misleading date can erode trust.
Refreshing a page whose topic interest is genuinely dead. Discover rewards relevance, not recency; no update revives a subject no one is searching for now.
Editing only navigation, comments, or boilerplate. Changes to the main body carry far more weight; a real refresh changes the article itself.
Expecting instant results. A refresh only counts once Google recrawls and re-evaluates — that takes time and varies by page and site.
Chasing a precise "48-hour window" or "5-10x boost" as if it were a Google rule. Those are publisher observations, not documented figures; the window estimates range widely.
Changing the URL on refresh, or deleting and reposting. Keep the same URL so it retains its history; if you must move it, 301-redirect rather than creating a 404.

Where Kompozy fits

Look at which step of this workflow actually stalls teams, because it is not the editing. Steps one through six — find the page, update the substance, keep the dates honest, help Google recrawl — are editorial judgment, and they are yours to make. The step almost everyone skips is step seven, re-promotion, and it is the one with the highest leverage: a refreshed page that no one points fresh attention at just sits there, waiting on luck to re-light the reader interest Discover runs on. That re-distribution is exactly where [Kompozy](/) earns its place in a content-refresh routine.

Here is the concrete motion. Once a page is genuinely updated, hand its URL and angle to Kompozy and it generates a whole redistribution wave from that one source — not a rewrite of the article, but the social layer that drives traffic back to it: a [Persona Shorts](/glossary/persona-shorts) talking-head on what changed, a [Marketing Shorts](/glossary/marketing-shorts) hook over relevant footage, Quote Graphics pulling the new stat or line, a Carousel walking the updated points, and Text posts for the link-led platforms. It is a full generation-and-publishing engine across [18 output formats](/glossary/output-buckets), not a repurposing tool, so each of those is a distinct net-new asset rather than the same post reflowed. Then it schedules the wave across the eight social platforms plus blog and email on [Autopilot](/glossary/autopilot) behind a per-post review gate, so the renewed attention lands over the days you want it to — turning step seven from a thing you mean to do into a queue you approved in one sitting.

Two honest limits, because they matter. Kompozy does not read your Search Console Discover report or decide whether Google resurfaces the page — step one's analysis and the editorial calls in steps two and three are human work, and no tool can guarantee Discover inclusion. What it removes is the throughput wall on re-promotion: one [Persona Brief](/glossary/persona-brief) keeps every cut in one voice and [HyperFrames](/glossary/hyperframes) keeps them brand-exact, so a refresh can trigger a real distribution wave in minutes instead of being abandoned for lack of hands. Starter ($199/mo for 5,500 credits) suits a solo publisher refreshing a handful of pages a month; Pro ($499/mo for 18,000 credits) sustains a weekly refresh-and-re-promote rotation across a back catalog; Enterprise is custom for agencies running this for multiple sites.

Frequently asked questions

Does changing the publish date get an old article back into Google Discover?

Only if you genuinely updated the content. Google has said for years that changing a date without substantively updating the page is "just noise" and does not help, and misleading dates can hurt trust. A real refresh — rewritten or added main-body content, new information, a current angle — can renew relevance; a date-only bump on stale text will not.

How quickly will a refreshed page come back in Discover?

There is no fixed timeline. The refresh only counts once Google recrawls and re-evaluates the page, which varies by how important and fast-changing Google considers it. Updating your sitemap lastmod, adding internal links, and requesting indexing can speed discovery of the change, but Discover traffic is explicitly volatile and less predictable than keyword search, so expect a range, not a guarantee.

Should I refresh every old page to chase Discover traffic?

No. Refresh pages where the topic genuinely evolved or where reader interest is cycling back, and skip pages whose subject interest is dead. Discover surfaces relevant content, not merely recent content, so a mass date-bump across a stale catalog wastes effort and risks the trust cost of dishonest dates. Target the refreshes that have a real reason to be relevant again.

Why does re-promoting a refreshed page matter for Discover?

Because Discover reacts to reader interest, and a refreshed page earns none on its own. Pushing a new wave of social posts, a newsletter mention, and internal links recreates the attention that made the page relevant the first time — so the renewed engagement gives Discover a current reason to resurface it, instead of waiting on luck. Re-distribution is how you re-light interest on demand.