Head to head
statinside.com vs stripes.com
stripes.com is more readable to AI, 70 against 48 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 1 hour ago · full report
Scanned 4 hours ago · full report
Where the difference is by dimension
| Dimension | statinside.com | stripes.com |
|---|---|---|
| Reach Whether AI crawlers and answer-engine fetchers are permitted to request the page at all. What h… |
40 / 40 | 38 / 40 |
| Readability Whether a fetcher that does not execute JavaScript receives the actual content, in markup an ex… |
4 / 25 | 22 / 25 |
| Structure Machine-readable markup that states the page's type, entities, canonical URL, and discrete fact… |
3 / 20 | 9 / 20 |
| Attribution Signals that let an answer engine name the author, date the content, resolve the publisher, and… |
1 / 15 | 1 / 15 |
The measurements side by side
| Measurement | statinside.com | stripes.com |
|---|---|---|
| Answer engines blocked | 0 | 1 |
| Training crawlers blocked | 0 | 5 |
| Refuses AI agents at the edge | no | no |
| Words of text without JavaScript | 1 | 1,677 |
| Structured data | no | no |
| Sitemap | no | yes |
| llms.txt | no | no |
statinside.com blocks no tracked AI crawler in robots.txt.
stripes.com blocks Amazonbot, ChatGPT-User, ClaudeBot, FacebookBot, Google-Extended, GPTBot.
Compare your own site
Free, no account. To watch a competitor and get an email when their crawler policy changes, see pricing.