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.
Found https://meetup.com/llms.txt.
Found at least one "[name](url)" markdown link.
Found a "> summary" blockquote.
First line is a top-level "# Title" heading.
Crawled 9 of 12 discovered pages beyond the homepage.
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.
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 ~2419 elements — heavy.
Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.
185/204 images have explicit width+height.
Fix: Add width and height to every <img>. Without them the browser doesn't know the aspect ratio and reflows the page on load (CLS).
Found 2 <h1> tags. Most AI summarisers expect exactly one.
Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.
1 of 9 pages are missing <title> and/or <h1>: /sw_pro_1.xml.gz.
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.
Homepage server response contains 1393 words of visible text — content is reachable without executing JavaScript.
64 headings, no level skips.
Language declared as "en-US".
204 of 204 <img> tags have alt attributes.
6 internal links found.
All four landmark elements present (main, header, footer, nav).
All 9 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.
Fix: Give every <button> discernible text or an aria-label so agents can identify it.
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with 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 of 10 agent-critical accessibility audits failed (Buttons do not have an accessible name) — an agent may be unable to identify or operate the affected elements.
Fix: Fix the failing agent-accessibility audits listed below (accessible names on controls, valid ARIA roles/relationships, nothing interactive hidden from the tree).
1.71s (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.
`[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.
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.
2 of 2 visible interactive form fields have labels.
0
0.010 (field data from CrUX) — good.
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.
HSTS max-age=7776000 is below six months.
Fix: Raise max-age to at least 15768000 (six months). The HSTS preload list requires 31536000 (one year).
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.
CSP header present.
Homepage scheme is https:.
http://meetup.com → https://www.meetup.com/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 173 more days (Jan 10 17:39:11 2027 GMT, issuer: GlobalSign Atlas R3 DV TLS CA 2025 Q4).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.