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?
Only 0 internal links on the homepage.
Fix: Add at least 5-10 internal links pointing to your top product, pricing, docs, blog and about pages so an AI agent can navigate to them from the homepage.
Homepage returns text/markdown when requested.
Homepage server response contains 943 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~1399 elements.
34 headings, no level skips.
Language declared as "en".
51 of 51 <img> tags have alt attributes.
51/51 images set width and height — no layout shift.
All four landmark elements present (main, header, footer, nav).
Exactly one <h1> on the homepage.
All 12 reachable key pages have both a <title> and <h1>.
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.
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.
2/4 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.
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.
0.240 (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 14 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-*]` attributes match their roles passed.
`button`, `link`, and `menuitem` elements have accessible names 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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. 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.
ARIA IDs are unique passed.
`<frame>` or `<iframe>` elements have a title passed.
Links have a discernible name passed.
Lighthouse accessibility score: 97/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
12 of 12 visible interactive form fields have labels.
4/4 data-collecting forms mark required fields.
430ms (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 404.
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 404.
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.
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.
cf-ray: a1eb155fcd7cfba4-AMS (Cloudflare); Server: cloudflare
max-age=63072000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://activecampaign.com → https://www.activecampaign.com/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 97 more days (Oct 26 23:59:59 2026 GMT, issuer: GeoTrust EV RSA CA G2).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.