Agent Web Index › sportokay.com

Can AI assistants read sportokay.com?

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.

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

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged 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 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
— 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 allowed-by-star

What to change, in order

  1. Let in the 1 crawler your own robots.txt already allows+1 crawler
    Amazonbot 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. 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 2 to 3 of 6 crawlers.
  2. 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.
  3. 3 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot, Meta-ExternalAgent 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 sportokay.com →

Sites with a similar score

cleverlife.com.auC 64kpfu.ruC 62spintheblog.comD 61stlouisfed.orgD 61sonarr.tvD 61suzone.inD 61sarthaks.comD 61thekatyblog.comD 61nizarblog.comD 61waitbutwhy.comD 61blogsidea.comD 61richmond.eduD 58

Other magento stores

gymbeam.roB 84trafag.comB 80nkd.comB 75kasanova.comC 70bexley.frC 65eram.frD 46

Browse the whole index →

Embed this score

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

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