Google's John Mueller was asked about a technique that forces search engines to re-crawl sitemaps daily. His answer: it's a bad idea, because it signals that the canonical URL for a piece of content keeps changing.
Key facts
- Timing: Live now — this is guidance from Google, not a rule change.
- Who it hits: Sites whose sitemap index is generated by a plugin, a CDN rewrite, or a custom script that appends dynamic parameters.
- What to do: Open your sitemap index and check whether child sitemap URLs carry a
?v=parameter. If they do, strip it and maintain accurate<lastmod>instead.
What happened
Someone described a pattern seen on a large, rigidly structured site: every child sitemap URL inside the sitemap index gets a fresh ?v= unix timestamp each day — the cache-busting trick normally used on CSS and JavaScript files — so the changing URL forces a refetch rather than relying on the <lastmod> element. Mueller first asked what the goal was, then answered plainly: "I think that's a bad idea because you're signaling that the canonical URL for a piece of content should be constantly changing. That's not good for search engines, it's not good for your tracking." Cache busting remains legitimate for static assets; the problem is applying it to sitemaps.
What it means for independent store owners
This isn't a content issue, it's a technical detail that's easy to inherit without noticing. On WordPress, your sitemap usually comes from an SEO plugin and outputs clean URLs by default — but a caching plugin, a CDN rewrite rule, or a past "speed up indexing" customization can quietly add parameters. Checking costs nothing: open /sitemap_index.xml (or whatever your sitemap entry point is) and look at the child sitemap URLs listed inside.
The reason the trick doesn't work is worth internalizing. Crawl budget follows your site's genuine update signals and importance, not how many times you ask. Rotating URLs daily won't get your product pages crawled more often; it just spends crawler capacity re-confirming the same sitemaps and muddies your own log analysis. Maintain <lastmod> honestly instead — update the timestamp only when the content actually changed. If that value refreshes on every sitemap regeneration, Google learns to ignore it, and losing a trusted freshness signal costs more than any forced crawl gains.