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

letao.com.tw and xn----otbdcdguhdkawh.xn--p1ai

letao.com.tw #80,894 xn----otbdcdguhdkawh.xn--p1ai #80,892

Measured takeaway

letao.com.tw allows model-training crawlers; xn----otbdcdguhdkawh.xn--p1ai blocks model-training crawlers.

letao.com.tw allows GPTBot; xn----otbdcdguhdkawh.xn--p1ai blocks GPTBot.

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.

Evidenceletao.com.tw xn----otbdcdguhdkawh.xn--p1ai
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 purposeletao.com.tw xn----otbdcdguhdkawh.xn--p1ai
Model training Allowed Blocked
AI search Allowed Not explicitly addressed
Live assistant fetch Allowed Not explicitly addressed
Opt-out directives Not explicitly addressed Not explicitly addressed
Ambiguous / undocumented Allowed 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.

Agentletao.com.tw xn----otbdcdguhdkawh.xn--p1ai
GPTBot OpenAI Allowed Blocked
ClaudeBot Anthropic Allowed Not explicitly addressed
CCBot Common Crawl Allowed Not explicitly addressed
Bytespider ByteDance Allowed Not explicitly addressed
OAI-SearchBot OpenAI Allowed Not explicitly addressed
PerplexityBot Perplexity Allowed Not explicitly addressed
Amazonbot Amazon Allowed Not explicitly addressed
anthropic-ai Anthropic Allowed 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.

Traitletao.com.tw xn----otbdcdguhdkawh.xn--p1ai
Wildcard group Yes 92.1% Ranks 10,001–100,000 · n=54,147 No 92.1% Ranks 10,001–100,000 · n=54,147
Effectively open file Yes 22.6% Ranks 10,001–100,000 · n=54,147 No 22.6% Ranks 10,001–100,000 · n=54,147
Sitemap declared No 61.7% Ranks 10,001–100,000 · n=54,147 No 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.