Agent Web Index › bolshoyvopros.ru

Can AI assistants read bolshoyvopros.ru?

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.

D57 / 100
1 of 6 crawlers can read this page.
More readable than 11% of the 47,315 sites measured so far. No JSON-LD.

What each crawler got back

CrawlerHTTPResultrobots.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-by-star
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
— opted out in robots.txt blocked
Meta-ExternalAgent (Meta AI)200 allowed by the server, blocked in robots.txt blocked
Amazonbot (Alexa, Rufus)403 challenged blocked

What to change, in order

  1. Declare the facts in JSON-LD
    There is no JSON-LD on the page, so every fact — who you are, what you sell, the price — has to be guessed out of the prose and the layout. A schema.org block is the difference between being quoted correctly and being paraphrased.
  2. Publish llms.txt
    llms.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.
  3. Fix the plain structure: one <h1>, a title, a description, alt text
    The structure check scores 55/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.
  4. 5 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot, PerplexityBot, Meta-ExternalAgent, Amazonbot 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

Re-run this audit live → Full AI-visibility report for bolshoyvopros.ru →

Sites with a similar score

bolgroup.myshopify.comD 57bombonel.myshopify.comD 57bodynet.myshopify.comD 57bonnet.myshopify.comD 57bluesparrow.myshopify.comD 57bope.myshopify.comD 57bensshoes.myshopify.comD 57buttons-up.myshopify.comD 57angga.myshopify.comD 57consultant.myshopify.comD 57ilbazaar.myshopify.comD 57crackleback.myshopify.comD 56

Browse the whole index →

Embed this score

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

bolshoyvopros.ru AI readability: D 57/100 
<a href="https://shop.lumnika.com/ai-readiness/bolshoyvopros.ru"><img src="https://shop.lumnika.com/ai-readiness/bolshoyvopros.ru/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.