In short: Wix ships a ready-made way to block AI crawlers, and the list it suggests names GPTBot, ChatGPT-User, CCBot and BingAI together.
Two of those do different jobs. GPTBot collects for training; ChatGPT-User fetches a page because somebody is asking a question right now. Blocking both is the decision this course spends a module warning about, made in one click.
Wix is right that it should not significantly affect your SEO. That is the point: the cost does not land on search, it lands on being named in answers.
What The Setting Actually Contains
Wix's own documentation puts it in the dashboard under SEO and GEO, in the robots.txt editor, and names the crawlers it targets: CCBot, GPTBot, ChatGPT-User and BingAI, with a note that you can add more.
It is an honest feature honestly documented. Wix says plainly that some crawlers ignore robots.txt so it is not airtight, and that blocking should not significantly impact your SEO. Both are true.
The part a reader has to supply is what the list mixes together, and Meet the AI Crawlers is the separation: training collection, live retrieval and search indexing are three jobs with three different costs when blocked.
Reading The Reassurance Correctly
"Should not significantly impact your SEO" is accurate and it is answering a different question than the one you are asking.
Search rankings are not what you lose. What you lose is presence in answers being generated while the block is on, because the agent that fetches a page to answer a live question is on the same list as the one that collects training data.
So the sentence is not reassurance about AI visibility. It is a correct statement that the two are separate, and it is the reason to make this decision deliberately rather than by clicking the option that sounds protective.
Decide it as the business question it is. If your content is the product, blocking training collection is coherent. If your content exists to make you known, blocking the retrieval agent removes you from the place people now ask. Those are opposite answers and the button does not distinguish them, which is why Managing AI Crawler Access puts the commercial question before the file.
The Version Worth Writing Instead
Keep the agent that answers questions today, and decide separately about the one that collects for training. On Wix that means editing the rules rather than accepting the suggested set: name the training collector, leave the live fetcher alone, and write the date and the reason as a comment so the next person knows it was a decision.
Then check what is actually being served, because a settings screen is not a file:
curl -s https://example.com/robots.txtThe Three Levels Of Not Being Indexed
Wix lets you prevent indexing for one page, for a group of pages, or for the whole site, and its documentation notes that pages prevented from indexing may not appear in your sitemap.
That second part is the one with teeth. The sitemap is how a retrieval system learns a URL exists, so a page kept out of search is frequently a page kept out of retrieval, which is the same trap as the Shopify hiding mechanisms in The Three Ways to Disappear on Shopify.
The site-wide switch is worth auditing on any site you inherit. It survives rebuilds, it explains total absence, and nothing else on the dashboard hints that it is on.
Hiding a page from the menu is not hiding it from anything else. Menu visibility and indexing are separate settings, and a page taken out of the navigation stays in search and in the sitemap until somebody says otherwise. That cuts both ways: it is also why a forgotten page keeps being retrieved long after you stopped linking to it.
Key Takeaways
- Wix's suggested AI crawler block names GPTBot, ChatGPT-User, CCBot and BingAI together, and the first two do different jobs.
- Blocking the live fetcher removes you from answers being generated now, which is not an SEO cost and is why the SEO reassurance is not the reassurance you needed.
- Edit the rules rather than accepting the set: block what collects for training, keep what answers questions, and date the reason.
- Preventing indexing can also remove a page from the sitemap, which is how a retrieval system learns the URL exists.
- Hiding a page from the menu changes nothing about indexing in either direction.
Check yourself
Before you move on
Not scored, not recorded, and not part of the certificate. Both answers are settled by a sentence in this lesson, and the reasoning appears whichever option you pick.
- 01
Wix's suggested AI crawler block names CCBot, GPTBot, ChatGPT-User and BingAI together. What is the problem with applying it as one decision?
- 02
Wix says blocking AI crawlers should not significantly impact your SEO. How should that be read?