← Analyze a URL · Tested sites

www.w3.org

Report from 7/2/2026, 10:34:27 AM https://www.w3.org
DesktopMobile
Agent blocked: bot-block (raw HTTP 403, only 45 tokens recovered) — scores reflect the block page, not your content.
37
Overall score
weighted CAV (0–100)
BLOCKED
0–4950–8990–100

Metrics

0%
CRR Content Recovery Poor
0.35
SSD Semantic Signal Density Poor
45 tok
TC Token Cost Good
14 ms
TTFUT Time to First Useful Token N/A

Final screenshot

Final screenshot of https://www.w3.org

Diagnostics

high CRR Agents are blocked before they see the page

A non-browser agent got a block/challenge (bot-block (raw HTTP 403, only 45 tokens recovered)). Every score below is measured against that wall, not your content.

Fix: Allowlist legitimate agent user-agents / IP ranges in your WAF or bot-management rules, and serve real content (not a challenge) to them.

high CRR Content is hidden behind JavaScript

100% of content requires JS

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.

high SSD Low signal-to-noise for agents

signal 0.70 · 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

Agent Discoverability 62/100 · Needs Work

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

✗ llms.txt Absent at /llms.txt and /.well-known/llms.txt Learn →
✓ robots.txt (AI bots) Major AI bots allowed Learn →
✗ sitemap.xml No /sitemap.xml Learn →
✗ JSON-LD structured data No JSON-LD found Learn →
~ agents.json Absent (emerging standard) Learn →
~ WebMCP endpoint Absent (emerging standard) Learn →
~ OpenAPI / API docs No OpenAPI/Swagger found Learn →

Issues (7)

~ Machine-readable prices medium impact No prices found (fine for non-commercial sites)

Business impact When a user asks an agent 'how much does X cost', it needs readable pricing. Hidden, JS-only or 'request a quote' pricing means the agent can't answer — and recommends someone who can.

What we measured We scan the HTML for price patterns and Schema.org Offer/PriceSpecification markup.

How to fix Expose prices (or a starting-from range) in HTML and add Schema.org Offer.

<script type="application/ld+json">{"@type":"Offer","price":"29.90","priceCurrency":"EUR"}</script>

Spec: https://schema.org/Offer

✗ 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.

Learn how to implement →

# Your Site
> One-line description for AI agents.

## Key pages
- /products — catalog
- /pricing — plans
- /docs — documentation

Spec: 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.

Learn how to implement →

<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.

Learn how to implement →

# robots.txt
Sitemap: https://example.com/sitemap.xml

Spec: https://www.sitemaps.org/

~ 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.

Learn how to implement →

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.

Learn how to implement →

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.

Learn how to implement →

Spec: https://www.openapis.org/

Passed audits (5)

✓ robots.txt allows AI bots✓ No CAPTCHA wall✓ No content-blocking cookie wall✓ No login wall on public content✓ Server response (TTFB)
Full profile — how to improve · unused JS · network · timing

How to improve

mediumReduce unused JavaScript

125 KiB (44%) of JS goes unused. Code-split, lazy-load below-the-fold scripts, and drop unused dependencies — less JS also lowers CAV Token Cost (TC) and speeds up agent parsing.

JavaScript coverage

125 KiB unused of 285 KiB (44% unused JS) — unused JS inflates Token Cost (TC) and slows the agent's parse.

ScriptSizeUnused
https://www.w3.org/cdn-cgi/challenge-platform/h/g/orchestrate/chl_page/v1?ray=a14b14326c26497b215 KiB80 KiB (37%)
https://challenges.cloudflare.com/turnstile/v0/g/37d84357f321/api.js?onload=CyjyG7&render=explicit67 KiB44 KiB (66%)
https://www.w3.org/3 KiB0 KiB (0%)

Network

9Requests
126 KiBTransferred
4Scripts
0%3rd-party
0Long tasks
Script (4)
97 KiB
XHR (1)
15 KiB
Image (1)
6 KiB
Document (2)
5 KiB
Other (1)
5 KiB

Heaviest requests

URLTypeStatusTransfer
https://www.w3.org/cdn-cgi/challenge-platform/h/g/orchestrate/chl_page/v1?ray=a14b14326c26497bScript20075 KiB
https://challenges.cloudflare.com/turnstile/v0/g/37d84357f321/api.js?onload=CyjyG7&render=explicitScript20022 KiB
https://www.w3.org/cdn-cgi/challenge-platform/h/g/fo/3772722130:1782965119:S5oVqS0bz1MwOmPyAw0HJCYHVWtr1JkoU1lkmN3m7rE/a14b14326c26497b/J0ME_ijbNBdc1B5_ORgSjMHvS5s753XQKx2cxu57buo-1782968343-1.2.1.1-7PzHUOtCbQVFFVrYadmtLcaahbB_mbrCjR3O6D_am4Yqiy8Qp0IMdZUdu0mhx6BSXHR20015 KiB
https://www.w3.org/favicon.icoImage4036 KiB
https://www.w3.org/Document4035 KiB
https://www.w3.org/favicon.icoOther4035 KiB
blob:https://www.w3.org/c1b32568-cb1b-4c4e-bced-89637f65b472Script—0 KiB
blob:https://www.w3.org/7d8d18d5-fc13-4e04-acfc-7ec2a1cd0ad0Script—0 KiB
https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/g/turnstile/f/av0/rch/on3k0/0x4AAAAAAADnPIDROrmt1Wwj/light/fbE/new/normal?lang=autoDocument2000 KiB
Analyzing…
running mobile + desktop · ~30s