How to fix it here
AI crawlers allowed in robots.txt
Wix editor: Settings → SEO → Robots.txt editor. It edits the live file directly, with no publish step.
Site platforms
Wix SEO for AI search: what an answer engine can read
Wix is better at this than its reputation suggests. It ships a robots.txt editor that writes the live file with no publish step, a field for custom structured data, and server-rendered pages — three things that took the rest of this list years to get. HubSpot's CMS, sold at many times the price, makes you find all three in different places.
- How we recognise it
- an X-Wix-Request-Id response header, or assets on Wix's CDN
What Wix changes
The check that catches Wix sites is the server-rendering one, and it catches a specific kind of site: pages where the copy is populated by Velo code after load. The text is there for a person and absent for a crawler, which is the worst version of this failure because nothing looks wrong when you check it yourself.
Read your site the way a crawler does
This is the fastest way to catch the Velo problem. If the text you expect is missing from the output, it is arriving after load and no engine that does not run JavaScript will ever see it.
In a terminal
curl -s https://yourdomain.com | grep -o "your key sentence"Add the Organization block in the structured data field
Settings → SEO → Structured data markup. Wix generates schema for some page types on its own, which is useful and is not an Organization statement — that one has to be yours, and sameAs is the part that matters.
Check the robots.txt editor rather than assuming
Settings → SEO → Robots.txt editor. It writes the live file immediately, which is convenient and means an experiment from months ago is still in effect. Wix's default lets the AI crawlers through, so a block here was added by somebody.
The readiness checks on Wix
CueScout runs eight checks on whether an answer engine can read a site at all. These are the ones whose answer is different on Wix. The rest are the same everywhere.
Not possible here
llms.txt present and parseable
Wix has no way to serve a plain-text file from your root. The nearest honest thing is a well-structured page and good schema; skip this check.
How to fix it here
Organization schema with sameAs links
Settings → SEO → Structured data markup lets you paste custom JSON-LD site-wide. Wix generates its own schema for some page types, which is not the same as an Organization block with sameAs.
How to fix it here
Content readable without JavaScript
Wix server-renders most page types now. A fail here usually means the copy sits in a Velo-populated element that renders after load, and the fix is to put the text in the page rather than fetch it.
These describe Wix’s own settings, which move without warning us. Last checked against the product on 2026-08-14.
What this does not do
- No root-level file access, so /llms.txt cannot be served.
- The structured data field is site-wide. Per-page markup — an FAQPage block on one page only — is harder to control on Wix than on platforms with per-page code injection.
- CueScout reads your published site over HTTP and does not connect to your Wix account.
Questions
Why would a Wix site fail the JavaScript check when the page looks fine?
Because you are looking at it in a browser, which runs the JavaScript. If the copy is placed by Velo after load, a crawler that does not execute scripts sees an empty shell. Fetching the raw HTML is the only way to tell.
Does Wix block AI crawlers by default?
No. The default robots.txt lets them through. A block on a Wix site was written into the robots.txt editor by somebody with access.
Is llms.txt worth switching platforms for?
No. It is a warn, not a failure, and no engine refuses to read a site without one. It is a convenience for assistants, not a gate.
Related
All integrationsSee where your Wix site stands
The readiness check is free, needs no signup and takes about half a minute. It works out what your site is built on and gives you the fixes written for it.