Not the way it works on WordPress. Webflow hosting runs no server code of yours at request time, so the agent cannot install directly on the site. The free structural checks and tools still read every page from outside, and a Cloudflare Worker in front of the site is the route to the rest, if the domain's DNS is already on Cloudflare.
Because Webflow gives you no server to put it on. On WordPress, the agent is a plugin that runs inside WordPress's own PHP layer; on a custom-coded site, it is one file in the middleware or a CDN worker. Webflow's hosted sites run no code of yours at request time, so there is no layer to drop a plugin or a file into.
That is a limit of the hosting model, not a decision Reflexa makes about the site. The same is true of other fully hosted builders, Shopify among them; the fix is the same one described on what the agent does on your site, just applied through a different route.
The structural checks and the five free tools, in full. They crawl the site's public pages from outside the way an AI engine would, so they need no install, no settings access and no account changes to run. Open the free check at dashboard.reflexatechnologies.com/audit against the live domain and every finding comes back the same as it would for any other site; see the 23 structural checks, one by one for what each one looks for.
| What it serves | What it needs |
|---|---|
| Structural checks (crawler access, schema, entity clarity, JS-only text) | Nothing; runs from outside on any public page |
| The five free tools | Nothing; same, no signup |
| Counting AI visits page by page | A place to run: a Cloudflare Worker, if Webflow itself can't host it |
| The four switches applied automatically | Same: a Cloudflare Worker in front of the site |
Two things, both inside Site settings that Webflow already gives every site owner. Webflow lets you edit robots.txt directly in the SEO section of Site settings, and the AI-crawler groups for GPTBot, ClaudeBot and PerplexityBot can be added there by hand; the crawler-access check shows exactly which ones are missing. Organization structured data can be added the same way, through the custom code field in Site settings; the schema and entity check shows what the page's head currently says, if anything.
Neither of these needs the agent installed. They are manual edits a site owner or a Webflow developer makes once, checked against the free tool's output rather than guessed at.
Yes, with one condition: the site's domain has to already have its
DNS on Cloudflare, with proxying turned on. A Cloudflare Worker put
in front of the site sees the whole response before it reaches the
visitor, so it can do what a plugin does on WordPress or a
middleware file does on a coded site: count every AI visit and apply
the four switches (crawler access, Organization data, the sitemap,
and /llms.txt) without anyone editing Site settings by
hand. See
the Cloudflare Workers install
guide for the one file it takes.
Without that Worker in place, the agent on a Webflow site stays at checks and manual fixes; it cannot count visits or flip a switch on a host it has no way to run on.
The difference is entirely about where the agent runs, not what it does once it is running.
| WordPress | Webflow | |
|---|---|---|
| Who installs it | You, no developer | No one, directly; a Worker instead |
| Where it runs | The Reflexa plugin, inside WordPress | A Cloudflare Worker in front of the site |
| Requirement | None beyond the plugin and a token | Domain's DNS already on Cloudflare, proxied |
| If the requirement isn't met | N/A | Checks and manual Site-settings fixes only |
Why it matters: a Webflow site is never locked out of the free checks, only out of the parts of the agent that need a place to run; the Worker route closes that gap for any site whose domain sits on Cloudflare already.
Bottom line: Webflow needs no developer for the free checks and two manual fixes; the full agent needs a Cloudflare Worker, which is a one-file job for whoever already manages the domain's DNS.
Webflow hosting runs no server code of yours at request time, so there is no plugin layer to install into. WordPress has that layer; Webflow does not, which is the whole difference.
The structural checks and the five free tools. They crawl the site's public pages from outside, the same way an AI engine would, and need no install and no account changes to run.
Two things, both in Site settings: edit robots.txt directly, and add Organization structured data through the custom code field. The free checks show exactly what is missing in each.
Yes, if the site's domain already has its DNS on Cloudflare with proxying turned on. A Cloudflare Worker put in front of the site sees the whole response, so it can count AI visits and apply the four switches the same way an install on a coded site does.
Yes. It belongs to this one site, lives in an environment variable rather than a committed file, and the domain proof refuses it from any other host, even another site on the same Reflexa account.
The free check reads your site the way AI crawlers do and shows every finding with its evidence, no card and no install needed.