Agent Web Index › imeteo.sk

Can AI assistants read imeteo.sk?

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.

F20 / 100
1 of 6 crawlers can read this page.
More readable than 0% of the 47,315 sites measured so far. The text is drawn by JavaScript, which most crawlers never run. No JSON-LD.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged blocked
GPTBot (ChatGPT)403 challenged blocked
OAI-SearchBot (ChatGPT Search)403 challenged 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)403 challenged blocked
Amazonbot (Alexa, Rufus)403 challenged 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 1 crawler your own robots.txt already allows+1 crawler
    OAI-SearchBot 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 1 to 2 of 6 crawlers.
  2. Put the text in the HTML, not only in JavaScript
    The HTML that arrives is nearly empty and the content is painted by JavaScript. None of these crawlers run it, so even the ones that are served read a blank page. Server-rendering or prerendering the main content is what changes their result.
  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.
  5. 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.
  6. 4 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot, 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 imeteo.sk →

Browse the whole index →

Embed this score

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

imeteo.sk AI readability: F 20/100
<a href="https://shop.lumnika.com/ai-readiness/imeteo.sk"><img src="https://shop.lumnika.com/ai-readiness/imeteo.sk/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.