How to › Wix
llms.txt on Wix: it is generated for you, and it stops updating when you edit it
Wix generates this file for you and serves it at your site root. That is the good news. The part worth knowing before you touch it: Wix documents that once you edit the file, it stops updating automatically.
Can this platform serve the file at the exact path?
Yes — generated automatically, and editable.
Wix documents a file served at the site root that it auto-generates, with an editor and a reset. Sources: Understanding your site's llms.txt file and the llms.txt API introduction.
before you start
What you need first
- An upgraded site with a connected custom domain — Wix lists this as a prerequisite.
- Search-engine indexing enabled for the site, also listed as a prerequisite.
the steps
Read it first, then decide whether to take it over
- Look at what Wix already publishes for you. In your site’s dashboard, open SEO & GEO, scroll to Tools and settings, and choose Go to llms.txt, then View File. You can also just fetch
https://yourdomain/llms.txt. - Judge it against the questions buyers ask. Wix documents that the generated file only includes content that is already publicly available, and never exposes private, password-protected or member-only content. Which means if an answer is not published on your site, it is not in the file either.
- Edit it, if it needs your words. From the same screen: More Actions › Edit file › Continue, edit the text, then Save Changes.
- Understand what you just took on. Wix states that once you edit the file it stops updating automatically, so your changes are preserved. That is a fair trade and it has a cost: an edited file goes stale the day your site changes and nothing will tell you. Reset to Default hands it back to the automatic version.
- Check the live URL. Fetch
https://yourdomain/llms.txtand confirm the text is yours.
what breaks it
The ways this goes wrong on Wix
- Testing before the custom domain is connected. The prerequisites are documented; a check on the wrong hostname looks like a failure that is not one.
- Expecting site functions to serve the root path. Wix documents that its HTTP functions are served under
/_functions/, and that routers take a URL prefix — neither can own the bare/llms.txt. Source: site API calls. You do not need them anyway, which is the point of this page. - Editing and forgetting. The stale-file problem is the real risk on this platform. Put a reminder in whatever you use for the rest of your housekeeping.
verify it
Prove the file is really there
A file that looks published in an admin screen and returns anything other than a plain 200 at the exact path has not been published. Three checks, in order:
- Open
https://yourdomain/llms.txtin a private window. You want the raw text, not a styled page, and not a redirect to another path. - Confirm the first line is a level-one Markdown heading —
# Your Business. Google’s agent-readiness audit fails a file with no H1 heading anywhere in it, and the llms.txt specification puts the H1 first, so first is the safe place for it. - Confirm at least one Markdown link is present, in
[label](https://…)form. A file with no links in that form is reported as a failure by the same audit.
Then run it through the validator, which checks the same conditions and tells you which recommendation each one comes from. The package passes the llms.txt and page-structure checks of Google’s agent-readiness audit; the WebMCP audits cover interactive tools a fact package deliberately does not install. That is the claim we make about this file, and the only one. It does not improve your search position.
the honest part
This file is the compliance surface, not the mechanism
Publishing it is worth doing and takes ten minutes. What it will not do on its own is get you found: in a controlled test, agents given no pointer to the file opened it 0 times in 18 visits (Note 15), and in a census of nine real sites, seven published one and not one of them placed it where it gets read (Note 09).
What moved the numbers was putting the answers in the homepage itself, where a one-page reader lands: 78% of fact checks recovered against 30% in the control, with agents stopping after 1.1 pages on average (Note 41). Do this file because Google’s page-quality tooling checks for it and the package passes the llms.txt and page-structure checks of Google’s agent-readiness audit; the WebMCP audits cover interactive tools a fact package deliberately does not install. Do the fact block because it works.
Sources: MARKETING_NOTES_AGENT_VISIBILITY.md, Notes 09, 15, 41.
If somebody has told you this file moves your search position, read does llms.txt help SEO first — the answer is documented, and it is not the one they gave you.
other platforms
The same job elsewhere
free audit
See what AI sees on your site
The file is ten minutes of work. Whether your homepage answers a buyer's question is a different question, and it is the one we measure.
One model fetches your homepage and answers buyer questions from it. You get the recovery score and the specific answers it could not find. That is the whole free tier: it shows you the problem, and the fix package is not included.