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

ap.org and ntp-fireos.com

ap.org #4,727 ntp-fireos.com #4,726

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.

Evidenceap.org ntp-fireos.com
robots.txt Served and parsed Fetch failed: dns_error
Google crawl posture Open Blocked
Unnamed crawler fallback Partly Restricted they inherit the wildcard (*) group's rules Unavailable
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 purposeap.org ntp-fireos.com
Model training Allowed Observation unavailable
AI search Allowed Observation unavailable
Live assistant fetch Allowed Observation unavailable
Opt-out directives Allowed Observation unavailable
Ambiguous / undocumented Not explicitly addressed Observation unavailable

Named agents

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

Agentap.org ntp-fireos.com
GPTBot OpenAI Allowed Observation unavailable
ClaudeBot Anthropic Allowed Observation unavailable
OAI-SearchBot OpenAI Allowed Observation unavailable
Applebot Apple Allowed Observation unavailable
PerplexityBot Perplexity Allowed Observation unavailable
ChatGPT-User OpenAI Allowed Observation unavailable
Amazonbot Amazon Allowed Observation unavailable
Google-Extended Google Allowed Observation unavailable

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.

Traitap.org ntp-fireos.com
Wildcard group Yes 94.1% Ranks 1,001–10,000 · n=5,437 Parsing unavailable 94.1% Ranks 1,001–10,000 · n=5,437
Effectively open file No 16.4% Ranks 1,001–10,000 · n=5,437 Parsing unavailable 16.4% Ranks 1,001–10,000 · n=5,437
Sitemap declared Yes 65.6% Ranks 1,001–10,000 · n=5,437 Parsing unavailable 65.6% Ranks 1,001–10,000 · n=5,437
robots.txt served Yes 60.7% Ranks 1,001–10,000 · n=9,037 Fetch failed: dns_error 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 Fetch failed: dns_error 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 Parsing unavailable 0.2% Ranks 1,001–10,000 · n=5,437
Blanket disallow No 3.7% Ranks 1,001–10,000 · n=5,437 Parsing unavailable 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.