Loading...
Loading...
17Module
Making Wix sites visible to AI systems. Working within Wix's constraints to maximize AI discoverability.
Available3 lessons18 min
On a hosted platform such as Wix you do not control rendering, so establish first with curl whether your pages arrive as text, because that is the only property a rewrite cannot fix. Everything else is yours: extraction is the words and their order, resolution is your own naming, and association is built by other people off your site entirely, which makes a rebuild the wrong first move. Wix offers a ready-made AI crawler block in its robots.txt editor naming CCBot, GPTBot, ChatGPT-User and BingAI together; GPTBot collects for training while ChatGPT-User fetches a page to answer a question somebody is asking right now, so applying the set as one decision removes you from live answers, and Wix's accurate note that this should not significantly impact SEO is answering a different question. Preventing indexing, whether for one page, a group or the whole site, can also remove a page from the sitemap, which is how a retrieval system learns the URL exists. Finally, a hosted site generates pages nobody wrote: read the sitemap rather than the dashboard, noindex public member and profile pages by hand, treat tag and filter URLs as navigation, and keep the community content, which is exactly what these systems draw on.
On a hosted platform the constraint feels total and is not. You do not own rendering; you do own the words and their order, your own naming, and everything that happens off the site, which is three of the four steps including the slowest and most valuable one.
What is genuinely platform-shaped here is the settings. One of them offers to block AI crawlers as a single decision, and the list it suggests puts a training collector and a live fetcher side by side. The other is the quiet inventory of pages nobody wrote.