Does blocking AI training bots hurt AI visibility? Search eligibility holds, but 'costs nothing' is overstated
Blocking GPTBot or ClaudeBot leaves ChatGPT and Claude search eligibility intact, but Google-Extended also controls Gemini Apps grounding. Across 3,115 ChatGPT entity questions, search visibility rose with training-data visibility, and no study has measured what a training-only block costs.
The advice to block AI training bots and allow the answering bots, at no cost to AI visibility, is Overstated. OpenAI documents its training crawler and its search crawler as separate robots.txt switches, so the retrieval half holds OpenAI · 2024. Google-Extended also controls grounding in Gemini Apps, so one of the three tokens usually named is not training-only Google · 2024. The one outcome study finds the median GPTBot blocker at 0.003 ChatGPT citations per Google organic appearance, against 0.417 for sites allowing it cloro · 2026. What leaving the training data costs has never been measured.
Blocking GPTBot or ClaudeBot leaves ChatGPT and Claude search eligibility intact
OpenAI documents GPTBot and OAI-SearchBot as independent robots.txt controls. GPTBot crawls content used to train foundation models, while OAI-SearchBot decides whether a site appears in ChatGPT search answers OpenAI · 2024. The publisher FAQ states the same split: a site must allow OAI-SearchBot to appear in ChatGPT search, and disallowing GPTBot opts content out of training OpenAI · 2026. Where both bots are allowed, OpenAI may crawl a page once and share the result between the two uses.
Anthropic runs the same design with three agents Anthropic · 2026. ClaudeBot collects training data, Claude-SearchBot indexes for search and Claude-User fetches pages on demand, each blockable on its own. Apple's Applebot-Extended governs training for Apple's foundation models, while Applebot keeps feeding Apple search Apple · 2025. For these three vendors, the retrieval half of the claim is first-party documented.
Blocking Google-Extended affects Gemini, not Google Search or AI Overviews
Google-Extended is a robots.txt control token with no separate crawler, and Google gives it two jobs Google · 2024. It governs whether crawled content may train future Gemini models. It also governs grounding in Gemini Apps and in Grounding with Google Search on Vertex AI. Grounding is retrieval at answer time, the half the claim treats as untouched.
Google states that the token does not affect inclusion or ranking in Google Search Google · 2024. AI Overviews and AI Mode need nothing beyond standard indexing and snippet eligibility Google · 2025. A Google-Extended block is therefore free in Search and AI Overviews, and not free in the Gemini app.
Removing a site from AI Overviews takes a different lever, a Search Console control that Google says leaves AI training to Google-Extended Google · 2026. One quarterly crawler report still labels Google-Extended's role "Training opt-out", omitting grounding TechnologyChecker.io · 2026. Of the three tokens in the usual snippet, that is the one the claim mislabels.
Sites that block GPTBot are cited far less by ChatGPT, for reasons the data cannot separate
The only study matching robots.txt rules to citation outcomes by token cuts against "costs nothing". Across 1,058 prominent domains, the median GPTBot blocker earned 0.003 ChatGPT citations per Google organic appearance, against 0.417 for allowers cloro · 2026. It is one vendor, a two-day citation window and a correlational design: Tier C, treat as provisional.
The usual rebuttal is that blocklists also block OAI-SearchBot. The study's own block rates limit that reading, with 13.9% of domains blocking GPTBot at the root against 3.4% for OAI-SearchBot cloro · 2026. At least three in four GPTBot blockers therefore left OAI-SearchBot open in robots.txt.
Site type explains part of the gap. GPTBot blockers were also cited about half as often by Perplexity, 0.566 against 1.143, an engine GPTBot does not feed cloro · 2026. A halving on an unrelated engine points to who blocks, and the ChatGPT gap is more than a hundred times larger.
Edge rules are the other blind spot, because a robots.txt crawl cannot see them. Cloudflare's Training category judges multi-purpose crawlers by all their behaviours, so a training block also blocks them Lee · Cloudflare · 2026. Site owners have reported verified Googlebot and Bingbot receiving HTTP 403 after setting that block, in a report that is anecdotal Montti · Search Engine Journal · 2026.
Training-data visibility tracks AI search visibility in the first disclosed-method study
The claim assumes training data carries no visibility value, and the first disclosed-method evidence points the other way. Across 3,115 entity-question pairs on logged-out ChatGPT, search visibility rose with parametric visibility in every mention-rate bin Druck et al. · Graphite · 2026. Parametric visibility is what a model says about an entity from its weights, without searching. The design is correlational, covers entity-comparison prompts only and does not test a block.
A network-traffic analysis shows one route for that link. In 21 of 27 ChatGPT conversations, the model's first search query already named brands the user never typed Mohanadasan · Snippet Digital; Keyword Insights · 2026. Brands named that way reached the answer 68.9% of the time, against 2.1% for brands only fetched. It is a single-account Tier C study, with a reproducible mechanism and unreproduced magnitudes.
The retrieval path still carries most of the weight on discovery prompts. Across 34,960 unbranded observations, brands appeared in 2.8% of GPT answers when neither brand nor own domain reached retrieval Tannenbaum · Aiso Boost Ltd · 2026. With the own domain cited, the figure rose to 49.0%. That study is observational and vendor-authored.
The opposite advice now circulates: allow GPTBot, ClaudeBot, Google-Extended and CCBot so models learn the brand. The paper behind it calls those tactics exploratory and its crawler advice inference, because training sets are undisclosed Druck et al. · Graphite · 2026. No study shows that allowing training crawlers changes what a model says about a brand.
No study has yet measured what a training-only block costs a brand
The only causal estimate cannot isolate training. News publishers that blocked LLM crawlers lost about 7% of weekly visits within six weeks, an effect confined to the top 50 publishers Zhao · Rutgers Business School; The Wharton School, University of Pennsylvania · 2026. Those blocks bundled training and retrieval agents before May 2024, and the paper is not peer reviewed.
The counterweight is weaker and points the other way. Across more than 6,000 publisher sites, Raptive found no statistically significant traffic change from blocking AI bots Griffin · Raptive · 2025. It discloses no cohort sizes or test, and it never measured citations. Neither study covers brand or retail sites.
Timing makes the gap slow to close. Recent models reached users 2.4 to 4.6 months after their knowledge cutoff Druck et al. · Graphite · 2026. The parametric study treats that gap as the minimum time for new content to reach a model's weights. A before-and-after test of a training block therefore has to span at least one model release.
Three designs would settle the question. One would match training-only blocks to citations, with edge rules observed and site type controlled. Another would track brand mentions with search switched off across a model release that followed a GPTBot block. A third would rerun the publisher analysis on post-2024 data, with GPTBot and OAI-SearchBot separated.
FAQFrequently Asked Questions
Sources
Sources are tiered per our methodology & sources page.
Your site, your rules: new AI traffic options for all customers (Content Independence Day 2026)
Cloudflare · Jin-Hee Lee, Bryan Becker · 2026
Cloudflare replaced its single 'AI bots' block with three categories, available to all customers: Search (indexes to answer later, expected to return referrals), Agent (real-time action for a person) and Training (absorbed into a model). From 15 September 2026, new domains block Training and Agent by default on pages showing ads, while Search stays allowed. Multi-purpose crawlers are judged by all behaviors, so blocking Training also blocks them.
Methodology note
Official Cloudflare product and policy announcement (its second 'Content Independence Day') by Jin-Hee Lee and Bryan Becker, published 1 July 2026. Also introduces a robots.txt content-use signal (immediate/reference/full, default reference), a redefinition of 'Verified' bots, and a transitive-trust proposal using the Forwarded header (RFC 7239). Verified by direct fetch and by TechCrunch and Cloudflare's own changelog.
OpenAI's publisher FAQ states that to appear in ChatGPT search, sites must allow OAI-SearchBot in robots.txt. Disallowed pages may still surface as a bare link and title in ChatGPT Atlas when OpenAI obtains the URL from a third-party search provider; publishers can prevent this with a noindex tag. Disallowing GPTBot opts content out of training.
Methodology note
First-party help-center documentation from OpenAI (last updated approximately June 2026). Normative, not empirical. The page was behind a bot challenge to automated fetch; content was read directly in a browser session during this run, confirming the OAI-SearchBot, third-party-link and GPTBot statements and the absence of any sitemap guidance.
Search generative AI control (Search Console Help)
Google · 2026
Google's Search Console control has three states, include (default), exclude or inherit from parent, covering AI Overviews, AI Mode and generative features in Discover. Excluded sites get no traffic or impressions and cannot be grounding input, though other sites' similar content remains. Inheritance runs from domain to subdomain to URL-prefix properties, and a child can be set independently, so path-scoped exclusion is possible today.
Methodology note
First-party Google Search Console help documentation for the Search generative AI control, fetched directly on 2026-08-24; platform documentation, not a study, and the rollout still reached only some site owners. Four stated carve-outs: not a ranking signal elsewhere, no override of Merchant Center or Google Ads, content may still power language understanding, and no effect on AI training, which remains Google-Extended's job.
Strategic Response of News Publishers to Generative AI (SSRN working paper)
Rutgers Business School; The Wharton School, University of Pennsylvania · Hangcheng Zhao, Ron Berman · 2026
News publishers that blocked LLM crawlers in robots.txt lost about 7% of weekly visits within six weeks (SimilarWeb ATT -0.074, 95% CI -0.141 to -0.007), with matching Semrush (-0.069) and Comscore human-panel (-0.065, not significant) estimates. The effect is confined to the top 50 publishers; ranks 101 to 500 show none. Blocks bundled training and retrieval agents before May 2024.
Methodology note
SSRN working paper by Hangcheng Zhao (Rutgers) and Ron Berman (Wharton), current version dated 2026-04-15, revised 2026-04-21, not peer reviewed. Staggered difference-in-differences (Callaway-Sant'Anna) on 30 core newspaper domains, November 2022 to May 2024, three traffic sources and three placebo tests. SSRN returned an empty page to direct fetch; figures cross-verified via PPC Land (2026-04-26) and independent search extracts.
Anthropic Crawler Documentation (ClaudeBot, Claude-User, Claude-SearchBot)
Anthropic · 2026
Anthropic operates three distinct web crawlers with separate robots.txt user agents: ClaudeBot collects content for training foundation models, Claude-User fetches pages on demand when users ask Claude a question, and Claude-SearchBot indexes content for Claude's search features. Each can be allowed or blocked independently, letting site owners opt out of training while still appearing in Claude's search answers. All three respect robots.txt and support the non-standard Crawl-delay directive.
Methodology note
Official Anthropic crawler documentation, formalised in updates throughout 2025. The page was inaccessible to direct fetch; user-agent strings, behaviour and robots.txt rules were confirmed against Anthropic's Claude Help Center article and multiple secondary references (Search Engine Journal, Search Engine Land, Search Engine Roundtable) reporting the same three-bot framework.
Apple uses one crawler, Applebot, to gather data that powers Spotlight, Siri, and Safari search. A separate user agent, Applebot-Extended, governs whether content is used to train Apple's foundation models, including Apple Intelligence. Sites can disallow Applebot-Extended in robots.txt to opt out of generative AI training while keeping content discoverable in Apple search. Applebot is identified via reverse DNS at applebot.apple.com or a published IP CIDR list.
Methodology note
Official Apple support documentation about Applebot, last updated April 25, 2025. The page details user-agent strings, robots.txt behavior, supported meta directives such as noindex, nosnippet, nofollow, and how Applebot-Extended works as a secondary control specifically for generative AI training.
Google AI Overviews and Your Website | Google Search Central
Google · 2025
Google states there are no extra technical requirements for appearing in AI Overviews or AI Mode beyond being indexed and eligible for a standard search snippet. SEO fundamentals apply: allow crawling in robots.txt, maintain internal linking, keep pages findable. Google describes the query fan-out technique, where the system issues multiple related searches across subtopics, and reports that clicks from AI Overview pages tend to be higher quality.
Methodology note
Official Google Search Central documentation describing how AI features such as AI Overviews and AI Mode interact with websites, and what site owners can and cannot do to influence inclusion. Direct fetch failed; content was verified against the live Google AI Features and AI Optimization Guide pages on developers.google.com plus corroborating secondary coverage.
Google Common Crawlers Overview (incl. Google-Extended)
Google · 2024
Google lists its common crawlers with their robots.txt tokens and the products each affects. Google-Extended has no separate user agent; it is a control token that governs whether crawled content may train future Gemini models and be used for grounding in Gemini Apps and Grounding with Google Search on Vertex AI. Google states it does not affect inclusion or ranking in Google Search.
Methodology note
Official Google Search Central documentation listing the common Googlebot variants and their robots.txt tokens. The page was inaccessible to direct fetch; user-agent strings, IP-range publication mechanism and reverse-DNS verification process were confirmed through the live developers.google.com URL referenced in search results and supporting third-party crawler reference databases.
OpenAI Crawlers Documentation (GPTBot, OAI-SearchBot, ChatGPT-User)
OpenAI · 2024
OpenAI documents three distinct user agents, controllable independently via robots.txt. OAI-SearchBot surfaces sites inside ChatGPT search results; blocking it removes a site from those answers but still allows navigational links. GPTBot crawls content used to train foundation models. ChatGPT-User performs on-demand fetches triggered by user prompts, Custom GPTs and GPT Actions. Sites that allow both OAI-SearchBot and GPTBot may be crawled only once, with results shared between use cases.
Methodology note
Official OpenAI developer documentation listing each crawler, its full user-agent string and its published IP-range JSON file (searchbot.json, gptbot.json, chatgpt-user.json). The page sets out which robots.txt directives apply to each agent, the approximate 24-hour lag for search opt-outs to take effect, and the policy that user-initiated ChatGPT-User requests are not governed by robots.txt.
Parametric Knowledge Optimization (Graphite)
Graphite · Gregory Druck et al. · 2026
Graphite reports that models released since July 2026 had knowledge cutoff gaps of 4.6 months for OpenAI (n=5), 2.4 for Anthropic (n=4) and 4.4 for Google (n=3), which the authors treat as the minimum time before new content can reach a model's weights. In 3,115 entity-question pairs on logged-out ChatGPT, search visibility rose with parametric visibility in every mention-rate bin; correlational.
Methodology note
Vendor research paper by Gregory Druck, Ethan Smith and Bevin Benson of Graphite, published 16 October 2026 and read directly. Gaps use vendor documentation and model cards (30.44 days a month; Anthropic training-data cutoff); the visibility experiment is correlational, logged-out ChatGPT, collected August 2026, with two replications. The authors call the PKO tactics exploratory.
robots.txt AI Crawler Report Q3 2026: Who Gets Blocked (TechnologyChecker, Cloudflare Radar data)
TechnologyChecker.io · 2026
In Cloudflare Radar's 28 September 2026 snapshot of 4,242 robots.txt files, every training crawler is disallowed more often than allowed (GPTBot 1.60:1, ClaudeBot 1.58:1, Google-Extended 1.38:1) while OAI-SearchBot (0.91:1) is allowed as often as blocked. Over twelve months, Allow rules naming GPTBot rose from 2.51% to 7.69% of files; September's disallow drop likely reflects a sample change.
Methodology note
Vendor report by TechnologyChecker.io, first published 2026-04-03 and updated 2026-10-01, re-querying named Cloudflare Radar API endpoints (robots_txt directive, crawl_refer_ratio, crawl_purpose) and normalising counts by files parsed per snapshot. Fetched directly. Counts cover Cloudflare's sample of top domains rather than the whole web; the vendor flags September as provisional.
From Prompt to Recommendation: A Fitted Stage Model of Brand Visibility in AI Search (arXiv 2609.23162)
Aiso Boost Ltd · Benjamin Tannenbaum · 2026
Across 34,960 unbranded prompt-engine observations from 75 Aiso client projects (June to September 2026), brands were mentioned in 2.8% of GPT and 3.8% of Gemini answers when neither the brand nor its own domain appeared in the live retrieval path, but 49.0% and 58.4% when the own domain was cited without a branded fan-out. Within-prompt odds ratios: 15.3 GPT, 29.7 Gemini. Observational, not causal.
Methodology note
arXiv preprint 2609.23162 (cs.IR), submitted 19 September 2026 by Benjamin Tannenbaum of Aiso Boost Ltd, a GEO vendor analysing its own anonymised client projects; not peer reviewed. Three cohorts: real-user prompts with ChatGPT fan-outs, page match versus citations, and 160 repeated ChatGPT runs. Cochran-Mantel-Haenszel estimates stratified by organisation and prompt. HTML full text read directly.
Report That Cloudflare AI Bot Blocking Prevents Googlebot From Indexing Sites
Search Engine Journal · Roger Montti · 2026
Site owners report that setting Cloudflare's AI Training block returns HTTP 403 to verified Googlebot and Bingbot fetching their sitemaps, because Cloudflare classifies both as Search plus Training crawlers. Google's John Mueller asked the reporter for details. Cloudflare's own documentation confirms mixed-purpose crawlers are blocked by every training-block configuration including the legacy Block AI bots toggle, from 15 September 2026.
Methodology note
Trade-press news report by Roger Montti for Search Engine Journal, 4 August 2026, fetched directly 14 September 2026. Built on a single r/TechSEO thread plus a verbatim quote of Cloudflare's block-ai-bots documentation. The article states explicitly that the report is anecdotal and that user error is not ruled out. No sample, no incidence rate.
ChatGPT Already Knows Who's In The Running Before It Searches
Snippet Digital; Keyword Insights · Suganthan Mohanadasan · 2026
In 21 of 27 ChatGPT conversations, the model's first search query already named brands the user never typed, before any page was fetched. Brands named in ChatGPT's own query reached the final answer 68.9% of the time against 2.1% for brands whose pages were fetched but never named. Only 110 of 3,554 retrieved pages were cited (3.1%), falling from 5.2% to 0.3% by position within a domain group.
Methodology note
Single-researcher study by Suganthan Mohanadasan, published 10 August 2026 and updated 17 August, read from PDF on 2026-08-24. One ChatGPT Plus account in Dubai, 24-25 July 2026: 57 conversations for citation figures and 27 for the first-query test, weighted toward software and AI tools. The author calls percentages directional and flags personalisation and tokenisation errors; the mechanism is reproducible, the magnitudes are not.
Do Sites That Block GPTBot Get Cited Less by ChatGPT? (cloro, 1,058 domains)
cloro · 2026
Across 1,058 prominent domains, the median GPTBot-blocking domain earned 0.003 ChatGPT citations per Google organic appearance, against 0.417 for domains allowing GPTBot; OAI-SearchBot blockers scored 0. Training crawlers were blocked far more often than retrieval bots (GPTBot 13.9%, ClaudeBot 15.4%, CCBot 17.8% vs OAI-SearchBot 3.4%, ChatGPT-User 6.2%). Correlational; the vendor states it cannot prove causation.
Methodology note
Vendor study by cloro, published 2026-07-06. robots.txt fetched for the 1,058 most-cited or most-ranking domains in cloro's corpus (88% resolved); a block is a root-level Disallow for the agent's group or for * where the agent has no group. Citation propensity is citations per Google-organic appearance over a two-day window; domains without organic appearances excluded. Fetched directly 2026-10-12.
Why We Still Recommend Blocking AI Crawlers (Raptive network traffic analysis)
Raptive · Trey Griffin · 2025
Across the Raptive network of over 6,000 publisher sites, June 2024 to May 2025, sites blocking one or more AI bots showed no statistically significant traffic change against sites that did not, with average variation across cohorts within one percent. As of July 2025 roughly 40 percent of Raptive sites blocked GPTBot and nearly 10 percent blocked Google-Extended. Traffic only; AI citations were never measured.
Methodology note
Vendor blog post by Trey Griffin, Raptive, published 21 July 2025 and modified 24 July, fetched directly 14 September 2026. Discloses only the network size and the date window. Analysed N, cohort sizes and definitions, traffic metric and significance test are all absent, and the bolded conclusion upgrades a null result to a positive claim of no effect.
About the author Max Ackermann
Max Ackermann is founder and Managing Director of info.link, the product data platform that makes brands visible in AI search and connects every physical product to the web through GS1 Digital Link. He writes about AI search and generative engine optimization (GEO), AI-powered commerce, and how brands can structure product data for ChatGPT, Gemini, Perplexity, and retailer AI assistants like Amazon Rufus. For the past two years he has built the pipelines that put structured product data into AI answers, and run the experiments that test what actually moves AI citations.
Max has 20+ years of experience building digital products and businesses. He previously led McKinsey's Corporate Venture and Design teams across Europe, and as Managing Director of a leading US digital agency he built platforms with Nike, Google, Meta, and Airbnb. He founded the UX Design program at Central Saint Martins College, University of the Arts London, and is a Fellow of the UK's Higher Education Academy. Based in Hamburg, he works closely with GS1 on Digital Link adoption; info.link is headquartered in Hamburg and Berlin and counts GS1 Germany among its investors.
Follow Max on LinkedIn.


