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

clevertap-prod.com and umeng.com

clevertap-prod.com #2,074 umeng.com #2,073

Measured takeaway

clevertap-prod.com's robots.txt disallows every crawler; umeng.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.

Evidenceclevertap-prod.com umeng.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 Allowed the wildcard (*) group is effectively open
Base /llms.txt Served; parsing unavailable 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 purposeclevertap-prod.com umeng.com
Model training Not explicitly addressed Allowed
AI search Not explicitly addressed Allowed
Live assistant fetch Not explicitly addressed Allowed
Opt-out directives Not explicitly addressed Allowed
Ambiguous / undocumented Not explicitly addressed Allowed

Named agents

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

Agentclevertap-prod.com umeng.com
GPTBot OpenAI Not explicitly addressed Allowed
ClaudeBot Anthropic Not explicitly addressed Allowed
Bytespider ByteDance Not explicitly addressed Allowed
OAI-SearchBot OpenAI Not explicitly addressed Allowed
Applebot Apple Not explicitly addressed Allowed
PerplexityBot Perplexity Not explicitly addressed Allowed
ChatGPT-User OpenAI Not explicitly addressed Allowed
Google-Extended Google Not explicitly addressed Allowed
anthropic-ai Anthropic Not explicitly addressed Allowed

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.

Traitclevertap-prod.com umeng.com
Wildcard group Yes 94.1% Ranks 1,001–10,000 · n=5,437 Yes 94.1% Ranks 1,001–10,000 · n=5,437
Effectively open file No 16.4% Ranks 1,001–10,000 · n=5,437 Yes 16.4% Ranks 1,001–10,000 · n=5,437
Sitemap declared No 65.6% Ranks 1,001–10,000 · n=5,437 Yes 65.6% Ranks 1,001–10,000 · n=5,437
robots.txt served Yes 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 No 0.2% Ranks 1,001–10,000 · n=5,437 No 0.2% Ranks 1,001–10,000 · n=5,437
Blanket disallow Yes 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.