Not the way it works on WordPress. Wix is a closed host that runs no server code of yours, so the agent cannot install directly on the site. The free structural checks and tools still read every page from outside, and the route the agent uses on other hosted builders, a Cloudflare Worker in front of the site, rarely applies here.
Because Wix 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. Wix's hosted sites run no code of yours and sit entirely inside Wix's own platform, 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 and Webflow among them; the fix described on what the agent does on your site is the same one, just applied through a different route, where a route exists at all.
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 dashboard 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, rarely available in front of Wix |
| The four switches applied automatically | Same: a place to run, which most Wix domains do not have |
Two things, both inside Wix's own dashboard. Wix lets you edit robots.txt directly from its SEO 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 through the Custom Code panel, which injects a snippet into every page's head; the schema and entity check shows what the page currently says, if anything.
Neither of these needs the agent installed. They are manual edits a site owner makes once inside Wix's own tools, checked against the free tool's output rather than guessed at.
Rarely, and only under one condition: the domain's DNS has to be pointed through Cloudflare with proxying turned on, the same requirement that unlocks the full agent on Shopify and Webflow. Wix sites typically do not meet it, because Wix expects either its own nameservers or specific A and CNAME records pointed straight at Wix, which leaves no room for a proxy to sit in front of the response.
Where a Wix domain's DNS setup does allow it, a Cloudflare Worker
works the same way it does on any other closed host: it sees the
whole response, so it can count every AI visit and apply the four
switches (crawler access, Organization data, the sitemap, and
/llms.txt) without anyone touching the dashboard by
hand. See
the Cloudflare Workers install
guide for the one file it takes. Where it does not, the only way
to get the rest of the agent is to move the domain to a host that
runs middleware, such as the ones on
the install page.
Without that route in place, the agent on a Wix site stays at checks and the two 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 | Wix | |
|---|---|---|
| Who installs it | You, no developer | No one, directly; a Worker only rarely |
| Where it runs | The Reflexa plugin, inside WordPress | Nowhere, unless DNS already sits on Cloudflare |
| Requirement | None beyond the plugin and a token | Domain's DNS on Cloudflare, proxied, which Wix rarely permits |
| If the requirement isn't met | N/A | Checks and manual dashboard fixes only |
Why it matters: a Wix site is never locked out of the free checks, only out of the parts of the agent that need a place to run; on Wix, unlike Shopify or Webflow, that gap usually stays open because the platform's own DNS setup closes off the Worker route.
Bottom line: Wix needs no developer for the free checks and two manual fixes; the full agent needs a place to run that most Wix domains cannot offer, which makes the free checks and the manual fixes the realistic ceiling for most Wix sites today.
Wix is a closed host that runs no server code of yours, so there is no plugin layer to install into. WordPress has that layer; Wix 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 Wix's own dashboard: edit robots.txt in the SEO settings, and add Organization structured data through the Custom Code panel. The free checks show exactly what is missing in each.
Only if the domain's DNS can be pointed through Cloudflare with proxying turned on, and Wix's own domain setup rarely allows that since Wix expects its own nameservers or specific DNS records. Where it is possible, a Cloudflare Worker in front of the site can count AI visits and apply the four switches; where it is not, moving the domain to a host that runs middleware is the only way to get the rest.
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.