Agent Web Index › alexisregen.com

Can AI assistants read alexisregen.com?

Measured on 2026-09-19 by asking the site 5 times — once as a browser, once as each of the 4 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.

C71 / 100
2 of 4 crawlers can read this page.
More readable than 42% of the 47,934 sites measured so far. Structured data: FAQPage, BreadcrumbList.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged no-file
GPTBot (ChatGPT)403 challenged no-file
OAI-SearchBot (ChatGPT Search)200 can read it no-file
PerplexityBot (Perplexity)200 can read it no-file
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 no-file

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

  1. Let in the 2 crawlers your own robots.txt already allows+2 crawlers
    ClaudeBot, GPTBot 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 2 to 4 of 4 crawlers.
  2. Publish sitemap.xml and llms.txt
    sitemap.xml and llms.txt are 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 56/100. These are the cheapest signals on the page and the first ones an assistant uses to decide what the site is.

Get told if this changes

One email only when a measured crawler flips on alexisregen.com, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.

The checks

Full AI-visibility report for alexisregen.com → Scan your own site →

Sites with a similar score

alexisbarcelona.comC 71alexissendai.comC 71agilemanifesto.orgC 71alibabacloud.comC 71adplay.ruC 71andrews.eduC 71bdc.caC 71envi.myshopify.comC 71videobyte.comC 71zane.myshopify.comC 70up-tempo.myshopify.comC 70nderegistrationportal.ngC 70

Browse the whole index →

Embed this score

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

alexisregen.com AI readability: C 71/100 
<a href="https://aivis.lumnika.com/ai-readiness/alexisregen.com"><img src="https://aivis.lumnika.com/ai-readiness/alexisregen.com/badge.svg" alt="AI readability"></a>
Method. 5 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,934 domains measured, updated continuously.