Can agents find your site and its capabilities?
Crawled 12 of 12 discovered pages beyond the homepage.
Lighthouse Agentic Browsing audits ran.
Built on WordPress.
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 ~2077 elements — heavy.
Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.
Detected 2 heading level skips (e.g. h1 → h3).
Fix: Tighten the heading order so each level only steps down by one. Skipped levels confuse both screen-readers and AI structural extractors.
Missing landmark elements: main.
1 of 12 pages are missing <title> and/or <h1>: /column/the-cost-of-caregiving.
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 1448 words of visible text — content is reachable without executing JavaScript.
Language declared as "en-US".
25 of 25 <img> tags have alt attributes.
25/25 images set width and height — no layout shift.
27 internal links found.
Exactly one <h1> on the homepage.
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.
0.428
All 3 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.
Document has a `<title>` element passed.
`<frame>` or `<iframe>` elements have a title passed.
Lighthouse accessibility score: 94/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
1 of 1 visible interactive form fields have labels.
0.040 (field data from CrUX) — good.
301ms (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?
Found 1 http:// reference in the homepage HTML — browsers will block these resources.
Fix: Update every http:// resource URL to https:// (or use protocol-relative `//`). Common offenders: image CDNs and legacy embed snippets.
/.well-known/oauth-authorization-server returned 403.
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 502.
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 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.
x-amz-cf-id: 1jt0QQ83lsJ9tPkjVnfjTnKGzjMloV7Wdn-CfDZV (AWS CloudFront)
max-age=63072000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://marketwatch.com → https://www.marketwatch.com/ (1 hop).
No stack-trace markers in the first 5KB.
Referrer-Policy: strict-origin-when-cross-origin.
Valid for 216 more days (Feb 22 23:59:59 2027 GMT, issuer: Amazon RSA 2048 M04).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.