Comparisons with published methodology Every claim dated & sourced

Research · original data · not a review

How AI companies treat each other's crawlers

Scanned 2026-10-30 · re-checked weekly · machine-readable data

Every AI company asks the open web for machine access. This page records, per crawler identity, what each major AI vendor's own website says in robots.txt and what its server does when that crawler requests the homepage, including the vendors' own crawlers and their competitors'. The full dataset, regenerated by a script with no manual edits, lives at /crawler-matrix.json.

Reading the table

First token: robots.txt verdict for that bot (— means no rule names it). Second token: live HTTP status returned to that bot's exact user-agent. "challenge" is a Cloudflare managed-challenge response (CF-Mitigated: challenge). The two can disagree: a site can permit a bot in policy and refuse it at the network layer, or stay silent in robots.txt while blocking in practice.

AI-vendor crawler matrix · scanned 2026-10-30 · 64 cells
Vendor site GPTBotOAI-SearchBotChatGPT-UserClaudeBotClaude-SearchBotGoogle-ExtendedPerplexityBotCCBot
openai.com — / 403 (challenge) — / 403 (challenge) — / 403 (challenge) — / 403 (challenge) — / 403 (challenge) — / 403 (challenge) — / 403 (challenge) — / 403 (challenge)
anthropic.com — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓
google.com — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓
perplexity.ai — / 403 (cf-403) — / 403 (challenge) — / 200 ✓ — / 403 (cf-403) — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 403 (challenge)
mistral.ai — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓
cohere.com — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓ — / 200 ✓
meta.ai — / 403 — / 403 — / 403 — / 403 — / 403 — / 403 — / 403 — / 403
x.ai — / 200 ✓ — / 200 ✓ — / 403 (cf-403) — / 403 (cf-403) — / 403 (cf-403) — / 403 (cf-403) — / 403 (cf-403) — / 200 ✓

Observations from this scan

Method

  1. robots: fetch /robots.txt as ourselves, parse the User-agent group naming the bot; block-all = Disallow: / in that group, restricted = other rules, no-rule = no group names the bot
  2. http: fetch / with the bot's exact user-agent; record status plus Cloudflare challenge markers (CF-Mitigated: challenge)

Vantage: TestedActually build machine, datacenter IP, 2026-10-30. Crawler behaviour can vary by IP reputation and path; we publish the vantage so results can be independently reproduced. Limitations: homepage only, eight vendors, eight crawler identities, one vantage point, no authentication-bearing fetchers. Week-over-week diffs are kept in the public repository history.

Reproduce

The scanner is a single script: node scripts/vendor-crawler-matrix.mjs in the site's repository. It rewrites /crawler-matrix.json from live requests; no manual edits.