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.
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.
Found https://teamwork.com/llms.txt.
Found a "> summary" blockquote.
First line is a top-level "# Title" heading.
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 ~1628 elements — heavy.
Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.
Missing landmark elements: main, header.
Homepage server response contains 3739 words of visible text — content is reachable without executing JavaScript.
Detected 4 cookie-banner elements but none look agent-hostile (small, dismissible, or offer a reject option).
29 headings, no level skips.
Language declared as "en".
102 of 102 <img> tags have alt attributes.
102/102 images set width and height — no layout shift.
180 internal links found.
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?
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.
14 of 15 visible interactive form fields have labels.
Fix: Associate every input with a label — either wrap it in <label>, link via for/id, or set aria-label / aria-labelledby.
All 12 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.
`[aria-*]` attributes match their roles passed.
Uses ARIA roles only on compatible elements 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.
`[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.
0
0.040 (field data from CrUX) — good.
746ms (field data from CrUX) — good.
Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.
10 tool(s) published at /.well-known/webmcp.json. The catalog is a community convention signpost, not part of the WebMCP standard.
10: twprojects-list_projects, twprojects-create_task, twprojects-list_tasks, twprojects-create_timelog, twprojects-search, twdesk-search_tickets, twdesk-create_ticket, twdesk-reply_ticket, twspaces-search, twspaces-create_page
All 10 tool(s) declare a name and description.
Can agents safely transact?
/.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 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.
/.well-known/oauth-authorization-server returns parseable JSON.
x-amz-cf-id: 8NRoWOLrTA5U543-hqSt3UmuIQGh11V0NG_tPDBR (AWS CloudFront)
CSP header present.
max-age=31536000, includeSubDomains=true, preload=false.
Homepage scheme is https:.
http://teamwork.com → https://www.teamwork.com/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 87 more days (Oct 16 23:59:59 2026 GMT, issuer: Amazon RSA 2048 M01).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
CSP frame-ancestors directive present.