Agent Web Index › jrc.or.jp

Can AI assistants read jrc.or.jp?

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.

C70 / 100
4 of 4 crawlers can read this page.
More readable than 37% of the 47,934 sites measured so far. No JSON-LD.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)200 can read it no-file
GPTBot (ChatGPT)200 can read it 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

Imperva 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 35/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 jrc.or.jp, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.

The checks

History

2026-09-18: 70 · 2026-09-19: 70

Full AI-visibility report for jrc.or.jp → Scan your own site →

Sites with a similar score

jquerymobile.comC 70jtestshop.myshopify.comC 70journalists.orgC 70julyseven.myshopify.comC 70jofan.myshopify.comC 70kaukasus.myshopify.comC 70itemfix.comC 70ladyxena.comC 70ghcr.ioC 70moresolutions.myshopify.comC 70aapd.orgC 70tremendo.myshopify.comC 70

Browse the whole index →

Embed this score

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

jrc.or.jp AI readability: C 70/100 
<a href="https://aivis.lumnika.com/ai-readiness/jrc.or.jp"><img src="https://aivis.lumnika.com/ai-readiness/jrc.or.jp/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.