Yes, you can block AI crawlers on Squarespace — but not the way you would on WordPress or a self-hosted site. Squarespace does not let you edit your robots.txt file directly. Instead, you flip one switch: go to Settings > Crawlers and check "Block known AI crawlers." Squarespace then rewrites your generated robots.txt file with Disallow rules for a list of known AI crawler tokens. That is the whole mechanism, and it comes with real limits you should understand before you rely on it.
In this guide, you will learn exactly where the setting lives, what it blocks, what it quietly misses, and what to do when the built-in toggle is not enough. If you run a Squarespace site and you do not want your content swept into AI training data or AI answers, this is the full picture.
Why Squarespace Handles Robots.txt Differently
On a self-hosted site, robots.txt is a plain text file you control. You open it, add a User-agent block, save it, and the change is live. Squarespace works differently: the platform generates your robots.txt file for you, and every Squarespace site gets the same base file.
That base file already blocks search engines from crawling Squarespace's own internal paths — things like /config/ (your admin login), /api/ (analytics), /search, and URL parameters such as ?tag=, ?month=, and ?author=. Those rules exist to keep duplicate and internal pages out of search results. You cannot change them, add to them, or remove them. There is no file to edit, no code injection trick that replaces robots.txt, and no support ticket that will open it up.
What Squarespace gives you instead is a settings panel with two checkboxes. That panel is your entire robots.txt control surface. Once you accept that, the rest of this guide is about using it correctly — and knowing when to add a second layer of protection outside Squarespace.
Step by Step: Turn On the AI Crawler Block
Here is the exact process:
- Log in to your Squarespace site and open Settings.
- Click Crawlers. (On some older plans the path is Settings > Advanced > Crawlers and Indexing, but the panel is the same.)
- You will see two options: "Block search engine crawlers" and "Block known AI crawlers."
- Check only "Block known AI crawlers." Leave the search engine box unchecked.
- Save. The change is reflected in your robots.txt file right away.
Now verify it. Open yourdomain.com/robots.txt in your browser and look for the AI crawler tokens with Disallow: / rules under them. If you see them, the toggle is live. You can also paste your robots.txt into the free robots.txt tester and check how it treats specific user agents such as GPTBot or CCBot.
One checkbox, one minute, and your site has a machine-readable AI opt-out. The hard part is not flipping the switch — it is understanding what the switch does and does not cover.
What the Toggle Actually Blocks — and What It Misses
The "Block known AI crawlers" toggle is a bulk control. Squarespace introduced the toggle after photographers and other creators raised concerns about their work being crawled for AI training.
When it is off — the default — the AI crawler tokens are still named in the generated robots.txt file, but they sit in the same group as the wildcard rule and carry no blocking rule of their own. In practice, that means they are allowed. When you check the box, Squarespace applies Disallow rules to its list of roughly two dozen known AI crawler tokens, including GPTBot, ClaudeBot, CCBot, Bytespider, and Google-Extended.
That sounds complete. It is not. Here are the gaps that matter:
1. It does not cover AI search and answer bots
Training crawlers and AI search crawlers are different bots with different user-agent tokens. The toggle targets the training side. It does not cover tokens such as OAI-SearchBot (ChatGPT search) or ChatGPT-User (the fetcher that visits a page when a ChatGPT user asks about it), and it does not cover Perplexity's fetchers either. So a Squarespace site with the toggle on can still be cited in AI answers. If your goal is to disappear from AI answers entirely, the toggle alone will not get you there.
2. It is all or nothing
You cannot block one AI crawler and allow another. There is no per-bot list to edit. If you want GPTBot blocked but PerplexityBot allowed (because Perplexity sends cited traffic back), Squarespace's panel cannot express that choice.
3. It only covers bots Squarespace has listed
New AI crawlers appear regularly, and smaller or less transparent scrapers may never make Squarespace's list. A robots.txt rule only constrains bots that identify themselves with a listed token and choose to obey robots.txt. A scraper that ignores robots.txt, or that uses a made-up user agent, walks straight past this toggle.
4. Robots.txt is a request, not a lock
Even for the bots it names, robots.txt is a polite request. Honest crawlers from OpenAI, Google, Anthropic, and the other major providers honor it. Dishonest scrapers do not. Treat the toggle as a policy statement, not as enforcement.
The One Box You Must Not Check
The panel's other checkbox — "Block search engine crawlers" — blocks Googlebot, Bingbot, and other search crawlers, along with Google's AdsBots. Checking it removes your site from search engines. That is the nuclear option, and it is almost never what a site owner wants.
If you only want to opt out of AI crawling, check the AI box and leave the search engine box alone. If both boxes are checked, your site disappears from Google as well as from AI crawlers. If you ever see a sudden traffic collapse after touching this panel, this is the first thing to check: open the Crawlers panel and confirm the search engine box is unchecked.
Per-Page Control: Hiding Individual Pages
Sometimes you do not want to block AI crawlers site-wide. You want to protect one thing: a paid course, a client gallery, an unpublished portfolio. Squarespace gives you two page-level tools:
- Hide from search results: In a page's SEO settings, you can mark it to be hidden from search results. This adds a noindex signal for that page. It is the right tool when a page should exist but should not be indexed or surfaced.
- Password-protect the page: A password-protected page cannot be crawled at all, because the crawler cannot log in. This is the strongest option Squarespace offers for a single page, and it works against every bot, honest or not.
Remember that hiding a page from search results is not the same as blocking crawlers from fetching it. A noindex page can still be fetched and read; it just should not appear in search results. If the content must never be read by a bot, password protection is the answer.
When the Toggle Is Not Enough: Adding Cloudflare
If you need per-bot control, enforcement against scrapers that ignore robots.txt, or protection for newer bots Squarespace has not listed, add a layer in front of Squarespace: Cloudflare.
Point your domain's DNS at Cloudflare (its free plan is enough for this), then go to Security > Bots in the Cloudflare dashboard and turn on "AI Scrapers and Crawlers". Cloudflare maintains that blocklist and updates it as new AI bot fingerprints appear, and it enforces the block at the network edge — meaning the request never reaches your Squarespace site. Because Cloudflare can also use behavioral signals rather than just the user-agent string, it catches scrapers that robots.txt never could.
For even finer control, Cloudflare's WAF lets you write custom rules for individual user agents. That is how you get the per-bot granularity Squarespace's panel cannot give you: block GPTBot, allow PerplexityBot, challenge anything that looks like a scraper. If you are on Squarespace and serious about crawler control, this combination — Squarespace toggle for the policy, Cloudflare for enforcement — is the practical setup.
One caution: if you use Cloudflare's bot blocking, keep your Squarespace toggle on as well. The two layers agree with each other, and the robots.txt policy still matters for bots that read it before they ever hit your edge.
How to Verify It Worked
- Read your robots.txt. Visit
yourdomain.com/robots.txtand confirm the AI crawler tokens now carryDisallow: /rules. If the file looks unchanged, the setting did not save — go back and check the box again. - Test specific bots. Use the robots.txt tester to confirm how your file treats GPTBot, ClaudeBot, CCBot, and any other token you care about.
- Watch your logs. Squarespace's own analytics will not show you bot traffic. If you run Cloudflare in front, its analytics will show you blocked bot requests — the clearest proof the enforcement layer is working.
- Give it time. Crawlers re-fetch robots.txt on their own schedule. A bot that visited yesterday may not re-read your file today. Expect the change to take effect over days, not minutes, and do not treat one stray visit as proof the toggle failed.
Common Mistakes Squarespace Owners Make
- Checking both boxes and accidentally deindexing the site from Google. Check only the AI box.
- Assuming the toggle removes content from AI answers. It targets training crawlers. AI search and user-triggered fetchers are separate bots.
- Assuming it removes content already in a model. Robots.txt controls future crawling. It cannot delete content from a model that already trained on it, and it cannot remove an already-indexed page — that needs a noindex tag or a removal request.
- Assuming "listed in robots.txt" means "blocked." With the toggle off, the AI tokens are named in the file but effectively allowed. The checkbox is what turns names into rules.
- Trying to hand-edit robots.txt through code injection. Squarespace's code injection cannot replace the generated robots.txt. If someone sells you a snippet that claims to do this, it does not work.
Should You Block AI Crawlers on Squarespace?
For most Squarespace owners — photographers, designers, writers, small businesses — the answer is: turn the toggle on if you are uncomfortable with your work feeding AI training data, and leave it off if you want maximum exposure in AI answers. There is no universal right answer. A photographer whose portfolio is their livelihood has a strong case for blocking. A local business that wants every possible citation in AI answers has a strong case for staying open.
What matters is making the choice deliberately, understanding the toggle's limits, and adding Cloudflare if you need enforcement or per-bot control. If you later migrate off Squarespace to WordPress or another platform, read our guide on blocking AI crawlers on WordPress — there you get the full robots.txt control Squarespace does not offer. For the broader picture, see the complete list of AI crawlers and the Wix AI crawler guide, which has a similar platform-toggle problem.
FAQ
Can I edit robots.txt on Squarespace?
No. Squarespace generates the robots.txt file automatically and does not offer a way to edit it. Your only built-in controls are the two checkboxes under Settings > Crawlers, plus per-page hide-from-search and password-protection options.
Does the "Block known AI crawlers" toggle hurt my Google ranking?
No, as long as you leave "Block search engine crawlers" unchecked. The AI toggle targets AI crawler tokens only. Googlebot and Bingbot keep crawling and indexing your site normally.
Will the toggle stop ChatGPT from citing my site?
Not by itself. ChatGPT search and user-triggered fetches use different tokens (OAI-SearchBot and ChatGPT-User) that the toggle does not cover. To control those, you need enforcement at the edge, such as Cloudflare WAF rules, or a platform that lets you write custom robots.txt rules.
How long does it take for the toggle to work?
The robots.txt file updates immediately, but crawlers re-fetch robots.txt on their own schedules. Expect the change to take effect over several days. A single bot visit shortly after you flip the switch is usually a crawler working from a cached copy of your old file.
Can I block just one AI crawler on Squarespace?
Not with Squarespace's built-in settings — the toggle is all or nothing. For per-bot control, put Cloudflare in front of your site and write WAF rules for the specific user agents you want to block or allow.
Does the toggle stop scrapers that ignore robots.txt?
No. Robots.txt is a voluntary standard. Scrapers that ignore it will keep fetching. For those, you need server- or edge-level enforcement, such as Cloudflare's AI Scrapers and Crawlers toggle or WAF rules.
Bottom line: on Squarespace, blocking AI crawlers means one checkbox under Settings > Crawlers — the "Block known AI crawlers" toggle. It is a solid first step for opting out of AI training crawls, but it is a bulk, policy-only control with real gaps. Pair it with Cloudflare if you need enforcement, per-bot control, or protection from scrapers that ignore robots.txt. And if you want full robots.txt control, that is a reason to consider a platform that lets you edit the file yourself.
