No server code. Webflow hosting runs no code of yours at request time.
Webflow hosting runs no code of yours at request time. The page check reads the site from outside; the free tools show what AI sees. For the agent itself, a Cloudflare Worker in front of the Webflow site (your DNS on Cloudflare, proxied) is the route that works.
What it does not: without a place to run, the agent cannot count visits or apply switches on this host — put a Cloudflare Worker in front of it, or move the domain to a host with middleware.
The Cloudflare Workers guide → is the route for a host that runs no code of yours.
How installing the agent works, in general → · what the agent does and never does →
No. Installing puts the agent in place and binds it to the site by its token; nothing is applied. Every switch is your click in the dashboard and every word it writes is shown to you first.
Nothing was installed on this host; the Cloudflare Worker, if you used one, is removed in Cloudflare.
The 23 checks run from outside on every page check. The free tools read the site the way AI does. Without a place to run, the agent cannot count visits or apply switches on this host — put a Cloudflare Worker in front of it, or move the domain to a host with middleware.
Yes — it belongs to this one site and should live in an environment variable, never in a file you commit. It grants nothing beyond this site, and the domain proof refuses it from any other host.
The 23 checks run from outside before anything is installed — you see what the agent would do before it does it.