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

gsxt.gov.cn and yellowpages.com

gsxt.gov.cn #7,865 yellowpages.com #7,863

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.

Evidencegsxt.gov.cn yellowpages.com
robots.txt Returned HTTP 521 Served and parsed
Google crawl posture Blocked Open
Unnamed crawler fallback Unavailable Partly Restricted they inherit the wildcard (*) group's rules
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 purposegsxt.gov.cn yellowpages.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 Blocked

Named agents

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

Agentgsxt.gov.cn yellowpages.com
gptbot OpenAI Observation unavailable Not explicitly addressed
claudebot Anthropic Observation unavailable Not explicitly addressed
oai-searchbot OpenAI Observation unavailable Not explicitly addressed
chatgpt-user OpenAI Observation unavailable Not explicitly addressed
claude-user Anthropic Observation unavailable Not explicitly addressed
scrapy Scrapy Observation unavailable Blocked

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.

Traitgsxt.gov.cn yellowpages.com
Wildcard group Parsing unavailable 94.1% Ranks 1,001–10,000 · n=5,437 Yes 94.1% Ranks 1,001–10,000 · n=5,437
Effectively open file Parsing unavailable 16.4% Ranks 1,001–10,000 · n=5,437 No 16.4% Ranks 1,001–10,000 · n=5,437
Sitemap declared Parsing unavailable 65.6% Ranks 1,001–10,000 · n=5,437 No 65.6% Ranks 1,001–10,000 · n=5,437
robots.txt served No 60.7% Ranks 1,001–10,000 · n=9,037 Yes 60.7% Ranks 1,001–10,000 · n=9,037
robots.txt returned 404 No 5.4% Ranks 1,001–10,000 · n=9,037 No 5.4% Ranks 1,001–10,000 · n=9,037
Over the RFC parse limit Parsing unavailable 0.2% Ranks 1,001–10,000 · n=5,437 No 0.2% Ranks 1,001–10,000 · n=5,437
Blanket disallow Parsing unavailable 3.7% Ranks 1,001–10,000 · n=5,437 No 3.7% Ranks 1,001–10,000 · n=5,437
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.