Why Websites Are Blocking AI Agents — and What It Means for the Internet
More websites now decide which AI systems may read them, and some charge for the privilege. Here is how the blocking actually works, what changed in 2026, and what it could do to the open web.

The short answer
The useful distinction is not 'humans versus AI.' It is who is accessing content, for which purpose, under which permissions, and with what return to its creator. Search indexing, model training, answering a question and making a purchase can look like similar web requests but carry very different economic and legal relationships. Websites now have real technical tools to separate these purposes—and the choices they make will shape how open the internet stays.
More websites now decide which AI systems may read them, and some charge for the privilege. Here is how the blocking actually works, what changed in 2026, and what it could do to the open web.
01 / The story
Five kinds of 'AI traffic' that are not the same
When a website says it blocks 'AI,' it may mean very different things. A search crawler builds an index so people can find pages. An AI training crawler collects material to train models. An AI search or answer engine retrieves sources to compose answers, often with links. A scraper extracts information—a broad technique, not a synonym for AI or for illegality. And a user-directed agent fetches pages or drives a browser for a specific person's current task. [1, 2]
These categories overlap in practice. OpenAI, for example, documents separate crawlers—GPTBot for training, OAI-SearchBot for search, and user-triggered access—and says search and training preferences are independent. Cloudflare classifies traffic into Search, Agent and Training categories. One crawl can serve more than one allowed purpose, and the categories are functional distinctions, not mutually exclusive legal ones. [1, 2]
| Category | Purpose | Important qualification |
|---|---|---|
| Search crawler | Builds an index used to find pages | Search products can also generate answers |
| AI training crawler | Collects material for training models | Blocking future collection does not delete old training data |
| AI search/answer engine | Retrieves sources to compose answers | Retrieval is not the same process as model training |
| Scraper | Extracts structured or unstructured data | A technique, not a synonym for AI or illegality |
| User-directed agent | Fetches pages for a person's current task | User authorization is not automatically the website's permission |
02 / The story
Access and permission are different questions
Robots.txt is the web's traditional 'please don't' note. The standard behind it, RFC 9309, is explicit: these are requests that cooperative crawlers are asked to honor—not access authorization. It is neither a password wall nor a copyright license. [5]
Technical enforcement is different. Cloudflare can reject classified traffic at its network edge, which actually stops requests rather than asking nicely. Rate limits constrain how much traffic is allowed without banning everything. Bot detection decides which policy applies; rate limiting decides how much is permitted. Neither establishes ownership or reuse rights. [3, 4, 6, 10]
And licensing is a third layer. Permission to fetch a page is not permission to reproduce it, redistribute it or train a model on it. Conversely, paying for access does not automatically buy every downstream right. The RSL standard, published as version 1.0 in December 2025, explicitly separates machine-readable usage terms, authorization and payment for exactly this reason. [7]
03 / The story
What changed in 2025 and 2026
On July 1, 2025, Cloudflare announced permission-based default blocking of AI crawlers and launched 'pay per crawl' in private beta, using the HTTP 402 'Payment Required' status code to let sites allow, block or charge for access. This was one company's product policy—not an internet-wide ban, and the beta launch does not prove widespread adoption or meaningful publisher revenue. [3, 6]
The system then got more granular. A July 1, 2026 changelog, effective September 15, 2026, documented separate Search, Agent and Training controls. New-domain defaults block Training and Agent traffic on ad-displaying pages while leaving Search allowed—so a simple 'Cloudflare blocks all AI bots by default' headline is now outdated. [2]
On September 15, 2026, Cloudflare launched a 'Disallow AI Training' option and an 'Accountable' designation for mixed-use crawlers, with Apple, Google and Microsoft designated as meeting requirements or committing to specified timelines. That does not mean every operator already enforces every control. Cloudflare's goal of summary-length controls in early 2027 is a roadmap commitment, not an available feature. [4]
04 / The story
Why site owners are doing this
The concerns are economic and legal, and they are related but separate. Cloudflare describes a weakening exchange in which sites provide content but receive fewer visits than under conventional search—treat that as the vendor's and publishers' rationale, not proof that every AI answer destroys a visit. Automated requests also consume real infrastructure resources. [3, 6, 8]
Reddit's lawsuit against Anthropic shows how contested this is. Reddit filed its California complaint on June 4, 2025, alleging breach of contract, unjust enrichment, trespass to chattels, tortious interference and unfair competition—not simply copyright infringement. Anthropic disputed the claims. On March 30, 2026, a federal court sent the dispute back to California state court. That remand was a jurisdictional decision, not a finding that Anthropic unlawfully scraped Reddit, and the federal docket's 'terminated' label does not mean the state case ended. [8, 9, 11, 12]
Meanwhile, licensing is becoming a market. OpenAI and News Corp announced a multiyear agreement on May 22, 2024, covering access to current and archived journalism; the announcement does not disclose a price, so reported valuations should not be presented as company-confirmed. RSL 1.0, published December 10, 2025, defines a machine-readable vocabulary for usage, licensing and payment terms—an industry specification, not legislation, and not evidence that all AI companies accept its terms. [13, 14]
05 / The story
What this means for everyone else
Publishers gain granular control—they can stay discoverable in search while refusing training—but blocking may also reduce their visibility in AI answers, and licensing tends to favor organizations with distinctive content and bargaining power. [1, 2, 3, 4, 13]
Developers should identify their purpose honestly, honor site policies, budget their requests and prefer authorized APIs or feeds. A user-agent label alone is not strong proof of identity, and access policy and permitted reuse are separate checks. [1, 5, 6, 7]
Retailers face a real dilemma: blanket blocking can also obstruct legitimate shopping and comparison agents. Distinguishing catalog discovery from cart operations and account actions is a policy design worth doing deliberately. [2]
And users may face a trade-off between convenient delegated browsing and incomplete coverage. An internet fragmented into paid or selectively accessible sources is a plausible outcome—not an established inevitability. The open web's next decade depends on how these controls, licenses and court cases settle.
A closer look
What we verified and what stays uncertain
This guide is desk research based on standards documents, company announcements, court filings and technical documentation, checked on October 17, 2026. Vendor bot categories are operational classifications, not neutral measurements of the whole web.
Uncertain as of publication: how many sites enforce the new controls, whether pay-per-crawl revenue is meaningful for publishers, and how courts will rule on the pending disputes. There is no verified universal figure for AI-driven server costs or lost publisher revenue.
Put it to work
How to read any 'website blocks AI' story
Before drawing conclusions, check:
0 of 5 considered
These questions are editorial guidance, not a product score or verified assessment.
Keep learning
Further reading
- AI Agent Security: Prompt Injection, Safe Tools, and Containment
Qlauson · Artificial Intelligence
- ChatGPT and Your Browser: What Can AI Actually See, Read and Do?
Qlauson · AI Tools
- What Are APIs? How Apps, AI Tools, and Software Connect
Qlauson · Software and Development
- Overview of OpenAI Crawlers — OpenAI, living documentation, retrieved Oct 17, 2026
External resource · Separate GPTBot, OAI-SearchBot and user-triggered access documentation. Opens in a new tab.
- New options to manage AI traffic — Cloudflare developer changelog, Jul 1, 2026
Primary documentation · Separate Search, Agent and Training controls effective Sep 15, 2026. Checked Oct 17, 2026. Opens in a new tab.
- Cloudflare Just Changed How AI Crawlers Scrape the Internet-at-Large — Cloudflare, Jul 1, 2025
Primary documentation · Permission-based default blocking announcement. Checked Oct 17, 2026. Opens in a new tab.
- Cloudflare Helps End the Search-or-AI-Training Tradeoff — Cloudflare, Sep 15, 2026
Primary documentation · Disallow AI Training and Accountable crawler designation. Checked Oct 17, 2026. Opens in a new tab.
- RFC 9309: Robots Exclusion Protocol — IETF, Sep 2022
Primary documentation · The standard; explicitly not access authorization. Checked Oct 17, 2026. Opens in a new tab.
- Introducing pay per crawl — Cloudflare Blog, Jul 1, 2025
Primary documentation · Private beta using HTTP 402; adoption and revenue unproven. Checked Oct 17, 2026. Opens in a new tab.
- Really Simple Licensing (RSL) 1.0 Specification — RSL Technical Steering Committee, Dec 10, 2025
Primary documentation · Machine-readable usage, licensing and payment vocabulary. Checked Oct 17, 2026. Opens in a new tab.
- Reddit, Inc. v. Anthropic, PBC — Complaint, California Superior Court, Jun 4, 2025
Primary documentation · Contract, unjust enrichment and other claims; allegations, not adjudicated facts. Checked Oct 17, 2026. Opens in a new tab.
- Reddit sues AI startup Anthropic — Reuters, Jun 4, 2025
Primary documentation · Reporting on the filing and Anthropic's dispute of the claims. Checked Oct 17, 2026. Opens in a new tab.
- RFC 6585: Additional HTTP Status Codes — IETF, Apr 2012
Primary documentation · Background protocol reference for rate limiting (429). Checked Oct 17, 2026. Opens in a new tab.
- Order on Motion to Remand, Reddit v. Anthropic — U.S. District Court, N.D. Cal., Mar 30, 2026
Primary documentation · Remand to state court; a jurisdictional decision, not a merits finding. Checked Oct 17, 2026. Opens in a new tab.
- Reddit privacy case against Anthropic kicked back to state court — Courthouse News Service, Mar 30, 2026
Primary documentation · Reporting on the remand. Checked Oct 17, 2026. Opens in a new tab.
- A landmark multi-year global partnership with News Corp — OpenAI, May 22, 2024
Primary documentation · Licensing example; price not disclosed in the announcement. Checked Oct 17, 2026. Opens in a new tab.
- New RSL Web Standard and Collective Rights Organization — RSL Internet Collective, Sep 10, 2025
Primary documentation · Announcement of the licensing initiative. Checked Oct 17, 2026. Opens in a new tab.
Read next
AI Agent Security: Prompt Injection, Safe Tools, and Containment
AI agents read untrusted text and take real actions. This guide explains prompt injection in plain language, how to give agents safer tools, and how to contain them so a mistake stays small.
Continue readingNewsletter
Get new Qlauson stories by email.
An occasional email when we publish a new guide or update an important one. No unrelated promotions, and you can unsubscribe from any email.


