Google’s Mueller advises against daily sitemap URL changes
Keep sitemap URLs stable and audit real freshness. Compare child locations, page changes and cached responses with a downloadable two-snapshot worksheet.
Keep sitemap locations stable and fix stale responses at the cache. Adding a new timestamp to a child sitemap’s URL every day is not evidence that Google will discover or index its pages sooner.
What Mueller said about rotating sitemap URLs
On September 1, Google’s John Mueller advised against the practice on Bluesky: “Having clean, stable URLs is important.” The original question described a site adding a fresh timestamp parameter to child-sitemap locations inside a sitemap index each day.
The exchange matters because it distinguishes a changing address from changed content. It does not document a penalty, identify the site, or measure how often Google fetched either version. Mueller’s reply discusses URL stability broadly; it should not be presented as a controlled test of sitemap caching.
Separate the sitemap address from the page addresses
A sitemap index points to sitemap files. A URL sitemap points to pages. In the reported setup, /posts.xml?v=100 becomes /posts.xml?v=200. That does not necessarily mean the article URLs inside the file have changed. Check both layers before describing the implementation as a canonical problem.
Our practical recommendation is to retain an address such as /posts.xml, make sure it serves the intended current XML, and investigate the component serving an old copy. If a plugin generates dated child filenames for a legitimate partitioning scheme, document that scheme first. A new archive partition is different from renaming the same unchanged file every day.
What a sitemap date should describe
Google’s sitemap guidance says it uses lastmod when the values are consistently accurate and reflect significant page changes. Google ignores priority and changefreq. Submission remains a discovery hint, not a promise of fetching or indexing.
For the sitemap index itself, the Sitemaps protocol defines lastmod as the modification time of the corresponding sitemap file. Within a URL entry, it describes the page. Keep those two dates separate in your generator and audit.
A worked example: new address, same content
These are invented examples, not observations of Googlebot. Suppose two daily exports list the same 25 articles and identical page modification dates. Only the child-sitemap parameter changes. Your audit has found address churn; it has not found 25 fresh articles or faster discovery.
| Change | What to record | Next check |
|---|---|---|
| Only the child URL changes | Old and new locations; XML comparison | Ask why the generator rotates the address |
| An article is substantially revised | Changed passage; page modification time | Verify that the URL entry reports that change |
| Origin XML is fresh; public XML is old | Two response bodies and cache headers | Investigate cache rules and invalidation |
Do not reset every article’s date because the sitemap was rebuilt. In this example, replacing a broken source link on one article and regenerating the file should lead to a review of that article’s metadata—not a claim that every listed page was updated.
Download the two-snapshot audit
Download the sitemap freshness audit CSV. Each row compares one child sitemap across two observations. It records locations, response status, body comparison, a sampled page’s change evidence, cache evidence, decision, owner, and next review. Replace the rows marked EXAMPLE-REMOVE.
Save the first XML response before changing configuration. After one known content update, save another response and compare it with the actual edit. Check a small set of important URLs in Search Console separately. A successful sitemap fetch and a page’s indexed status answer different questions.
Fix a demonstrated mismatch, then observe
Act when the public file is stale, inaccessible, malformed, or listing the wrong destinations. If the sitemap is current but Google selects a different page, use the canonical observation ledger. If the concern is falling traffic, use the traffic-drop diagnosis before attributing the change to sitemaps.
Evidence note: The original exchange and documentation were checked September 5, 2026. The downloadable worksheet is an editorial audit aid, not a crawl-speed experiment or a promise of indexing.
Keep learning
Continue this topic
Next in this topic
Why Google shows your domain instead of your site name
Earlier in this topic
Google Avoids an Ad-Tech Breakup, but Publishers Still Lack the Details
SEO
Ask a question or join the discussion