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.
| Sitemap signal | What Google concludes |
|---|---|
| lastmod updated only when content changed | Trustworthy — used for prioritisation |
| every lastmod = today, always | Noise — ignored, crawl decided elsewhere |
| newest lastmod months-to-years old | Site looks dormant — recrawl slows site-wide |
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
- 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.
- Let lastmod tell the truth: regenerate sitemap dates only when the content actually changed, so the signal stays legible.
- 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
Shipwork reads your sitemap\u2019s lastmod values from outside your network and reports how stale the newest one is — the freshness signal Google recrawl scheduling reads. Free, no account, no signup — paste your store address.
Check freshnessQuestions
- Does content freshness affect SEO?
- Yes, indirectly: freshness signals shape recrawl frequency, and dormant sites get crawled less. But refreshing content only helps when the update is real — churn without substance is ignored.
- How does Google know content is fresh?
- Mechanically: sitemap lastmod values, HTTP Last-Modified headers, and its own crawl observations. Claims of freshness without any of those are unread.
- How often should I update my sitemap?
- Every time content meaningfully changes — and only then. Faking lastmod dates devalues the whole file.
- What does the freshness check measure?
- The age of the newest lastmod in your sitemap, read from outside your network the way a crawler reads it.
Keep reading