Quick answer: On Wix, you block AI crawlers by editing your site's robots.txt in the SEO Dashboard (SEO Settings → Tools and settings → Robots.txt Editor). You can't touch server files or .htaccess on Wix — it's a closed platform — so robots.txt is your main lever, plus a couple of workarounds for crawlers that ignore it. Here's the full walkthrough, including which bots to block and how to verify it worked.
Why Wix makes AI-crawler control a little tricky
Wix hosts your site on its own servers, which means three things you get for free and two things you don't get at all. You get: automatic SSL, a default robots.txt, and managed infrastructure. You don't get: .htaccess or server config access, or raw server logs.
On WordPress or a self-hosted site, robots.txt is just one layer — you can add IP blocks, rate limits, or Cloudflare firewall rules on top. On Wix, there is no "top" you control. That makes the robots.txt editor the single most important tool for the job, and it makes choosing the right tokens matter more, because a bot that ignores robots.txt has nothing else on Wix to stop it. (Cloudflare firewall rules still work if Wix sites route through Cloudflare? No — Wix sites use Wix's own CDN, so Cloudflare WAF can't sit in front of a Wix site. Your enforcement layer is robots.txt plus Wix's built-in security features.)
The good news: the major AI labs' crawlers — OpenAI's, Anthropic's, Meta's — do honor robots.txt, so for the bots most site owners care about, the Wix editor is enough.
Step 1: Open the robots.txt editor
- In your Wix dashboard, go to SEO Dashboard (left sidebar) or Marketing & SEO → SEO Dashboard.
- Under Tools and settings, click Go to Robots.txt Editor.
- Click View File to see your current robots.txt.
- Add your rules under the "This is your current file" section, then save.
Two prerequisites worth knowing: the editor is available on premium plans with a connected domain — Wix doesn't let you customize robots.txt on a free wixsite.com address in the same way. And give crawlers time to notice the change; bots cache robots.txt for up to 24 hours.
Step 2: Add the AI-crawler blocklist
Wix's default robots.txt already handles the basics (blocking things like /feed/ and search internals). Don't delete the default lines — append your AI rules below them. Here's a solid starting blocklist for 2026:
# --- Block AI training crawlers ---
User-agent: GPTBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /This blocks the training bots — the crawlers that feed model training — while leaving Googlebot, Bingbot, and the AI answer-engine bots (like OAI-SearchBot for ChatGPT search and PerplexityBot) untouched. That split matters: blocking GPTBot does not remove you from Google Search, and blocking OAI-SearchBot would remove you from ChatGPT's answers. Most Wix owners who want AI visibility without donating content to training datasets use exactly this configuration.
If you'd rather block everything AI-related including answer engines, add groups for OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, and Meta-WebIndexer with Disallow: / too. Just know the tradeoff before you do.
Step 3: Understand what Wix can't do
Honesty time — there are limits, and you should know them before they surprise you:
- No server-level blocking. No .htaccess rules, no nginx configs, no IP deny lists. If a crawler ignores robots.txt, Wix gives you no direct way to force it out at the edge.
- No server logs. You can't grep access logs to see if GPTBot actually stopped visiting, the way self-hosted owners can. Verification has to be indirect (see below).
- User-triggered fetchers may ignore robots.txt. Bots like ChatGPT-User and Perplexity-User fetch pages when a real user asks about them, and their makers say robots.txt "may not apply" in that context. This is true on every platform, not just Wix — but on Wix you have no fallback layer.
What Wix does offer: its built-in security and bot protection. If you're seeing aggressive scraping, check your site settings for bot-protection/CAPTCHA options and contact Wix support about abusive traffic patterns — they can act at the platform level even when you can't.
Step 4: Verify your rules actually work
Since you can't read server logs on Wix, verify from the outside:
- Check the file is live. Open
yourdomain.com/robots.txtin a browser (or our free robots.txt tester) and confirm your new rules appear. - Test individual URLs. Google Search Console's robots.txt tester (under Settings → robots.txt) lets you enter a URL and a user agent to see whether it's allowed or blocked. It works for any user-agent string you type in, including GPTBot.
- Watch for re-crawls. Bots that respect robots.txt typically back off within days. You won't see this in Wix logs, but you may notice the crawler's requests stop appearing in any third-party analytics you run.
- Use Search Console for Google-Extended. Since Google-Extended is just a permission token (it has no crawler of its own), verification means checking you haven't hurt normal indexing — confirm your pages are still indexed in Search Console a week after the change.
The AI crawler decision every Wix owner should make
Before you paste a blocklist, decide what you actually want. There are three common positions:
- Block training, allow answers (most common). Block GPTBot, ClaudeBot, Google-Extended, CCBot. Stay visible in Google Search, ChatGPT search, and Perplexity answers. Good for blogs, portfolios, and businesses that want traffic.
- Block everything AI. Add the answer-engine bots too. Good for paywalled content, licensing plays, or sites whose business model is selling access to content.
- Allow everything (deliberate). Some sites want to be in training data and AI answers for maximum visibility. That's a valid choice too — but make it a choice, not an accident of the default settings.
Our longer guide on whether to block AI crawlers at all walks through the pros and cons in detail, and the complete list of AI crawler user agents covers every token worth knowing.
What to do if a crawler ignores your Wix robots.txt
Some crawlers have a documented history of brushing off robots.txt — Bytespider (ByteDance's training crawler) drew public criticism for it in 2023, and various stealth scrapers never declare themselves at all. On a platform where you can't add firewall rules, your options are:
- Wait and re-check — compliance is usually good from the big labs, and most "ignoring" reports turn out to be cached robots.txt or a different bot with a similar name.
- Use Wix's bot protection features and report abusive patterns to Wix support.
- For truly critical content, keep it behind member logins or paywalls — authentication is the only real barrier, on any platform.
Don't have a robots.txt ready to paste? Our free robots.txt generator builds one with AI-crawler presets — copy the output into the Wix editor and you're done.
The flip side: explicitly allowing AI crawlers on Wix
Not everyone wants to block. If your Wix site is a portfolio, a local business, or a blog that lives on discovery, being in AI answers is free visibility. On Wix, allowing is the default — crawlers treat an absent rule as allowed — but there's value in writing it explicitly, because explicit Allow rules document your intent and override any broader Disallow you add later:
# Explicitly welcome AI answer engines (documents intent)
User-agent: OAI-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-SearchBot
Allow: /You can also go further than robots.txt allows and actively court AI citations: keep your pages fast, use clear headings that answer questions directly, add FAQ sections, and publish an llms.txt-style summary page. Our guide on getting cited by ChatGPT covers the full playbook — everything in it works on Wix.
Monitoring AI crawler traffic on Wix without server logs
The lack of server logs is Wix's biggest weakness for crawler control, but you're not completely blind. Here's what you can use:
- Wix Analytics traffic reports. They won't name individual bots, but sudden traffic spikes from unknown sources — especially bandwidth-heavy ones with no corresponding page views from humans — are a classic crawler signature.
- Google Analytics 4 bot filtering. GA4 automatically excludes known bots from reports, which is the opposite of what you want here — but third-party analytics tools like Cloudflare Web Analytics (if you route a subdomain through it) or Plausible can show bot traffic separately.
- Search Console crawl stats. The Settings → Crawl stats report shows you Googlebot's behavior in detail. It won't show GPTBot, but it confirms your robots.txt isn't accidentally throttling the crawlers you want.
- Honeypot pages. Advanced users create a page linked only from robots.txt's Disallow lines (never from navigation). Any human-like visit to that page is, by definition, a bot that read your robots.txt and came anyway. It's a crude but effective compliance check that works on any platform, Wix included.
Frequently asked questions
Can I edit robots.txt on a free Wix site?
Wix's robots.txt editor requires a premium plan with a connected domain. On a free wixsite.com address you get Wix's default robots.txt, which you can't customize the same way. Upgrade and connect your domain to unlock the editor.
Does blocking GPTBot on Wix hurt my Google rankings?
No. GPTBot is OpenAI's training crawler; blocking it has no effect on Google Search. Blocking Google-Extended (the Gemini training token) also has no effect on Search. Only blocking Googlebot itself would hurt rankings — don't do that by accident.
Can I use .htaccess on Wix to block bots?
No. Wix is a closed platform with no server-file or .htaccess access. Robots.txt is your primary crawler-control tool, and it's the only layer you can edit directly.
How do I check if an AI crawler visited my Wix site?
Wix doesn't expose raw server logs, so you can't grep for bot user agents the way self-hosted owners do. Verify indirectly: confirm your rules are live at yourdomain.com/robots.txt, test with Search Console's robots.txt tester, and watch third-party analytics for changes in crawler traffic.
What's the difference between blocking GPTBot and OAI-SearchBot?
GPTBot crawls for OpenAI's model training — blocking it opts you out of training. OAI-SearchBot crawls so ChatGPT can cite your site in search answers — blocking it removes you from ChatGPT answers. They are separate bots with separate robots.txt tokens, so you can block one and allow the other.
Will Wix's default robots.txt block AI crawlers?
No. Wix's default robots.txt handles Wix-internal paths and lets all standard crawlers through. AI-crawler tokens like GPTBot and ClaudeBot are not in the default file — you have to add them yourself in the robots.txt editor.
