Agent Web Index › quest.nl
Can AI assistants read quest.nl?
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.
C73 / 100
1 of 6 crawlers can read this page.
More readable than 47% of the 47,315 sites measured so far.
Structured data: ItemList, WebPage.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|---|---|---|
| ClaudeBot (Claude) | 403 | challenged | allowed-by-star |
| GPTBot (ChatGPT) | 403 | challenged | blocked |
| OAI-SearchBot (ChatGPT Search) | 200 | allowed by the server, blocked in robots.txt | blocked |
| PerplexityBot (Perplexity) | 200 | can read it | allowed-by-star |
| 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-by-star |
| Meta-ExternalAgent (Meta AI) | 403 | challenged | allowed-by-star |
| Amazonbot (Alexa, Rufus) | 403 | challenged | allowed-by-star |
What to change, in order
- Let in the 3 crawlers your own robots.txt already allows+3 crawlersClaudeBot, Meta-ExternalAgent, Amazonbot are turned away before reading the page (served a bot challenge instead of the page), while robots.txt permits them — so this block is not written in your site. No CDN signature was found in the response headers, so the refusal comes from the origin server itself or from a WAF this index does not recognise. Fixing it takes this domain from 1 to 4 of 6 crawlers.
- 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.
- 2 crawlers are named and refused in robots.txt — a deliberate choiceGPTBot, OAI-SearchBot 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.
The checks
- Answers AI agents like it answers people43%
- Readable without JavaScript100%
- robots.txt lets the crawlers in71%
- Facts in JSON-LD84%
- Content reachable, not buried82%
- Publishes a map of itself70%
- Plain structure70%
Sites with a similar score
Embed this score
Put the badge on quest.nl — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/quest.nl"><img src="https://shop.lumnika.com/ai-readiness/quest.nl/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,315 domains measured, updated continuously.
Part of the Agent Web Index, 47,315 domains measured, updated continuously.