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

brazil-family.com and projectwedding.com

brazil-family.com #396,158 projectwedding.com #396,157

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.

Evidencebrazil-family.com projectwedding.com
robots.txt Served and parsed Returned HTTP 301
Google crawl posture Open Open
Unnamed crawler fallback Allowed the wildcard (*) group is effectively open Unavailable
Base /llms.txt Published 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 purposebrazil-family.com projectwedding.com
Model training Mixed 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.

Agentbrazil-family.com projectwedding.com
GPTBot OpenAI Allowed Observation unavailable
ClaudeBot Anthropic Allowed Observation unavailable
CCBot Common Crawl Blocked Observation unavailable
OAI-SearchBot OpenAI Allowed Observation unavailable
PerplexityBot Perplexity Allowed Observation unavailable
ChatGPT-User OpenAI Allowed Observation unavailable
Claude-Web Anthropic 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.

Traitbrazil-family.com projectwedding.com
Wildcard group Yes 89.6% Ranks 100,001–1,000,000 · n=680,000 Parsing unavailable 89.6% Ranks 100,001–1,000,000 · n=680,000
Effectively open file Yes 26.0% Ranks 100,001–1,000,000 · n=680,000 Parsing unavailable 26.0% Ranks 100,001–1,000,000 · n=680,000
Sitemap declared Yes 60.6% Ranks 100,001–1,000,000 · n=680,000 Parsing unavailable 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 No 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 Parsing unavailable 0.3% Ranks 100,001–1,000,000 · n=680,000
Blanket disallow No 10.8% Ranks 100,001–1,000,000 · n=680,000 Parsing unavailable 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.