robots_named_agent_exempt
Umbodi adds the site's own Disallow rules to each named crawler group that escapes them, only when the owner has opted in to crawler-policy changes, publishes it as a pull request, and checks the file is live.
Not fixed by Umbodi on its own site — it cannot be planted there
A crawler obeys only the most specific group that names it. A group for GPTBot with just “Allow: /” lets that crawler read paths — /admin, /api — the site keeps everyone else out of.
Fires when a crawler group that names an agent carries none of the Disallow paths the site-wide group sets. Severity: warn.
The agent adds the site-wide Disallow paths to each escaping named group inside a fenced block it owns, so the stated policy is the one crawlers obey. 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.
Because this changes what crawlers may read, there is one more gate: the owner must have opted the project in to crawler-policy changes. Without that, the agent proposes and waits.
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:
plantable in principle and not built: the plant is a named group with `Allow: /` on the live robots.txt — the exact defect #912 removed, exempting a crawler from /admin and /api/ for up to 52 hours — and it needs a new robots edit plus a DRILL_EXCUSES entry, because test/robots-own-named-groups.test.mjs fails every pull request while the plant is open. Measured 2026-10-09: our robots.txt names ten crawlers and none escapes. Listed rather than attempted for the same reason as sitemap_url_not_indexable: a drill that re-opens what a fix just closed should be a decision, not a side effect of adding the code.
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 adds the site's own Disallow rules to each named crawler group that escapes them, only when the owner has opted in to crawler-policy changes, publishes it as a pull request, and checks the file is 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.