Can agents find your site and its capabilities?
The page registers no tools via the WebMCP browser API (navigator.modelContext).
Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.
Crawled 12 of 12 discovered pages beyond the homepage.
Could not identify a known website platform (custom stack or unrecognised).
Can agents understand your content?
Homepage ignored Accept: text/markdown and returned HTML.
Fix: Serve a markdown version of high-value pages when the client asks for text/markdown. AI summarisers, chatbots and IDE agents prefer markdown — fewer tokens, no DOM noise.
Only 0/5 images have width+height — large CLS risk.
Fix: Set width and height on every <img> so the browser reserves space before the image loads. A layout that shifts while loading makes an AI agent mis-click the element it targeted.
Found 2 <h1> tags. Most AI summarisers expect exactly one.
Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.
10 of 12 pages are missing <title> and/or <h1>: /menu, /menu/drinks/protein-beverages, /menu/drinks/hot-coffee, /menu/drinks/cold-coffee, /menu/drinks/hot-tea, /menu/drinks/cold-tea, /menu/drinks/refreshers, /menu/drinks/frappuccino-blended-beverage, /menu/drinks/hot-chocolate-lemonade-more, /menu/drinks/bottled-beverages.
Fix: Make sure every page sets a unique <title> and exactly one <h1>. The title is how an AI agent confirms it landed on the right page after navigating.
10 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /menu (4w), /menu/drinks/protein-beverages (4w), /menu/drinks/hot-coffee (4w), /menu/drinks/cold-coffee (4w), /menu/drinks/hot-tea (4w), /menu/drinks/cold-tea (4w), /menu/drinks/refreshers (4w), /menu/drinks/frappuccino-blended-beverage (4w), /menu/drinks/hot-chocolate-lemonade-more (4w), /menu/drinks/bottled-beverages (4w).
Fix: Pre-render or server-render these pages so AI crawlers (which usually don't execute JS) can read them. Frameworks: Next.js Server Components, Nuxt SSR, Astro, or build-time prerendering.
Homepage server response contains 405 words of visible text — content is reachable without executing JavaScript.
Detected 1 cookie-banner element but none look agent-hostile (small, dismissible, or offer a reject option).
Homepage contains ~452 elements.
16 headings, no level skips.
Language declared as "en-US".
5 of 5 <img> tags have alt attributes.
21 internal links found.
All four landmark elements present (main, header, footer, nav).
Can agents actually operate the page?
The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.
Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.
All 10 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-*]` attributes match their roles passed.
`[aria-hidden="true"]` is not present on the document `<body>` passed.
`[aria-hidden="true"]` elements do not contain focusable descendents passed.
`[role]`s have all required `[aria-*]` attributes passed.
`[role]` values are valid passed.
`[aria-*]` attributes are valid and not misspelled passed.
`[aria-*]` attributes have valid values passed.
Buttons have an accessible name passed.
Document has a `<title>` element passed.
Links have a discernible name passed.
Lighthouse accessibility score: 100/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
0.020 (field data from CrUX) — good.
517ms (field data from CrUX) — good.
No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.
Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.
Can agents safely transact?
/.well-known/oauth-authorization-server returned the site's HTML app shell — treating as not published.
Fix: Publish /.well-known/oauth-authorization-server so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.
/.well-known/oauth-protected-resource returned the site's HTML app shell — treating as not published.
Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.
No Web Bot Auth signature headers — sites can't verify agent identity.
Fix: Web Bot Auth (IETF HTTP Message Signatures over Signature / Signature-Input) lets you cryptographically verify which agent is hitting you. Several CDNs offer turn-key support; otherwise skip until vendor support matures.
No Referrer-Policy header on the homepage.
Fix: Add `Referrer-Policy: strict-origin-when-cross-origin` so outbound links don't leak full URLs (including query strings) to third parties.
x-powered-by: cwa00
Fix: Configure your web server / framework to suppress version strings. They give attackers a free shortlist of known CVEs to try.
CSP header present.
max-age=31536000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://starbucks.com → https://www.starbucks.com/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 173 more days (Jan 10 23:59:59 2027 GMT, issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1).
X-Content-Type-Options: nosniff.
CSP frame-ancestors directive present.