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

alibaba.com and media-amazon.com

alibaba.com #303 media-amazon.com #302

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.

Evidencealibaba.com media-amazon.com
robots.txt Served and parsed Fetch failed: dns_error
Google crawl posture Open Blocked
Unnamed crawler fallback Partly Restricted they inherit the wildcard (*) group's rules Unavailable
Base /llms.txt Related file observed at /ai.txt; /llms.txt not established 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 purposealibaba.com media-amazon.com
Model training Blocked Observation unavailable
AI search Not explicitly addressed Observation unavailable
Live assistant fetch Not explicitly addressed Observation unavailable
Opt-out directives Blocked Observation unavailable
Ambiguous / undocumented Not explicitly addressed Observation unavailable

Named agents

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

Agentalibaba.com media-amazon.com
GPTBot OpenAI Blocked Observation unavailable
claudebot Anthropic Not explicitly addressed Observation unavailable
chatgpt-user OpenAI Not explicitly addressed Observation unavailable
claude-user Anthropic Not explicitly addressed Observation unavailable
Google-Extended Google Blocked Observation unavailable

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.

Traitalibaba.com media-amazon.com
Wildcard group Yes 95.1% Ranks 1–1,000 · n=529 Parsing unavailable 95.1% Ranks 1–1,000 · n=529
Effectively open file No 11.3% Ranks 1–1,000 · n=529 Parsing unavailable 11.3% Ranks 1–1,000 · n=529
Sitemap declared No 66.0% Ranks 1–1,000 · n=529 Parsing unavailable 66.0% Ranks 1–1,000 · n=529
robots.txt served Yes 53.3% Ranks 1–1,000 · n=1,000 Fetch failed: dns_error 53.3% Ranks 1–1,000 · n=1,000
robots.txt returned 404 No 4.6% Ranks 1–1,000 · n=1,000 Fetch failed: dns_error 4.6% Ranks 1–1,000 · n=1,000
Over the RFC parse limit No 0.8% Ranks 1–1,000 · n=529 Parsing unavailable 0.8% Ranks 1–1,000 · n=529
Blanket disallow No 8.9% Ranks 1–1,000 · n=529 Parsing unavailable 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.