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

betsapi.com and clerk.com

betsapi.com #14,762 clerk.com #14,761

Measured takeaway

Both sites block model-training crawlers.

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.

Evidencebetsapi.com clerk.com
robots.txt Served and parsed Served and parsed
Google crawl posture Open Open
Unnamed crawler fallback Allowed the wildcard (*) group is effectively open Partly Restricted they inherit the wildcard (*) group's rules
Base /llms.txt Not probed Published

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 purposebetsapi.com clerk.com
Model training Blocked Blocked
AI search Not explicitly addressed Blocked
Live assistant fetch Blocked Not explicitly addressed
Opt-out directives Blocked Not explicitly addressed
Ambiguous / undocumented Not explicitly addressed 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.

Agentbetsapi.com clerk.com
CCBot Common Crawl Blocked Blocked
Bytespider ByteDance Blocked Blocked
GPTBot OpenAI Blocked Not explicitly addressed
ClaudeBot Anthropic Blocked Not explicitly addressed
meta-externalagent Meta Blocked Not explicitly addressed
Cohere-ai Cohere Not explicitly addressed Blocked
YouBot You.com Not explicitly addressed Blocked
Amazonbot Amazon Blocked Not explicitly addressed
Google-Extended Google Blocked Not explicitly addressed
Applebot-Extended Apple Blocked 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.

Traitbetsapi.com clerk.com
Wildcard group Yes 92.1% Ranks 10,001–100,000 · n=54,147 Yes 92.1% Ranks 10,001–100,000 · n=54,147
Effectively open file Yes 22.6% Ranks 10,001–100,000 · n=54,147 No 22.6% Ranks 10,001–100,000 · n=54,147
Sitemap declared No 61.7% Ranks 10,001–100,000 · n=54,147 Yes 61.7% Ranks 10,001–100,000 · n=54,147
robots.txt served Yes 59.7% Ranks 10,001–100,000 · n=91,507 Yes 59.7% Ranks 10,001–100,000 · n=91,507
robots.txt returned 404 No 7.9% Ranks 10,001–100,000 · n=91,507 No 7.9% Ranks 10,001–100,000 · n=91,507
Over the RFC parse limit No 0.2% Ranks 10,001–100,000 · n=54,147 No 0.2% Ranks 10,001–100,000 · n=54,147
Blanket disallow No 4.0% Ranks 10,001–100,000 · n=54,147 No 4.0% Ranks 10,001–100,000 · n=54,147
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.