www.ebay.com
Metrics
Final screenshot
Diagnostics
95% of content requires JS · 5% of rendered content recovered (rest is placeholder/wrong)
Fix: Server-render or statically generate the main content so a non-JS agent still receives it; make client rendering a progressive enhancement, not the source of truth.
signal 0.10 · JSON-LD 0/1 · missing: structured-data
Fix: Wrap the real content in <main>/<article>, cut repeated nav/boilerplate, and keep the primary content dense and early in the DOM.
Rendered profile: headless
Metrics
Final screenshot
Diagnostics
44% of content requires JS · 56% of rendered content recovered (rest is placeholder/wrong)
Fix: Server-render or statically generate the main content so a non-JS agent still receives it; make client rendering a progressive enhancement, not the source of truth.
signal 0.02 · JSON-LD 0/1 · missing: structured-data
Fix: Wrap the real content in <main>/<article>, cut repeated nav/boilerplate, and keep the primary content dense and early in the DOM.
Rendered profile: headless
Access & discovery checks — separate from the gated CAV metrics above. Click an issue for business impact, what we measured, and how to fix. · Take the Agent Readiness course →
Agent files & endpoints
Issues (8)
✗ robots.txt allows AI bots high impact Blocks: * (all)
Business impact If robots.txt blocks AI crawlers you are invisible to ChatGPT, Claude and Perplexity — they skip you and recommend a competitor instead.
What we measured We read /robots.txt and test it against 16 AI user-agents (GPTBot, ClaudeBot, PerplexityBot, …) for a Disallow that blocks them.
How to fix Allow major AI bots to public content; restrict only private paths (/admin, /api).
User-agent: GPTBot
Allow: /
Disallow: /admin/✗ llms.txt present high impact Absent at /llms.txt and /.well-known/llms.txt
Business impact llms.txt is the robots.txt for AI: it tells agents what your site is, what matters, and where to find it. Without it AI guesses — and guessing means inaccurate recommendations and lost visibility.
What we measured We fetch /llms.txt and /.well-known/llms.txt and validate the spec (H1 title + a one-line blockquote summary). We also note /llms-full.txt (your full content as Markdown).
How to fix Create /llms.txt with a short summary + key pages; optionally /llms-full.txt with full content in Markdown.
# Your Site
> One-line description for AI agents.
## Key pages
- /products — catalog
- /pricing — plans
- /docs — documentationSpec: https://llmstxt.org
✗ Structured data (JSON-LD) medium impact No JSON-LD found
Business impact Schema.org JSON-LD tells agents what a page IS (product, article, business) with typed fields (price, rating, hours). Without it agents extract less reliably.
What we measured We parse <script type=application/ld+json>, validate it, and check for populated @type fields.
How to fix Add JSON-LD: Organization/LocalBusiness on the homepage, Product on product pages, Article on posts.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Your Co","url":"https://example.com"}</script>Spec: https://schema.org/
✗ XML sitemap present medium impact No /sitemap.xml
Business impact A sitemap is your table of contents for AI crawlers. Without it agents follow homepage links and miss deep pages (products, docs, pricing) — shrinking what they can recommend.
What we measured We fetch /sitemap.xml (and /sitemap_index.xml), confirm valid XML with <loc> entries, and check <lastmod> freshness.
How to fix Generate an XML sitemap of all public pages with current lastmod dates and reference it in robots.txt.
# robots.txt
Sitemap: https://example.com/sitemap.xml~ Server response (TTFB) low impact 1000ms (good ≤800, warn ≤1800)
Business impact Slow servers cause agents to time out and move on. Fast response keeps you in the running.
What we measured We time the response (time-to-first-byte) against good (<800ms) / warn (<1800ms) thresholds.
How to fix Use a CDN, caching and an optimized origin to get TTFB under 800ms.
Spec: https://web.dev/ttfb/
~ agents.json discovery low impact Absent (emerging standard)
Business impact agents.json describes what your site can DO for agents (services, endpoints, capabilities) — an emerging discovery standard. Early adopters get native agent integration.
What we measured We check /agents.json and /.well-known/agents.json for a valid configuration.
How to fix Publish /agents.json describing your site's capabilities and actions.
Spec: https://agents-json.org
~ WebMCP endpoint low impact Absent (emerging standard)
Business impact WebMCP lets agents call actions on your site directly (book, buy, query) instead of scraping the DOM. Early adopters get native AI-agent interoperability.
What we measured We check /.well-known/webmcp and /webmcp.json for a valid actions array.
How to fix Add a WebMCP endpoint exposing your key actions to agents.
Spec: https://webmcp.org
~ API documentation low impact No OpenAPI/Swagger found
Business impact Programmatic agents prefer a typed API. An OpenAPI/Swagger spec lets them integrate without scraping.
What we measured We probe /openapi.json, /swagger.json, /api-docs and /.well-known/openapi.json.
How to fix Publish an OpenAPI spec at a well-known path.
Passed audits (4)
A deeper scan (a second render, ~30–60s): network waterfall, unused JavaScript, long tasks, and prioritized fixes. Runs only when you ask; the result is cached so it never re-runs.