Agent Web Index › kazar.com

Can AI assistants read kazar.com?

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.

C67 / 100
4 of 8 crawlers can read this page.
More readable than 29% of the 47,315 sites measured so far. Structured data: Store, Organization.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged allowed
GPTBot (ChatGPT)403 challenged allowed
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)200 can read it allowed
Amazonbot (Alexa, Rufus)403 challenged blocked
Bytespider (Doubao, Lark)403 challenged blocked
Applebot (Siri, Apple Intelligence)200 can read it 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
opted out in robots.txt blocked

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 2 crawlers your own robots.txt already allows+2 crawlers
    ClaudeBot, GPTBot 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. 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 6 of 8 crawlers.
  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. Mark the content with <main>
    The content-reachability check scores 26/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.
  4. 2 crawlers are named and refused in robots.txt — a deliberate choice
    Amazonbot, Bytespider 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 kazar.com →

Sites with a similar score

igoo.myshopify.comC 68kay.comC 67kcbgroup.comC 67kahoku.newsC 67kentonline.co.ukC 67jknmedia.myshopify.comC 67labirint.ruC 67henk.myshopify.comC 67mindreef.myshopify.comC 67cgshop.myshopify.comC 67slobodna-bosna.baC 67goldandgifts.myshopify.comC 66

Other magento stores

gymbeam.roB 84trafag.comB 80nkd.comB 75kasanova.comC 70omegawatches.comC 64eram.frD 46

Browse the whole index →

Embed this score

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

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