sitemap_stale
Umbodi regenerates sitemap.xml with current dates when a page's own Last-Modified is later than the date the sitemap gives it, publishes it as a pull request, and checks the new dates are live.
Not fixed by Umbodi on its own site — it cannot be planted there
A sitemap whose dates are older than the pages tells crawlers nothing has changed, so updated pages are revisited later than they should be.
Fires when a page's Last-Modified header is later than the lastmod its sitemap entry advertises. A date-only lastmod is compared by day, the precision the site published. Severity: warn.
The agent regenerates the sitemap from the site's own pages so each entry carries a date the page itself agrees with. No threshold is invented: both dates come from the site.
The change reaches the site as a pull request that adds or edits a site file at the repository's web root, opened by the Umbodi GitHub App. Generated blocks sit inside fences the agent owns, so the site's hand-written lines are never rewritten.
The value is derived from the site's own data, so the change is stamped mechanical and no score bar applies. It still applies only when the owner has armed unattended acting and set this category's autonomy dial to automatic; merging needs a separate opt-in.
One proposal in ten is held back as a control group — chosen by a fixed hash per project, not by hand — and is never applied unattended, so the effect of the fixes can be measured against the ones not made.
After the pull request merges and the production deploy appears, the agent fetches the live file and compares it with the merge's own diff: every line it added must be there, and a change that only removed lines must have them gone. If not, the file is re-read up to five times, about two and a half hours, and then the agent reverts its own merge.
It stops, and says why, when the live file is generated by the site's own code rather than served from the repository — a pull request would change nothing — when the file in the repository already says the same, when a robots.txt change needs a policy the owner has not chosen, or under the same merge and deploy rules as page changes. It never reverts on a file it cannot fetch.
Our site has nowhere this defect can be planted without breaking something real, so there is no live receipt. The repair path is proven in the test suite only. The reason, as the code states it:
same generator, same answer: build-sitemap rewrites every <lastmod> on each push, so a planted stale date is reverted by CI before the agent can act. Measured 2026-10-07; owner decision.
Last verified 2026-10-11 08:43 UTC
Only what the test suite proves: the route from finding to verified repair works against fixtures. Nothing on this page claims it has happened live.
It does not prove a ranking or citation change. Umbodi never infers one from a fix: rank is measured separately, on Google, and reported as measured. One receipt also shows the path works on this site, not that it works on every site.
Umbodi regenerates sitemap.xml with current dates when a page's own Last-Modified is later than the date the sitemap gives it, publishes it as a pull request, and checks the new dates are live.
Not live. Our site has nowhere it can be planted without breaking something real, so the repair is proven in the test suite only, and this page says why.
The receipts page lists every defect type the agent repairs on its own, and which of them it has repaired live on this site.