Agent Web Index › lucky-bike.de
Can AI assistants read lucky-bike.de?
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.
B75 / 100
5 of 6 crawlers can read this page.
More readable than 52% of the 47,249 sites measured so far.
Structured data: BreadcrumbList.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|---|---|---|
| ClaudeBot (Claude) | 200 | can read it | allowed-by-star |
| GPTBot (ChatGPT) | 200 | can read it | allowed-by-star |
| OAI-SearchBot (ChatGPT Search) | 200 | can read it | allowed-by-star |
| 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) | 200 | can read it | allowed-by-star |
BunnyCDN answers for this domain. Where a crawler above is refused while robots.txt allows it, the rule is applied by that edge, not written by the site — see how often each edge does this.
What to change, in order
- Let in the 1 crawler your own robots.txt already allows+1 crawlerMeta-ExternalAgent is turned away before reading the page (served a bot challenge instead of the page), while robots.txt permits it — so this block is not written in your site. BunnyCDN answers for this domain. Look for the bot or user-agent rules in its dashboard: that is where the decision is made, not in robots.txt. Fixing it takes this domain from 5 to 6 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.
- Mark the content with <main>The content-reachability check scores 0/100: with no <main> or <article> landmark, or with most of the page outside it, an assistant reads the navigation and the footer at the same cost as the text it came for.
Get told if this changes
One email only when a measured crawler flips on lucky-bike.de, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people86%
- Readable without JavaScript100%
- robots.txt lets the crawlers in100%
- Facts in JSON-LD67%
- Content reachable, not buried0%
- Publishes a map of itself45%
- Plain structure85%
Sites with a similar score
Embed this score
Put the badge on lucky-bike.de — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/lucky-bike.de"><img src="https://shop.lumnika.com/ai-readiness/lucky-bike.de/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,249 domains measured, updated continuously.
Part of the Agent Web Index, 47,249 domains measured, updated continuously.