logrocket.com — Agent-Adoption Score
25 checks evaluated · score 33 / 100
Web-discoverable basics in place; AI access policies (Content-Signal or AIPREF) not yet declared.
To reach L2 AI-Aware, pass:
Content-Signal (Cloudflare) or AIPREF Content-Usage directives declare what AI systems may do post-fetch — train, search-index, or generate answers.
Current: Skipped — dependency robots-txt-exists did not pass
Subscores
Where logrocket.com is most cited — and how those brands compare on agent-readiness
Top 2 categories where AI agents recommend logrocket.com most. Each card shows the most-cited brands in that category and where each sits on the agent-adoption ladder.
- #149 L1
- #256 L1
- #348 L1
- #428 L1
- #548 L1
- #8This scan33 L1
- #156 L1
- #249 L1
- #348 L1
- #428 L1
- #548 L1
- #14This scan33 L1
Per-check breakdown
Discoverability0 pass · 2 fail · 1 informational0
Non-2xx response (404)
robots.txt is the first file crawlers and agents check for access rules; silence defaults to blanket-allow. Per RFC 9309.
No valid sitemap found at any probed path
An XML sitemap is the route map agents use to find your pages. Without one they link-walk and miss deep or orphaned content.
Link header present but no agent-useful relation types found (only: preload)
Link: response headers expose related resources — API catalogs, service docs, alternates — before an agent parses HTML. Per RFC 8288.
Access Control0 pass · 0 fail · 1 informational0
Skipped — dependency robots-txt-exists did not pass
A blanket-allow posture (wildcard User-agent, Allow: /, no cross-bot blocks) declares that every crawler is welcome. Informational — no pass/fail.
Content Readability3 pass · 1 fail · 1 informational76
No llms.txt found at primary or fallback path
An llms.txt file gives agents a curated entry point into your docs — sitemap-equivalent, but sized for context windows. Per llmstxt.org.
llms-txt-valid cannot evaluate without llms.txt body
A well-formed llms.txt (H1 title, summary blockquote, linked sections) parses cleanly; a malformed one is skipped silently — worse than no file. Per llmstxt.org.
llms-txt-has-optional-section cannot evaluate without llms.txt body
Reports the shape of your llms.txt — Optional section, H2 count, link count — so you can tell at a glance whether agents get a skeleton or a full map.
Server-side rendering confirmed
Classifies the site as server-rendered, hydrated, or client-rendered (SPA) — what agents see without running JavaScript. A pure SPA reads as blank.
No sitemap URLs available to sample — cannot evaluate page size
Measures how much markdown each page feeds into an agent's context window. Under 50K fits cleanly; over 100K truncates mid-page — pages have context budgets too.
Correct HTTP 404 returned for non-existent path
Soft-404s (HTTP 200 on a missing page) make agents cache garbage as canonical content. An honest 4xx tells agents the URL is dead — drop it.
No sitemap URLs available to sample — cannot evaluate redirect behavior
Same-domain HTTP 3xx redirects work for agents. JavaScript redirects break agents without JS; cross-domain jumps read as tracking.
AGENTS.md not found at /AGENTS.md — HTTP 404 response
AGENTS.md is a coding-agent convention. ETH Zurich research (2026) found it often hurts those agents; we track presence to test the effect on websites. Informational.
Homepage response carries 1 of Cache-Control / ETag / Last-Modified: cache-control
Cache-Control, ETag, and Last-Modified headers let agents re-fetch only what changed — missing headers force full re-downloads. Informational.
Agent Endpoints0 pass · 2 fail · 3 informational0
No OAuth Protected Resource metadata at /.well-known/oauth-protected-resource
Protected Resource metadata identifies which authorization server protects your API. Paired with oauth-discovery, agents complete auth without reading docs. Per RFC 9728.