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