The AI agent
It reads your audits, decides what to fix, applies the fix to your live site, checks it worked, and keeps an undo for every change.
You decide how much it may do
| Off | It does nothing. |
|---|---|
| Suggest only default | It plans the work and shows you. Nothing is written to a live site. |
| Fix the obvious | Mechanical changes apply automatically. Judgement calls — anything touching article text — wait for you. |
| Full autopilot | Everything applies, including content edits. |
Caps on changes per run and per day, plus a cooldown, apply at every level, so it cannot work through your whole site in one go.
Everything is reversible
Before writing anything, the previous value is read from the CMS and stored. One click puts it back. If the previous value cannot be read, the change does not happen — an unrevertable edit is not worth the risk.
“Applied” and “verified” are tracked separately, because a CMS accepting a change is not the same as the change appearing on the page. The tool re-reads the page to confirm.
What it can fix by itself
Currently 29 of the 72 things the crawler can find. Titles, meta descriptions, image alt text, canonical tags, robots directives, Open Graph and Twitter tags, schema, redirects, internal links to orphan pages, site hardening, and your robots.txt AI crawler policy.
The rest need a person, and the tool says so rather than pretending. Some are server configuration, some belong to another platform's source code, and some — thin content — are writing rather than a mechanical edit.
What it needs
A way to write to your site. Today that is the WordPress bridge plugin, which also works for WordPress sites behind Cloudflare. Setting it up →
Without it the agent still plans the work and writes the exact change — you apply it.