| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/ai-crawl-control/changelog/ | [Back] [Original] |
You can now configure advanced Pay Per Crawl settings for your zone, including:
crawler-price response header, or by using a Cloudflare Worker to set prices based on request properties.When dynamic pricing is enabled, Pay Per Crawl adds a cf-pay-per-crawl request header to origin requests so your origin or Worker can determine the appropriate price.
Refer to the Advanced configuration documentation for details.
Cloudflare's network now supports redirecting verified AI training crawlers to canonical URLs when they request deprecated or duplicate pages. When enabled via AI Crawl Control > Quick Actions, AI training crawlers that request a page with a canonical tag pointing elsewhere receive a 301 redirect to the canonical version. Humans, search engine crawlers, and AI Search agents continue to see the original page normally.
This feature leverages your existing <link rel="canonical"> tags. No additional configuration required beyond enabling the toggle. Available on Pro, Business, and Enterprise plans at no additional cost.
Refer to the Redirects for AI Training documentation for details.
AI Crawl Control now includes new tools to help you prepare your site for the agentic Interneta web where AI agents are first-class citizens that discover and interact with content differently than human visitors.
The Metrics tab now includes a Content Format chart showing what content types AI systems request versus what your origin serves. Understanding these patterns helps you optimize content delivery for both human and agent consumption.
The Robots.txt tab has been renamed to Directives and now includes a link to check your site's Agent Readiness score.
Refer to our blog post on preparing for the agentic Internet for more on why these capabilities matter.
AI Crawl Control now supports extending the underlying WAF rule with custom modifications. Any changes you make directly in the WAF custom rules editor such as adding path-based exceptions, extra user agents, or additional expression clauses are preserved when you update crawler actions in AI Crawl Control.
If the WAF rule expression has been modified in a way AI Crawl Control cannot parse, a warning banner appears on the Crawlers page with a link to view the rule directly in WAF.
For more information, refer to WAF rule management.
AI Crawl Control metrics have been enhanced with new views, improved filtering, and better data visualization.
[AI Crawl Control path patterns]
Path pattern grouping
/blog/*, /api/v1/*, /docs/*) to identify which site areas crawlers target most. Refer to the screenshot above.Enhanced referral analytics
Data transfer metrics
Image exports
Learn more about analyzing AI traffic.
New reference documentation is now available for AI Crawl Control:
Account administrators can now assign the AI Crawl Control Read Only role to provide read-only access to AI Crawl Control at the domain level.
Users with this role can view the Overview, Crawlers, Metrics, Robots.txt, and Settings tabs but cannot modify crawler actions or settings.
This role is specific for AI Crawl Control. You still require correct permissions to access other areas / features of the dashboard.
To assign, go to Manage Account > Members and add a policy with the AI Crawl Control Read Only role scoped to the desired domain.
The Overview tab is now the default view in AI Crawl Control. The previous default view with controls for individual AI crawlers is available in the Crawlers tab.
[AI Crawl Control Overview tab showing executive summary, metrics, and crawler groups]
Learn more about analyzing AI traffic and managing AI crawlers.
Pay Per Crawl is introducing enhancements for both AI crawler operators and site owners, focusing on programmatic discovery, flexible pricing models, and granular configuration control.
A new authenticated API endpoint allows verified crawlers to programmatically discover domains participating in Pay Per Crawl. Crawlers can use this to build optimized crawl queues, cache domain lists, and identify new participating sites. This eliminates the need to discover payable content through trial requests.
The API endpoint is GET https://crawlers-api.ai-audit.cfdata.org/charged_zones and requires Web Bot Auth authentication. Refer to Discover payable content for authentication steps, request parameters, and response schema.
Payment headers (crawler-exact-price or crawler-max-price) must now be included in the Web Bot Auth signature-input header components. This security enhancement prevents payment header tampering, ensures authenticated payment intent, validates crawler identity with payment commitment, and protects against replay attacks with modified pricing. Crawlers must add their payment header to the list of signed components when constructing the signature-input header.
Pay Per Crawl error responses now include a new crawler-error header with 11 specific error codes for programmatic handling. Error response bodies remain unchanged for compatibility. These codes enable robust error handling, automated retry logic, and accurate spending tracking.
Site owners can now offer free access to specific pages like homepages, navigation, or discovery pages while charging for other content. Create a Configuration Rule in Rules > Configuration Rules, set your URI pattern using wildcard, exact, or prefix matching on the URI Full field, and enable the Disable Pay Per Crawl setting. When disabled for a URI pattern, crawler requests pass through without blocking or charging.
Some paths are always free to crawl. These paths are: /robots.txt, /sitemap.xml, /security.txt, /.well-known/security.txt, /crawlers.json.
AI crawler operators: Discover payable content | Crawl pages
Site owners: Advanced configuration
AI Crawl Control now supports per-crawler drilldowns with an extended actions menu and status code analytics. Drill down into Metrics, Cloudflare Radar, and Security Analytics, or export crawler data for use in WAF custom rules, Redirect Rules, and robots.txt files.
The Metrics tab includes a status code distribution chart showing HTTP response codes (2xx, 3xx, 4xx, 5xx) over time. Filter by individual crawler, category, operator, or time range to analyze how specific crawlers interact with your site.
[AI Crawl Control status code distribution chart]
Each crawler row includes a three-dot menu with per-crawler actions:
[AI Crawl Control crawler actions menu]
Learn more about AI Crawl Control.
AI Crawl Control now includes a Robots.txt tab that provides insights into how AI crawlers interact with your robots.txt files.
The Robots.txt tab allows you to:
robots.txt files across all your hostnames, including HTTP status codes, and identify hostnames that need a robots.txt file.robots.txt file, with breakdowns of successful versus unsuccessful requests.robots.txt files contain Content Signals directives for AI training, search, and AI input.robots.txt directives, including the crawler name, operator, violated path, specific directive, and violation count.robots.txt request data by crawler, operator, category, and custom time ranges.When you identify non-compliant crawlers, you can:
To get started, go to AI Crawl Control > Robots.txt in the Cloudflare dashboard. Learn more in the Track robots.txt documentation.
AI Crawl Control now provides enhanced metrics and CSV data exports to help you better understand AI crawler activity across your sites.
Visualize crawler activity patterns over time, and group data by different dimensions:
[AI Crawl Control requests over time chart with grouping tabs]Interactive chart showing crawler requests over time with filterable dimensions
Identify traffic sources with referrer analytics:
[AI Crawl Control top referrers breakdown]Bar chart showing top referrers and their respective traffic volumes
Download your filtered view as a CSV:
Learn more about AI Crawl Control.
We improved AI crawler management with detailed analytics and introduced custom HTTP 402 responses for blocked crawlers. AI Audit has been renamed to AI Crawl Control and is now generally available.
Enhanced Crawlers tab:
[Updated AI Crawl Control table showing request counts and trend charts]
Custom block responses (paid plans): You can now return HTTP 402 "Payment Required" responses when blocking AI crawlers, enabling direct communication with crawler operators about licensing terms.
For users on paid plans, when blocking AI crawlers you can configure:
[AI Crawl Control block response configuration interface]
Example 402 response:
HTTP 402 Payment Required
Date: Mon, 24 Aug 2025 12:56:49 GMT
Content-type: application/json
Server: cloudflare
Cf-Ray: 967e8da599d0c3fa-EWR
Cf-Team: 2902f6db750000c3fa1e2ef400000001
{
"message": "Please contact the site owner for access."
}
We are introducing a new feature of AI Crawl Control Pay Per Crawl. Pay Per Crawl enables site owners to require payment from AI crawlers every time the crawlers access their content, thereby fostering a fairer Internet by enabling site owners to control and monetize how their content gets used by AI.
[Pay per crawl]
For Site Owners:
For AI Crawler Owners:
Learn more in the Pay Per Crawl documentation.
We redesigned the AI Crawl Control dashboard to provide more intuitive and granular control over AI crawlers.
[Block AI crawlers]
[Analyze AI crawler activity]
To get started, explore:
Every site on Cloudflare now has access to AI Audit, which summarizes the crawling behavior of popular and known AI services.
You can use this data to:
robots.txt policy via an automatic WAF rule.
[View AI bot activity with AI Audit]
To get started, explore AI audit.
| Web Proxy Viewer | New URL | Original Page |