Content freshness: what staleness signals Google actually reads

The staleness signal that matters

Your sitemap\u2019s lastmod values are the one freshness signal Google can read mechanically for the whole site, and stores routinely undermine them. The common failure is the wholesale rewrite: a plugin or platform regenerates every lastmod to today because the file changed, not the content. Google learns to distrust those values and falls back on its own crawl observations. The opposite failure is the opposite problem: a site whose newest lastmod is years old reads as abandoned, and abandoned sites get crawled on abandoned schedules.

When refreshing helps (and when it does not)

Refreshing helps where the query rewards currency, prices, specifications, annual comparisons, regulation-adjacent topics. It does nothing where the ranking content is simply better than yours: rewriting a 2023 article with the same information in new words is not freshness, it is churn, and Google\u2019s quality systems are indifferent to it. The honest test: does the update change what a visitor gets (new data, new sections, corrected claims) or only its timestamp? Update the first kind; stop paying for the second.

A realistic update cadence

1. Pick the pages that earn freshness: prices, product lines, guides people compare annually. Those get real updates; the rest of the site does not need to move.
2. Let lastmod tell the truth: regenerate sitemap dates only when the content actually changed, so the signal stays legible.
3. Watch instead of remembering: staleness is silent by nature: nothing breaks. The freshness check reads the newest sitemap date and says how stale the site is today; the watch tells you when it starts drifting.

Run the free freshness check to see your newest sitemap date and how Google is likely reading it. Related: crawl budget · indexing check

Questions

Keep reading