myjcom.jp vs tokyo-np.co.jp
tokyo-np.co.jp is more readable to AI, 83 against 65 out of 100. Both were measured with the same audit: robots.txt policy for 48 AI agents, live requests under four crawler user agents, and a JavaScript-free read of the homepage.
Scanned 21 hours ago · full report
Scanned 21 hours ago · full report
Where the difference is by dimension
| Dimension | myjcom.jp | tokyo-np.co.jp |
|---|---|---|
| Reach Whether AI crawlers and answer-engine fetchers are permitted to request the page at all. What h… |
39 / 40 | 32 / 40 |
| Readability Whether a fetcher that does not execute JavaScript receives the actual content, in markup an ex… |
17 / 25 | 22 / 25 |
| Structure Machine-readable markup that states the page's type, entities, canonical URL, and discrete fact… |
4 / 20 | 20 / 20 |
| Attribution Signals that let an answer engine name the author, date the content, resolve the publisher, and… |
1 / 15 | 4 / 15 |
The measurements side by side
| Measurement | myjcom.jp | tokyo-np.co.jp |
|---|---|---|
| Answer engines blocked | 0 | 11 |
| Training crawlers blocked | 0 | 20 |
| Refuses AI agents at the edge | no | no |
| Words of text without JavaScript | 324 | 418 |
| Structured data | no | yes |
| Sitemap | no | yes |
| llms.txt | no | no |
myjcom.jp blocks no tracked AI crawler in robots.txt.
tokyo-np.co.jp blocks AI2Bot, Amazonbot, anthropic-ai, Applebot-Extended, Bytespider, CCBot, ChatGPT-User, Claude-SearchBot, Claude-User, ClaudeBot, cohere-ai, cohere-training-data-crawler, Diffbot, DuckAssistBot, FacebookBot, Google-CloudVertexBot, Google-Extended, GPTBot, ImagesiftBot, Kangaroo Bot, Meta-ExternalAgent, Meta-ExternalFetcher, OAI-SearchBot, omgili, omgilibot, PanguBot, Perplexity-User, PerplexityBot, Scrapy, SemrushBot-OCOB, Timpibot, YouBot.
Compare your own site
Free, no account. To watch a competitor and get an email when their crawler policy changes, see pricing.