missing_robots
Umbodi restores the site's last committed robots.txt from the repository's history, so the site's own rules come back, publishes it as a pull request, and checks the file is live.
Fixed by Umbodi on its own site · planted drill
robots.txt tells crawlers what they may read. Without it, every crawler is guessing, and rules the site relied on — keeping /admin or /api out of search — are gone.
Fires when /robots.txt answers but is missing or empty. Severity: warn.
The agent restores the last committed robots.txt from history first, which brings back the site's own rules exactly. Writing a new robots.txt needs the owner's chosen policy for AI crawlers (allow or block); without it the agent stops and asks.
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.
We planted this defect on our own site and let the agent find it. Each stage below is a timestamp read from the receipts, not a claim typed into this page.
| Page | planted | found | proposed | approved | published | merged | verified |
|---|---|---|---|---|---|---|---|
| /robots.txt | 2026-10-08 10:41 | 2026-10-08 10:55 | 2026-10-08 10:55 | 2026-10-08 10:55 | 2026-10-08 10:55 | 2026-10-08 11:10 | 2026-10-08 11:16 |
robots.txtfile deleted (66 lines)robots.txt+ # Umbodi — https://umbodi.ai + # The admin surfaces are gated by is_platform_admin() server-side; these rules keep them out of the + # index as well, because an admin screen appearing in search results is a disclosure of shape even file created (77 lines)
This receipt was recorded before 11 October 2026, when the after-deploy check confirmed only that the changed file loaded. The defect was re-checked on the live site on 11 October with the audit rule itself, and is fixed.
Last verified 2026-10-08 11:16 UTC
That the full chain ran with no human decision inside it: the agent found the defect, decided the fix, published it, merged it and verified the live site.
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 restores the site's last committed robots.txt from the repository's history, so the site's own rules come back, publishes it as a pull request, and checks the file is live.
Yes. We planted it on our own site and the agent found, fixed, merged and verified it with no human decision in the loop. The receipt is on this page.
The receipts page lists every defect type the agent repairs on its own, and which of them it has repaired live on this site.