Checked 9/23/2026 · https://www.eureko.sk/
The technical prerequisites for AI discoverability are met.
AI crawler matrix
For each bot: what your robots.txt allows — and what your server actually returns to the bot's user agent. Rows highlighted in red: robots allows it, but the server blocks it (usually a WAF or bot-protection rule).
| Bot | Operator | robots.txt | Server response |
|---|---|---|---|
| GPTBot | OpenAI | allowed | 200 + content |
| OAI-SearchBot | OpenAI | allowed | 200 + content |
| ChatGPT-User | OpenAI | allowed | 200 + content |
| ClaudeBot | Anthropic | allowed | 200 + content |
| Claude-SearchBot | Anthropic | allowed | 200 + content |
| Claude-User | Anthropic | allowed (via User-agent: *) | 200 + content |
| PerplexityBot | Perplexity | allowed | 200 + content |
| Perplexity-User | Perplexity | allowed (via User-agent: *) | 200 + content |
| Google-Extended | Google (Gemini-Training) | allowed | — |
| Googlebot | Google (KI-Übersichten) | allowed | 200 + content |
| CCBot | Common Crawl (Trainingsdaten vieler LLMs) | allowed | 200 + content |
| Bytespider | ByteDance (Doubao) | allowed | 200 + content |
| Amazonbot | Amazon (Alexa/Rufus) | allowed | 200 + content |
| Applebot-Extended | Apple (Intelligence-Training) | allowed (via User-agent: *) | — |
| Meta-ExternalAgent | Meta (Llama/Meta AI) | allowed | 200 + content |
How is the score calculated?
| No llms.txt | -5 |
| No author or authorship signal | -4 |
| Elevated server response time | -4 |
| Heading levels are skipped | -3 |
| No visible or marked-up date | -3 |
| No canonical URL | -3 |
| No FAQ or HowTo markup | -2 |
| Result | 76 / 100 |
Structure & machine understanding
No llms.txt
There is no file at /llms.txt. llms.txt is a short Markdown overview of your key content that some AI systems use for orientation.
This is what you should do: Create an /llms.txt: an H1 with the name, a short paragraph about the offering, and a link list to the central pages.
# Your company > One-sentence description. ## Key pages - [Product](https://your-domain.com/product): … - [Pricing](https://your-domain.com/pricing): … - [About](https://your-domain.com/about): …
Heading levels are skipped
The heading sequence skips at least one level (e.g. H2 straight to H4). This makes it harder to reconstruct the content structure automatically.
This is what you should do: Use the heading levels without gaps and in order (H1 → H2 → H3 …).
No FAQ or HowTo markup
Question-and-answer and step-by-step content is harder for AI systems to recognise as directly citable answers without FAQPage or HowTo markup.
This is what you should do: Where the page answers real questions or gives instructions, mark it up as FAQPage or HowTo (no markup without visibly matching content).
Trust and entity signals (E-E-A-T)
No author or authorship signal
No author is recognisable (neither meta tag, rel=author nor JSON-LD Person). For "experience" and "expertise" in the E-E-A-T sense, named, traceable authorship matters.
This is what you should do: For editorial content, name an author and link an author page; also mark them up as JSON-LD "Person".
No visible or marked-up date
No publication or modification date is recognisable (neither <time>, article:published_time nor datePublished in the JSON-LD). For many questions, AI systems prefer current sources.
This is what you should do: For content with a time reference, show a date visibly and mark up datePublished / dateModified in the JSON-LD.
Technical foundation
Elevated server response time
The time to first byte was around 1884 ms — noticeable, but not yet critical.
This is what you should do: Watch the response time and check caching or a CDN if it keeps rising.
No canonical URL
The page sets no <link rel="canonical">. Without a canonical, it can stay unclear which version is authoritative when several URL variants exist.
This is what you should do: Set a self-referencing <link rel="canonical"> with the preferred URL on every page.
OK (7)
- The main content is in the HTML without JavaScript.
- Structured data (JSON-LD) is present. — WebSite, Organization, LocalBusiness
- The organisation is marked up as JSON-LD.
- Exactly one H1 heading.
- The sitemap is reachable.
- The page title has a sensible length.
- No noindex — the page may be indexed.
Next steps
- No llms.txt. Create an /llms.txt: an H1 with the name, a short paragraph about the offering, and a link list to the central pages.
- No author or authorship signal. For editorial content, name an author and link an author page; also mark them up as JSON-LD "Person".
- Elevated server response time. Watch the response time and check caching or a CDN if it keeps rising.
Weekly re-scan with an email alert on every change. In preparation — add your address.
Method & limits
Checked 9/23/2026. citeglass fetches eureko.sk and its related files (robots.txt, llms.txt, sitemap.xml) over HTTP — once as a normal browser, once per AI crawler user agent. No JavaScript is executed. Time to first byte: 1884 ms.
What this is not: No rank or citation tracking, no statement about whether a model actually names you, and no check of content loaded via JavaScript. A snapshot from the perspective of one server IP.