Agent Web Index › brainscape.com
Can AI assistants read brainscape.com?
Measured on 2026-09-19 by asking the site 7 times — once as a browser, once as each of the 6 crawlers that feed ChatGPT, Claude, Perplexity, Gemini, Meta AI, Apple Intelligence and Doubao — and comparing what came back. The AI-training opt-out tokens that never crawl are read from robots.txt instead.
B76 / 100
1 of 6 crawlers can read this page.
More readable than 55% of the 47,934 sites measured so far.
Structured data: Organization, FAQPage.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|---|---|---|
| ClaudeBot (Claude) | 200 | allowed by the server, blocked in robots.txt | blocked |
| GPTBot (ChatGPT) | 200 | allowed by the server, blocked in robots.txt | blocked |
| OAI-SearchBot (ChatGPT Search) | 200 | can read it | allowed |
| PerplexityBot (Perplexity) | 200 | allowed by the server, blocked in robots.txt | blocked |
| Google-Extended (Gemini, AI Overviews) a robots.txt token, not a crawler: it controls how already-crawled pages may be used, and never makes a request of its own | — | not opted out | allowed |
| Meta-ExternalAgent (Meta AI) | 200 | allowed by the server, blocked in robots.txt | blocked |
| Amazonbot (Alexa, Rufus) | 200 | allowed by the server, blocked in robots.txt | blocked-by-star |
What to change, in order
- 1 AI crawler is shut out by the catch-all rule, not by a rule naming it+1 crawlerrobots.txt has no group for Amazonbot; it falls under
User-agent: *withDisallow: /. If the intent was to stop generic scrapers, the assistants are collateral: add one explicit group per crawler withAllow: /. The server already serves 1 of them, so the robots.txt line is the only thing standing in the way. - Publish llms.txtllms.txt is missing, so an assistant has to discover the site by following links. llms.txt is the emerging convention for telling an assistant which pages actually matter.
- 4 crawlers are named and refused in robots.txt — a deliberate choiceClaudeBot, GPTBot, PerplexityBot, Meta-ExternalAgent are blocked by a rule that names them. Nothing to fix here: this page records what is true, not what should be. It is listed so the deliberate part of the block is not confused with the accidental part above.
Get told if this changes
One email only when a measured crawler flips on brainscape.com, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people100%
- Readable without JavaScript100%
- robots.txt lets the crawlers in29%
- Facts in JSON-LD84%
- Content reachable, not buried60%
- Publishes a map of itself45%
- Plain structure80%
Sites with a similar score
Embed this score
Put the badge on brainscape.com — it links back here, and re-measures every time this index re-crawls.
<a href="https://aivis.lumnika.com/ai-readiness/brainscape.com"><img src="https://aivis.lumnika.com/ai-readiness/brainscape.com/badge.svg" alt="AI readability"></a>
Method. 7 live HTTP requests (one per crawler, one as a browser) plus robots.txt, llms.txt, sitemap.xml and security.txt, 12-second timeout each,
from a single vantage point. Blocking AI crawlers is a legitimate choice, not a failure: this page records what is true, not what should be.
Domain comes from a shop-platform seed (Shopify/WooCommerce/Magento/BigCommerce/Shopline fingerprint or JSON-LD price), not the Tranco traffic ranking. One page per domain — the homepage — is audited.
Part of the Agent Web Index, 47,934 domains measured, updated continuously.
Part of the Agent Web Index, 47,934 domains measured, updated continuously.