Can AI assistants read bluemoon-mcfc.co.uk?
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.
F28 / 100
0 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
| Crawler | HTTP | Result | robots.txt |
|---|
| ClaudeBot (Claude) | 403 |
challenged |
allowed-by-star |
| GPTBot (ChatGPT) | 403 |
challenged |
allowed-by-star |
| OAI-SearchBot (ChatGPT Search) | 403 |
challenged |
allowed-by-star |
| PerplexityBot (Perplexity) | 403 |
challenged |
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) | 403 |
challenged |
allowed-by-star |
| Amazonbot (Alexa, Rufus) | 403 |
challenged |
allowed-by-star |
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
- Let in the 6 crawlers your own robots.txt already allows+6 crawlers
ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, 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. 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 0 to 6 of 6 crawlers.
- 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.
- 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 40/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.
The checks
- Answers AI agents like it answers people0%
- Readable without JavaScript0%
- robots.txt lets the crawlers in100%
- Facts in JSON-LD0%
- Content reachable, not buried60%
- Publishes a map of itself45%
- Plain structure40%
Re-run this audit live →
Full AI-visibility report for bluemoon-mcfc.co.uk →
Browse the whole index →
Embed this score
Put the badge on bluemoon-mcfc.co.uk — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/bluemoon-mcfc.co.uk"><img src="https://shop.lumnika.com/ai-readiness/bluemoon-mcfc.co.uk/badge.svg" alt="AI readability"></a>