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

americancompass.org and randommer.io

americancompass.org #500,746 randommer.io #500,748

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.

Evidenceamericancompass.org randommer.io
robots.txt Served and parsed Served and parsed
Google crawl posture Open Open
Unnamed crawler fallback Allowed the wildcard (*) group is effectively open Unrestricted no wildcard (*) group exists, so no rule applies to them at all
Base /llms.txt Not probed Not 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 purposeamericancompass.org randommer.io
Model training Not explicitly addressed Not explicitly addressed
AI search Not explicitly addressed Not explicitly addressed
Live assistant fetch Not explicitly addressed Not explicitly addressed
Opt-out directives Not explicitly addressed 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.

Agentamericancompass.org randommer.io
gptbot OpenAI Not explicitly addressed Not explicitly addressed
claudebot Anthropic Not explicitly addressed Not explicitly addressed
oai-searchbot OpenAI Not explicitly addressed Not explicitly addressed
perplexitybot Perplexity Not explicitly addressed Not explicitly addressed
chatgpt-user OpenAI Not explicitly addressed Not explicitly addressed
claude-user Anthropic Not explicitly addressed 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.

Traitamericancompass.org randommer.io
Wildcard group Yes 89.6% Ranks 100,001–1,000,000 · n=680,000 No 89.6% Ranks 100,001–1,000,000 · n=680,000
Effectively open file Yes 26.0% Ranks 100,001–1,000,000 · n=680,000 No 26.0% Ranks 100,001–1,000,000 · n=680,000
Sitemap declared Yes 60.6% Ranks 100,001–1,000,000 · n=680,000 Yes 60.6% Ranks 100,001–1,000,000 · n=680,000
robots.txt served Yes 61.8% Ranks 100,001–1,000,000 · n=1,111,034 Yes 61.8% Ranks 100,001–1,000,000 · n=1,111,034
robots.txt returned 404 No 8.5% Ranks 100,001–1,000,000 · n=1,111,034 No 8.5% Ranks 100,001–1,000,000 · n=1,111,034
Over the RFC parse limit No 0.3% Ranks 100,001–1,000,000 · n=680,000 No 0.3% Ranks 100,001–1,000,000 · n=680,000
Blanket disallow No 10.8% Ranks 100,001–1,000,000 · n=680,000 No 10.8% Ranks 100,001–1,000,000 · n=680,000
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.