Can AI assistants read ktul.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.
D60 / 100
1 of 6 crawlers can read this page.
More readable than 19% of the 47,623 sites measured so far.
No JSON-LD.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|
| ClaudeBot (Claude) | 200 |
allowed by the server, blocked in robots.txt |
blocked |
| GPTBot (ChatGPT) | 200 |
allowed by the server, blocked in robots.txt |
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 |
allowed-by-star |
| Amazonbot (Alexa, Rufus) | 403 |
challenged |
allowed-by-star |
AWS CloudFront 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
- Let in the 3 crawlers your own robots.txt already allows+3 crawlers
OAI-SearchBot, Meta-ExternalAgent, Amazonbot 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. AWS CloudFront answers for this domain. AWS WAF Bot Control has an AI-crawler category that CloudFront enforces ahead of your origin. https://docs.aws.amazon.com/waf/latest/developerguide/waf-bot-control.html Fixing it takes this domain from 1 to 4 of 6 crawlers.
- 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.
- 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.
- Fix the plain structure: one <h1>, a title, a description, alt text
The structure check scores 57/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.
- 2 crawlers are named and refused in robots.txt — a deliberate choice
ClaudeBot, GPTBot 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.
Get told if this changes
One email only when a measured crawler flips on ktul.com, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people57%
- Readable without JavaScript100%
- robots.txt lets the crawlers in57%
- Facts in JSON-LD0%
- Content reachable, not buried97%
- Publishes a map of itself45%
- Plain structure57%
Re-run this audit live →
Full AI-visibility report for ktul.com →
Sites with a similar score
Browse the whole index →
Embed this score
Put the badge on ktul.com — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/ktul.com"><img src="https://shop.lumnika.com/ai-readiness/ktul.com/badge.svg" alt="AI readability"></a>