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?
No <h1> tag found on the homepage.
Fix: Add exactly one <h1> that names the page. AI summarisers use it as the document title.
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.
12 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /power-ups (50w), /templates (50w), /power-ups/586be36326cc4c7e9f70beb3/jira (50w), /power-ups/5893c2b56bde057070fbc1b7/miro (50w), /power-ups/5b4765f383dd7c75d8e57be4 (50w), /templates/marketing (50w), /templates/product-management (50w), /templates/engineering (50w), /templates/design (50w), /templates/business (50w), /templates/remote-work (50w), /power-ups/55a5d917446f51777421000a (50w).
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 1243 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~1188 elements.
18 headings, no level skips.
Language declared as "en".
13 of 13 <img> tags have alt attributes.
13/13 images set width and height — no layout shift.
62 internal links found.
All four landmark elements present (main, header, footer, nav).
All 12 reachable key pages have both a <title> and <h1>.
Can agents actually operate the page?
0.260 (field data from CrUX) — poor.
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.
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.
No autocomplete attributes on any data-collecting form field.
Fix: Add autocomplete hints (email, tel, name, etc.) so form-filling agents and browsers can populate fields without guessing.
0/2 data-collecting forms expose errors via ARIA attributes.
Fix: Wire inputs to their error containers with `aria-describedby` and toggle `aria-invalid` on validation failure. Agents that can't see styled error text rely on these attributes.
0/2 data-collecting forms mark required fields.
Fix: Add the `required` attribute (or `aria-required="true"`) to mandatory inputs. Form-filling agents skip optional fields by default — without markers they over-fill.
No HTML5 validation hints (pattern / minlength / maxlength / min / max) on any data-collecting form input.
Fix: Publish input constraints via HTML attributes so agents and browsers can validate client-side.
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: 92/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
3 of 3 visible interactive form fields have labels.
404ms (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 Content-Security-Policy header on the homepage.
Fix: Add a Content-Security-Policy. Even a strict default-src directive cuts XSS blast radius dramatically. Start in report-only mode to find violations.
HSTS configured (max-age=63072000) but missing includeSubDomains.
Fix: Add `includeSubDomains` so subdomains inherit the policy.
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-Frame-Options header and no CSP frame-ancestors directive.
Fix: Add `X-Frame-Options: SAMEORIGIN` (or a CSP frame-ancestors directive) to prevent your site being framed by a phishing host.
x-amz-cf-id: TAU3wSyWy7zXA4vk0BlMoYSCgGavvwjoTIQkuWx3 (AWS CloudFront)
Homepage scheme is https:.
http://trello.com → https://trello.com/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 164 more days (Jan 1 23:59:59 2027 GMT, issuer: Amazon RSA 2048 M04).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.