robots.txt & llms.txt across the Tranco top 1M
Data as of 2026-09-07 · robots.txt via Common Crawl CC-MAIN-2026-34 + our polite crawl · llms.txt via our polite crawl · Tranco list XN67N (2026-09-03T22:00:02.533886) · 1,000,000 panel domains 1,212,578 robots.txt fetches · 740,113 parsed · 56,498 llms.txt probes

Two public profiles · no score or winner

cloudflareinsights.com and mysql.com

cloudflareinsights.com #501 mysql.com #502

Measured takeaway

Botfy does not have comparable evidence for a strong policy takeaway; the available states are shown below.

Measured in Botfy's 2026-09-07 publication.

At a glance

A difference appears only when both sites have comparable evidence. Unavailable or unresolved observations remain incomplete.

Evidencecloudflareinsights.com mysql.com
robots.txt Returned HTTP 301 Served and parsed
Google crawl posture Open Open
Unnamed crawler fallback Unavailable Partly Restricted they inherit the wildcard (*) group's rules
Base /llms.txt Related file observed at /ai.txt; /llms.txt not established Not found when probed

Treatment by purpose

Only resolved blocked, allowed, or mixed states count as a policy agreement or difference. Unnamed agents still inherit each site's wildcard rules.

Declared purposecloudflareinsights.com mysql.com
Model training Observation unavailable Not explicitly addressed
AI search Observation unavailable Not explicitly addressed
Live assistant fetch Observation unavailable Not explicitly addressed
Opt-out directives Observation unavailable Not explicitly addressed
Ambiguous / undocumented Observation unavailable Not explicitly addressed

Named agents

Measured differences appear first. “Not explicitly addressed” is not the same as allowed; the site's wildcard fallback governs that crawler.

Agentcloudflareinsights.com mysql.com
gptbot OpenAI Observation unavailable Not explicitly addressed
claudebot Anthropic Observation unavailable Not explicitly addressed
oai-searchbot OpenAI Observation unavailable Not explicitly addressed
perplexitybot Perplexity Observation unavailable Not explicitly addressed
chatgpt-user OpenAI Observation unavailable Not explicitly addressed
claude-user Anthropic Observation unavailable Not explicitly addressed

How each site compares with its own rank peers

The sites may belong to different rank bands. Each percentage keeps its own population and denominator; Botfy does not subtract rates from unlike cohorts.

Traitcloudflareinsights.com mysql.com
Wildcard group Parsing unavailable 95.1% Ranks 1–1,000 · n=529 Yes 95.1% Ranks 1–1,000 · n=529
Effectively open file Parsing unavailable 11.3% Ranks 1–1,000 · n=529 No 11.3% Ranks 1–1,000 · n=529
Sitemap declared Parsing unavailable 66.0% Ranks 1–1,000 · n=529 No 66.0% Ranks 1–1,000 · n=529
robots.txt served No 53.3% Ranks 1–1,000 · n=1,000 Yes 53.3% Ranks 1–1,000 · n=1,000
robots.txt returned 404 No 4.6% Ranks 1–1,000 · n=1,000 No 4.6% Ranks 1–1,000 · n=1,000
Over the RFC parse limit Parsing unavailable 0.8% Ranks 1–1,000 · n=529 No 0.8% Ranks 1–1,000 · n=529
Blanket disallow Parsing unavailable 8.9% Ranks 1–1,000 · n=529 No 8.9% Ranks 1–1,000 · n=529
How this comparison is measured

Both sites use Botfy's latest published observations. A missing fetch, unresolved agent verdict, and measured absence are different states. Peer percentages use each site's exclusive Tranco rank band and print their own denominator. Populations, sources, and limits →

Keep comparing

Each suggestion replaces one side using an editorial collection or current rank proximity. Neither means the sites have similar policies.