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

123stitch.com and tabirai.net

123stitch.com #51,770 tabirai.net #51,772

Measured takeaway

123stitch.com blocks AI-search crawlers; tabirai.net has mixed rules for AI-search 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.

Evidence123stitch.com tabirai.net
robots.txt Served and parsed Served and parsed
Google crawl posture Open Open
Unnamed crawler fallback Partly Restricted they inherit the wildcard (*) group's rules Partly Restricted they inherit the wildcard (*) group's rules
Base /llms.txt Not probed Not found when 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 purpose123stitch.com tabirai.net
Model training Blocked Blocked
AI search Blocked Mixed
Live assistant fetch Blocked Allowed
Opt-out directives Not explicitly addressed Not explicitly addressed
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.

Agent123stitch.com tabirai.net
Amazonbot Amazon Blocked Allowed
CCBot Common Crawl Blocked Blocked
Petalbot Huawei Blocked Blocked
Bytespider ByteDance Blocked Not explicitly addressed
FacebookBot Meta Blocked Not explicitly addressed
Diffbot Diffbot Blocked Not explicitly addressed
omgili Webz.io Blocked Not explicitly addressed
Applebot Apple Not explicitly addressed Allowed
Scrapy Scrapy Not explicitly addressed 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.

Trait123stitch.com tabirai.net
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 No 22.6% Ranks 10,001–100,000 · n=54,147 No 22.6% Ranks 10,001–100,000 · n=54,147
Sitemap declared Yes 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.