Two public profiles · no score or winner
anthropic.com and threads.com
Measured takeaway
threads.com's robots.txt disallows every crawler; anthropic.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.
| Evidence | anthropic.com | threads.com |
|---|---|---|
| robots.txt | Served and parsed | Served and parsed |
| Google crawl posture | Open | Blocked |
| Unnamed crawler fallback | Allowed the wildcard (*) group is effectively open | Blocked the wildcard (*) group disallows everything, so they are blocked without being named |
| Base /llms.txt | Not found when probed | Related file observed at /ai.txt; /llms.txt not established |
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 purpose | anthropic.com | threads.com |
|---|---|---|
| Model training | Not explicitly addressed | Blocked |
| AI search | Not explicitly addressed | Mixed |
| Live assistant fetch | Not explicitly addressed | Blocked |
| Opt-out directives | Not explicitly addressed | Blocked |
| 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.
| Agent | anthropic.com | threads.com |
|---|---|---|
| GPTBot OpenAI | Not explicitly addressed | Blocked |
| ClaudeBot Anthropic | Not explicitly addressed | Blocked |
| Applebot Apple | Not explicitly addressed | Partly blocked |
| PerplexityBot Perplexity | Not explicitly addressed | Blocked |
| PetalBot Huawei | Not explicitly addressed | Blocked |
| Amazonbot Amazon | Not explicitly addressed | Blocked |
| Google-Extended Google | Not explicitly addressed | Blocked |
| Applebot-Extended Apple | Not explicitly addressed | Blocked |
| 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.
| Trait | anthropic.com | threads.com |
|---|---|---|
| Wildcard group | Yes 95.1% Ranks 1–1,000 · n=529 | Yes 95.1% Ranks 1–1,000 · n=529 |
| Effectively open file | Yes 11.3% Ranks 1–1,000 · n=529 | No 11.3% Ranks 1–1,000 · n=529 |
| Sitemap declared | Yes 66.0% Ranks 1–1,000 · n=529 | Yes 66.0% Ranks 1–1,000 · n=529 |
| robots.txt served | Yes 53.3% Ranks 1–1,000 · n=1,000 | Yes 53.3% Ranks 1–1,000 · n=1,000 |
| robots.txt returned 404 | No 4.6% Ranks 1–1,000 · n=1,000 | No 4.6% Ranks 1–1,000 · n=1,000 |
| Over the RFC parse limit | No 0.8% Ranks 1–1,000 · n=529 | No 0.8% Ranks 1–1,000 · n=529 |
| Blanket disallow | No 8.9% Ranks 1–1,000 · n=529 | Yes 8.9% Ranks 1–1,000 · n=529 |
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 →