Agent Web Index › btc.bw

Can AI assistants read btc.bw?

Measured on 2026-09-19 by asking the site 9 times — once as a browser, once as each of the 8 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.

D58 / 100
0 of 8 crawlers can read this page.
More readable than 18% of the 47,315 sites measured so far. Structured data: WebPage, BreadcrumbList, WebSite, Organization.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)— no-answer allowed-by-star
GPTBot (ChatGPT)— no-answer allowed-by-star
OAI-SearchBot (ChatGPT Search)— no-answer allowed-by-star
PerplexityBot (Perplexity)— no-answer 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)— no-answer allowed-by-star
Amazonbot (Alexa, Rufus)— no-answer allowed-by-star
Bytespider (Doubao, Lark)— no-answer allowed-by-star
Applebot (Siri, Apple Intelligence)— no-answer allowed-by-star
Applebot-Extended (Apple Intelligence training)
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

What to change, in order

  1. Let in the 8 crawlers your own robots.txt already allows+8 crawlers
    ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, Meta-ExternalAgent, Amazonbot, Bytespider, Applebot are turned away before reading the page (the connection never completed), 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 0 to 8 of 8 crawlers.
  2. Publish sitemap.xml and llms.txt
    sitemap.xml and llms.txt are 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.
  3. Fix the plain structure: one <h1>, a title, a description, alt text
    The structure check scores 40/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.

The checks

Re-run this audit live → Full AI-visibility report for btc.bw →

Sites with a similar score

gov.on.caD 61abebooks.frD 59brushandkeyartistry.comD 58bundesjustizamt.deD 58brightree.netD 58camstreams.tvD 58bangumi.tvD 58coreboot.orgD 58houseofblouse.comD 58yufak.myshopify.comD 57vielevitamine.myshopify.comD 57responsecrew.myshopify.comD 57

Other woocommerce stores

drivestrike.comA+ 93logix.inA 90hosterion.comA 86arcticwolf.comB 79zentrixads.comC 71littlevectordesigns.comF 29

Browse the whole index →

Embed this score

Put the badge on btc.bw — it links back here, and re-measures every time this index re-crawls.

btc.bw AI readability: D 58/100 
<a href="https://shop.lumnika.com/ai-readiness/btc.bw"><img src="https://shop.lumnika.com/ai-readiness/btc.bw/badge.svg" alt="AI readability"></a>
Method. 9 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.