Agent Web Index › gizmodo.jp

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

A86 / 100
2 of 4 crawlers can read this page.
More readable than 74% of the 47,934 sites measured so far. Structured data: NewsMediaOrganization, WebSite.

What each crawler got back

CrawlerHTTPResultrobots.txt
ClaudeBot (Claude)200 allowed by the server, blocked in robots.txt blocked
GPTBot (ChatGPT)200 allowed by the server, blocked in robots.txt blocked
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

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

  1. 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.
  2. 2 crawlers are named and refused in robots.txt — a deliberate choice
    ClaudeBot, GPTBot 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.

Get told if this changes

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

The checks

History

2026-09-18: 86 · 2026-09-19: 86

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

Sites with a similar score

corsetsqueen.comA 87github.blogA 86glamourmagazine.co.ukA 86gibson.comA 86globes.co.ilA 86gaurang.coA 86greyweave.comA 86fcdynamo.ruA 86hunter.ioA 86bodgirls.comA 86momentumhosting.cloudA 86kesq.comA 85

Browse the whole index →

Embed this score

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

gizmodo.jp AI readability: A 86/100 
<a href="https://aivis.lumnika.com/ai-readiness/gizmodo.jp"><img src="https://aivis.lumnika.com/ai-readiness/gizmodo.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.