Agent Web Index › praktiker.bg

Can AI assistants read praktiker.bg?

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.

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

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)200 can read it allowed
GPTBot (ChatGPT)200 can read it allowed
OAI-SearchBot (ChatGPT Search)200 allowed by the server, blocked in robots.txt blocked-by-star
PerplexityBot (Perplexity)200 can read it allowed
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)403 challenged allowed
Amazonbot (Alexa, Rufus)200 can read it allowed

Cloudflare 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

  1. Let in the 1 crawler your own robots.txt already allows+1 crawler
    Meta-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. Cloudflare answers for this domain. Cloudflare applies AI-crawler blocking at the edge, independently of robots.txt (Security → Bots, plus the managed robots.txt feature). https://developers.cloudflare.com/bots/concepts/bot/ Fixing it takes this domain from 4 to 5 of 6 crawlers.
  2. 1 AI crawler is shut out by the catch-all rule, not by a rule naming it+1 crawler
    robots.txt has no group for OAI-SearchBot; it falls under User-agent: * with Disallow: /. If the intent was to stop generic scrapers, the assistants are collateral: add one explicit group per crawler with Allow: /. The server already serves 1 of them, so the robots.txt line is the only thing standing in the way.
  3. 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.
  4. 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.

The checks

Re-run this audit live → Full AI-visibility report for praktiker.bg →

Sites with a similar score

matrixgames.comC 73practicefusion.comC 72princehotels.co.jpC 72pos4dtototogel86.comC 72profitmetrics.ioC 72pik-potsdam.deC 72qazsporttv.kzC 72numpy.orgC 72saitama-np.co.jpC 72islandnet.comC 72utmb.eduC 72rebel.myshopify.comC 71

Browse the whole index →

Embed this score

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

praktiker.bg AI readability: C 72/100
<a href="https://shop.lumnika.com/ai-readiness/praktiker.bg"><img src="https://shop.lumnika.com/ai-readiness/praktiker.bg/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.