Head to head
some.porn vs ineed.porn
some.porn is more readable to AI, 85 against 52 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 1 hour ago · full report
Where the difference is by dimension
| Dimension | some.porn | ineed.porn |
|---|---|---|
| Reach Whether AI crawlers and answer-engine fetchers are permitted to request the page at all. What h… |
40 / 40 | 31 / 40 |
| Readability Whether a fetcher that does not execute JavaScript receives the actual content, in markup an ex… |
22 / 25 | 13 / 25 |
| Structure Machine-readable markup that states the page's type, entities, canonical URL, and discrete fact… |
20 / 20 | 7 / 20 |
| Attribution Signals that let an answer engine name the author, date the content, resolve the publisher, and… |
3 / 15 | 1 / 15 |
The measurements side by side
| Measurement | some.porn | ineed.porn |
|---|---|---|
| Answer engines blocked | 0 | 0 |
| Training crawlers blocked | 0 | 2 |
| Refuses AI agents at the edge | no | yes |
| Words of text without JavaScript | 1,062 | 237 |
| Structured data | yes | no |
| Sitemap | yes | no |
| llms.txt | no | no |
Compare your own site
Free, no account. To watch a competitor and get an email when their crawler policy changes, see pricing.