Agent Web Index › homes.jp
Can AI assistants read homes.jp?
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.
B78 / 100
5 of 6 crawlers can read this page.
More readable than 60% of the 47,934 sites measured so far.
Structured data: WebSite.
What each crawler got back
| Crawler | HTTP | Result | robots.txt |
|---|---|---|---|
| ClaudeBot (Claude) | 200 | can read it | allowed-by-star |
| GPTBot (ChatGPT) | 200 | can read it | allowed-by-star |
| OAI-SearchBot (ChatGPT Search) | 200 | can read it | allowed-by-star |
| PerplexityBot (Perplexity) | 200 | can read it | 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 |
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 crawlerAmazonbot is turned away before reading the page (served a bot challenge instead of the page), 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 5 to 6 of 6 crawlers.
- Publish sitemap.xml and llms.txtsitemap.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.
Get told if this changes
One email only when a measured crawler flips on homes.jp, served to refused or back. No schedule, no newsletter; double opt-in, one-click stop.
The checks
- Answers AI agents like it answers people86%
- Readable without JavaScript100%
- robots.txt lets the crawlers in100%
- Facts in JSON-LD67%
- Content reachable, not buried65%
- Publishes a map of itself0%
- Plain structure96%
Sites with a similar score
Embed this score
Put the badge on homes.jp — it links back here, and re-measures every time this index re-crawls.
<a href="https://aivis.lumnika.com/ai-readiness/homes.jp"><img src="https://aivis.lumnika.com/ai-readiness/homes.jp/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,934 domains measured, updated continuously.
Part of the Agent Web Index, 47,934 domains measured, updated continuously.