Agent Web Index › harvardlawreview.org

Can AI assistants read harvardlawreview.org?

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.

B80 / 100
2 of 6 crawlers can read this page.
More readable than 64% of the 47,315 sites measured so far. Structured data: WebPage, BreadcrumbList, WebSite, Organization.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)403 challenged allowed-by-star
GPTBot (ChatGPT)403 challenged blocked
OAI-SearchBot (ChatGPT Search)200 can read it 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)200 can read it 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

  1. Let in the 3 crawlers your own robots.txt already allows+3 crawlers
    ClaudeBot, PerplexityBot, 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 2 to 5 of 6 crawlers.
  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. 1 crawler is named and refused in robots.txt — a deliberate choice
    GPTBot is blocked by a rule that names it. 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 harvardlawreview.org →

Sites with a similar score

speechify.comB 81harvard.eduB 80hatarako.netB 80guardianlife.comB 80hello.pornB 80glaze.com.qaB 80hood.deB 80faplane.comB 80k5learning.comB 800catch.comB 80rctiplus.comB 80chemie.deB 79

Browse the whole index →

Embed this score

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

harvardlawreview.org AI readability: B 80/100
<a href="https://shop.lumnika.com/ai-readiness/harvardlawreview.org"><img src="https://shop.lumnika.com/ai-readiness/harvardlawreview.org/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.