Can agents find your site and its capabilities?
The site registers callable WebMCP tools with the browser at runtime, so an AI agent can operate the page through them.
Found a parseable Agent Skills index at https://monday.com/.well-known/agent-skills/index.json.
Found a parseable Linkset at https://monday.com/.well-known/api-catalog.
Found https://monday.com/llms.txt.
Found at least one "[name](url)" markdown link.
Found a "> summary" blockquote.
First line is a top-level "# Title" heading.
Crawled 12 of 12 discovered pages beyond the homepage.
Built on Webflow.
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 ~3591 elements — well above the 1500-element budget.
Fix: Trim the homepage DOM: an AI agent has to read all of it before acting, and this page is several times over budget. Long product carousels, hidden modal markup and large tracker scripts are common culprits.
Detected 1 heading level skip (e.g. h2 → h4).
Fix: Tighten the heading order so each level only steps down by one. Skipped levels confuse both screen-readers and AI structural extractors.
399 of 405 images have alt attributes (99%).
Fix: Add alt text to the remaining images. Empty alt="" is fine for purely-decorative graphics.
Only 60/405 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.
Missing landmark elements: main, footer.
Found 2 <h1> tags. Most AI summarisers expect exactly one.
Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.
7 of 12 pages are missing <title> and/or <h1>: /academy, /academy/view/certification/work-management-core-certification, /academy/view/lesson/admin-essentials, /academy/view/lesson/building-workflows, /academy/view/lesson/monday-ai-blocks, /academy/view/lesson/onboarding-essentials, /academy/view/lesson/work-management-product-demo.
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.
7 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /academy (9w), /academy/view/certification/work-management-core-certification (9w), /academy/view/lesson/admin-essentials (9w), /academy/view/lesson/building-workflows (9w), /academy/view/lesson/monday-ai-blocks (9w), /academy/view/lesson/onboarding-essentials (9w), /academy/view/lesson/work-management-product-demo (9w).
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 2279 words of visible text — content is reachable without executing JavaScript.
Language declared as "en".
194 internal links found.
Can agents actually operate the page?
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.
832ms (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 13 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]`s are contained by their required parent element 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: 95/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.
2/2 data-collecting forms mark required fields.
All 2 data-collecting forms include pattern/min/max constraints.
0.020 (field data from CrUX) — good.
1 tool(s) registered via the WebMCP browser API (navigator.modelContext).
All 1 registered tool(s) declare a name, description, and an object inputSchema.
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.
1: navigate_by_use_case
Can agents safely transact?
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-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.
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.
/.well-known/oauth-authorization-server returns parseable JSON.
/.well-known/oauth-protected-resource returns parseable JSON.
cf-ray: a1eab9407c2e66ce-AMS (Cloudflare); x-amz-cf-id: aOncNHAcrsb-Ki5Xu5a39_yUfQaoCE93EFf61I9J (AWS CloudFront); Server: cloudflare
max-age=31536000, includeSubDomains=true, preload=false.
Homepage scheme is https:.
http://monday.com → https://monday.com/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 148 more days (Dec 16 15:06:09 2026 GMT, issuer: Go Daddy Secure Certificate Authority - G2).
Server / X-Powered-By headers don't leak product version.