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.
If your llms.txt file does not follow recommendations, large language models may not be able to understand how you want your website to be crawled or used for training. The [llms.txt](https://llmstxt.org/) file should be a Markdown file containing at least one H1 header.
Found /.well-known/agent-skills/index.json but its body did not parse as JSON.
Fix: Serve a valid JSON index at /.well-known/agent-skills/index.json.
Found /AGENTS.md but it is served as "unknown", not Markdown.
Fix: Serve AGENTS.md as Markdown (text/markdown). See agents.md.
/agents.txt exists but the body is essentially empty.
Fix: Either populate the manifest or remove it — empty agent manifests confuse crawlers more than they help.
/.ai.txt is reachable but the body looks empty or malformed.
Fix: Provide either YAML frontmatter (---\nkey: value\n---) or key: value lines. The spec is unstable — keep it short.
Per llmstxt.org, group key pages under "## Section" headings as "[name](url)" links.
Fix: Add "## Docs" / "## Products" sections listing your key pages as markdown links.
Per llmstxt.org, follow the H1 with a "> short summary" blockquote.
Fix: Add a "> One-sentence description of your site." blockquote under the H1.
Per llmstxt.org, /llms.txt should open with a single "# Project name" H1.
Fix: Make the first line of /llms.txt a "# Your site name" H1.
Found https://ah.nl/llms.txt.
Crawled 12 of 12 discovered pages beyond the homepage.
Lighthouse Agentic Browsing audits ran.
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.
Homepage contains ~2526 elements — heavy.
Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.
104 of 105 images have alt attributes (99%).
Fix: Add alt text to the remaining images. Empty alt="" is fine for purely-decorative graphics.
Only 10/105 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 7 <h1> tags. Most AI summarisers expect exactly one.
Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.
Homepage server response contains 1107 words of visible text — content is reachable without executing JavaScript.
26 headings, no level skips.
Language declared as "nl-NL".
250 internal links found.
All four landmark elements present (main, header, footer, nav).
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.
1.22s (field data from CrUX) — needs improvement.
Fix: Every request an AI agent makes pays this server latency, and agents make many requests per task. Reduce TTFB with edge caching, a CDN, and shipping less server-side work per request.
All 6 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.
`[aria-hidden="true"]` elements do not contain focusable descendents passed.
`[role]`s have all required `[aria-*]` attributes passed.
`[role]` values are valid passed.
Buttons have an accessible name passed.
Links have a discernible name passed.
Lighthouse accessibility score: 91/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
2 of 2 visible interactive form fields have labels.
All audits passed
0
0.030 (field data from CrUX) — good.
1 form missing annotations
Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.
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.
x-akamai-transformed: 0 - 0 - (Akamai)
CSP header present.
max-age=31536000, includeSubDomains=true, preload=false.
Homepage scheme is https:.
http://ah.nl → https://www.ah.nl/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: strict-origin-when-cross-origin.
Valid for 37 more days (Aug 27 23:59:59 2026 GMT, issuer: Sectigo Public Server Authentication CA OV E36).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.