Can AI assistants read getsurrey.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.
F21 / 100
0 of 6 crawlers can read this page.
More readable than 0% of the 47,821 sites measured so far.
No JSON-LD.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|
| ClaudeBot (Claude) | 402 |
error |
blocked |
| GPTBot (ChatGPT) | 402 |
error |
blocked |
| OAI-SearchBot (ChatGPT Search) | 402 |
error |
blocked |
| PerplexityBot (Perplexity) | 402 |
error |
blocked |
| 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) | 402 |
error |
blocked |
| Amazonbot (Alexa, Rufus) | 402 |
error |
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 1 crawler your own robots.txt already allows+1 crawler
Amazonbot is turned away before reading the page (answered with an HTTP error), while robots.txt permits it — 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 0 to 1 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 50/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.
- 5 crawlers are named and refused in robots.txt — a deliberate choice
ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, 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.
Get told if this changes
One email only when a measured crawler flips on getsurrey.co.uk, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people14%
- Readable without JavaScript0%
- robots.txt lets the crawlers in29%
- Facts in JSON-LD0%
- Content reachable, not buried60%
- Publishes a map of itself45%
- Plain structure50%
Re-run this audit live →
Full AI-visibility report for getsurrey.co.uk →
Browse the whole index →
Embed this score
Put the badge on getsurrey.co.uk — it links back here, and re-measures every time this index re-crawls.
<a href="https://shop.lumnika.com/ai-readiness/getsurrey.co.uk"><img src="https://shop.lumnika.com/ai-readiness/getsurrey.co.uk/badge.svg" alt="AI readability"></a>