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

i-spo.ru and rigidindustries.com

i-spo.ru #345,140 rigidindustries.com #345,139

Measured takeaway

i-spo.ru's robots.txt disallows every crawler; rigidindustries.com's does not.

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.

Evidencei-spo.ru rigidindustries.com
robots.txt Served and parsed Served and parsed
Google crawl posture Blocked Open
Unnamed crawler fallback Blocked the wildcard (*) group disallows everything, so they are blocked without being named 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 purposei-spo.ru rigidindustries.com
Model training Not explicitly addressed Blocked
AI search Not explicitly addressed Blocked
Live assistant fetch Not explicitly addressed Blocked
Opt-out directives Not explicitly addressed Blocked
Ambiguous / undocumented Not explicitly addressed Blocked

Named agents

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

Agenti-spo.ru rigidindustries.com
GPTBot OpenAI Not explicitly addressed Blocked
ClaudeBot Anthropic Not explicitly addressed Blocked
CCBot Common Crawl Not explicitly addressed Blocked
Bytespider ByteDance Not explicitly addressed Blocked
meta-externalagent Meta Not explicitly addressed Blocked
cohere-ai Cohere Not explicitly addressed Blocked
Diffbot Diffbot Not explicitly addressed Blocked
OAI-SearchBot OpenAI Not explicitly addressed Blocked
PerplexityBot Perplexity Not explicitly addressed Blocked
YouBot You.com Not explicitly addressed Blocked
PetalBot Huawei Not explicitly addressed Blocked
ChatGPT-User OpenAI Not explicitly addressed Blocked
4 additional tracked agents
Agenti-spo.ru rigidindustries.com
Amazonbot Not explicitly addressedBlocked
Google-Extended Not explicitly addressedBlocked
Applebot-Extended Not explicitly addressedBlocked
anthropic-ai Not explicitly addressedBlocked

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.

Traiti-spo.ru rigidindustries.com
Wildcard group Yes 89.6% Ranks 100,001–1,000,000 · n=680,000 Yes 89.6% Ranks 100,001–1,000,000 · n=680,000
Effectively open file No 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 No 60.6% Ranks 100,001–1,000,000 · n=680,000 No 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 Yes 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.