Head to head

mysanantonio.com vs spectator.com

spectator.com is more readable to AI, 88 against 54 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.

mysanantonio.com 54/10054mysanantonio.com

Scanned 2 days ago · full report

spectator.com 88/10088spectator.com

Scanned 2 days ago · full report

Where the difference is by dimension

Dimensionmysanantonio.comspectator.com
Reach
Whether AI crawlers and answer-engine fetchers are permitted to request the page at all. What h…
36 / 4040 / 40
Readability
Whether a fetcher that does not execute JavaScript receives the actual content, in markup an ex…
9 / 2518 / 25
Structure
Machine-readable markup that states the page's type, entities, canonical URL, and discrete fact…
5 / 2020 / 20
Attribution
Signals that let an answer engine name the author, date the content, resolve the publisher, and…
1 / 1510 / 15

The measurements side by side

Measurementmysanantonio.comspectator.com
Answer engines blocked60
Training crawlers blocked90
Refuses AI agents at the edgenono
Words of text without JavaScript371,166
Structured datanoyes
Sitemapyesyes
llms.txtnono

mysanantonio.com blocks anthropic-ai, Applebot-Extended, Bytespider, CCBot, Claude-User, ClaudeBot, cohere-ai, Diffbot, DuckAssistBot, omgili, omgilibot, Perplexity-User, PerplexityBot, Scrapy, Timpibot, YouBot.

spectator.com blocks no tracked AI crawler in robots.txt.

Compare your own site

Free, no account. To watch a competitor and get an email when their crawler policy changes, see pricing.