Agent Web Index › recordonline.com

Can AI assistants read recordonline.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.

F33 / 100
0 of 6 crawlers can read this page.
More readable than 1% of the 47,315 sites measured so far. No JSON-LD.

What each crawler got back

CrawlerHTTPResultrobots.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
opted out in robots.txt blocked
Meta-ExternalAgent (Meta AI)402 error blocked
Amazonbot (Alexa, Rufus)402 error blocked

Fastly 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. 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.
  2. 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.
  3. 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.
  4. 6 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot, OAI-SearchBot, PerplexityBot, 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 recordonline.com →

Sites with a similar score

geodruid.comF 36avtub.netF 35doradobet.comF 34reconn.ruF 33registerguard.comF 33providencejournal.comF 33roadsideamerica.comF 33news-journalonline.comF 33tallahassee.comF 33clarionledger.comF 33burlingtonfreepress.comF 32

Browse the whole index →

Embed this score

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

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