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 returned 401 — couldn't analyse structure.
Homepage returned 401 for Accept: text/markdown.
Homepage returned 401.
12 of 12 pages are missing <title> and/or <h1>: /arc/outboundfeeds/sitemap?outputType=xml, /arc/outboundfeeds/sitemap?outputType=xml&from=100, /arc/outboundfeeds/sitemap?outputType=xml&from=200, /arc/outboundfeeds/sitemap?outputType=xml&from=300, /arc/outboundfeeds/sitemap?outputType=xml&from=400, /arc/outboundfeeds/sitemap?outputType=xml&from=500, /arc/outboundfeeds/sitemap?outputType=xml&from=600, /arc/outboundfeeds/sitemap?outputType=xml&from=700, /arc/outboundfeeds/sitemap?outputType=xml&from=800, /arc/outboundfeeds/sitemap?outputType=xml&from=900, /arc/outboundfeeds/sitemap?outputType=xml&from=1000, /arc/outboundfeeds/sitemap?outputType=xml&from=1100.
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.
All 12 pages return ≥80 words of visible text without JavaScript.
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.
0.110 (field data from CrUX) — needs improvement.
Fix: A layout that shifts while loading makes an AI agent mis-click the element it targeted. Eliminate CLS by setting explicit width/height on images and embeds, avoiding inserted content above existing content, and reserving space for ad slots.
All 3 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-hidden="true"]` is not present on the document `<body>` passed.
Document has a `<title>` element passed.
`<frame>` or `<iframe>` elements have a title passed.
Lighthouse accessibility score: 94/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
442ms (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?
No Strict-Transport-Security header on the homepage.
Fix: Add `Strict-Transport-Security: max-age=15768000; includeSubDomains` so browsers and agents refuse to downgrade to http for at least six months.
/.well-known/oauth-authorization-server returned 403.
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 403.
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.
Homepage returned 401.
Homepage returned 401 — couldn't scan for error markers.
Homepage returned 401 — couldn't scan for mixed content.
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.
No `X-Content-Type-Options: nosniff` header.
Fix: Add `X-Content-Type-Options: nosniff` to prevent browsers (and some agents) from re-interpreting your responses as a different content type.
x-amz-cf-id: JyephAKqi5u3SZExzhwMaBkS6yxWRy_Xur4yxS1t (AWS CloudFront)
CSP header present.
Homepage scheme is https:.
http://reuters.com → https://www.reuters.com/ (1 hop).
Valid for 143 more days (Dec 11 23:59:59 2026 GMT, issuer: Sectigo Public Server Authentication CA OV R40).
Server / X-Powered-By headers don't leak product version.
CSP frame-ancestors directive present.