logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·01.11.26
← Back to news

Cloudflare's new AI traffic options for customers

Original article
blog.cloudflare.com|178 points|135 comments|by alphabetatango|Jul 25, 2026

Cloudflare's Enhanced AI Traffic Management for Site Owners

By Jin-Hee Lee and Bryan Becker | July 1, 2026 | 📖 13 minute read

One year ago, Cloudflare inaugurated the first Content Independence Day, providing website administrators with the tools necessary to reclaim authority over their digital assets.

For three decades, a silent agreement existed between crawlers and publishers: crawlers index content, and in exchange, publishers receive referral traffic. This equilibrium has collapsed. Modern AI systems often ingest data without providing any reciprocal value, creating an existential crisis for content creators.

To combat this, Cloudflare initially introduced a simplified "Block AI Bots" toggle and a Pay-Per-Crawl marketplace.

The Need for Nuance

While the initial focus was on stopping uncompensated AI training, the conversation has evolved. Content owners recognize that a binary "block all" approach is too blunt. For smaller websites, the risk of being invisible to search engines is often more dangerous than the risk of being used for training.

This creates a precarious situation, often described as a Faustian bargain:

"Either you permit AI to train on your data to maintain search visibility, or you block the bots and risk total digital obscurity."

This dynamic unfairly benefits established search giants who utilize the same bots for both indexing and training, while forcing new competitors to be deceptive to survive. Furthermore, search is evolving; Google and its peers are transitioning from link directories to answer engines that provide direct responses on the results page.

Because the definition of "AI" is a moving target, Cloudflare is shifting its focus from what a bot is to what a bot does.


A Pragmatic Taxonomy of AI Traffic

To provide better control, Cloudflare has developed a behavioral classification system. Rather than a simple "AI vs. Non-AI" label, traffic is now categorized by its specific intent.

The Three Primary AI Use Cases

CategoryPrimary ActionKey CharacteristicExpected Outcome
SearchIndexing/CollectingProactively building a database for future queries.Referral traffic or fair compensation.
AgentReal-time ExecutionActing on a human's behalf to complete a task.Completion of a specific user job.
TrainingModel AbsorptionIngesting data to fine-tune or build a model.Permanent integration into AI architecture.

Examples of these in the wild:

  • Agents: ChatGPT-User or agents like Gemini/Claude interacting with a browser.
  • Training: Large-scale crawlers harvesting datasets for LLM weights.
  • Search: Traditional and AI-enhanced indexing bots.

The Logic of Classification

Cloudflare believes in transparency. We encourage bot operators to use distinct crawlers for different purposes. If a single entity performs all three functions, they should ideally deploy three separate bots.

We also recognize that some bots are multi-purpose. In such cases, they will be tagged with all applicable labels rather than just one.


New Management Capabilities

Cloudflare is expanding these granular controls to all customers, including those on the Free tier.

Previously, the "Block AI bots" preset was a broad brush that primarily targeted training bots:

Existing AI Bot Settings - July 2025

Now, users can independently toggle access for Search, Agent, and Training traffic.

New Granular AI Options - July 2026

Summary of New Features:

  • Granular control over Search bots.
  • Granular control over Agent bots.
  • Granular control over Training bots.
  • Availability for Free tier users.
  • Multi-purpose bot tracking.

The Value Exchange Formula

The tension between publishers and AI can be expressed as a simple mathematical imbalance:

Value Received<Content Value+Server Cost\text{Value Received} < \text{Content Value} + \text{Server Cost}Value Received<Content Value+Server Cost

Cloudflare's goal is to help site owners shift this equation toward:

Referrals+Compensation≥Content Value\text{Referrals} + \text{Compensation} \geq \text{Content Value}Referrals+Compensation≥Content Value

Implementation and Future Defaults

To protect the ecosystem, Cloudflare is updating its default security posture.

Effective September 15, 2026: For all new domains joining the Cloudflare network, the following rules will apply by default to pages that display advertisements:

  1. Training bots →\rightarrow→ Blocked
  2. Agent bots →\rightarrow→ Blocked

This can be represented in a pseudo-configuration rule:

{
  "default_policy": {
    "onboarding_date": "2026-09-15",
    "target_pages": "ad_supported",
    "actions": {
      "ai_training": "BLOCK",
      "ai_agent": "BLOCK",
      "ai_search": "ALLOW"
    }
  }
}

By providing these tools, Cloudflare ensures that the "Content Independence Day" spirit continues, allowing every site owner to define their own rules for the AI era.