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.
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 returned 403 — couldn't analyse structure.
Homepage returned 403 for Accept: text/markdown.
Homepage returned 403.
12 of 12 pages are missing <title> and/or <h1>: /chuchumama-baby-diaper-pants-l-9-14-kg-pack-of-1-50-pieces-anti-lock-gel-technology-upto-12-hours-protection/p/1izwjr, /madhubani-print-saree/p/1nnri7, /frc-decor-fridge-cover-combo-pack-multicolor/p/1jmqai, /pthouse_very-cute-and-soft-yellow-unicorn/p/1jkmfv, /nutri-fast-general-health-tonic-natural-multi-vitamin-good-health-capsule-complete-family-super-health-ever-health-perfect-health-wellness-tonic-for-general-weakness-liver-digestive-disorder-gastric-acidity-anemia-natural-source-of-vitamin-calcium-minerals-pack-of-4-100-capsule-900-ml/p/1nw6wi, /velvet-cushion-cover-pack-of-2/p/1jmq9t, /mi-redmi-9a/p/1qjcyb, /dakshya-industries-waterproof-semi-automatic-washing-machine-cover-biege/p/1iw1gr, /cover2sell-vintage-leather-flip-cover-for-redmi-9i-redmi-9a-attractive-dark-blue/p/1ieu0b, /feeding-zip-maternity-dress-yellow/p/1jgeqe, /soni-jewellery-single-line-18-inch-red-beads-mangalsutra/p/1ncvl9, /snowpearl-double-sided-fruit-melon-ba
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.
12 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /chuchumama-baby-diaper-pants-l-9-14-kg-pack-of-1-50-pieces-anti-lock-gel-technology-upto-12-hours-protection/p/1izwjr (5w), /madhubani-print-saree/p/1nnri7 (5w), /frc-decor-fridge-cover-combo-pack-multicolor/p/1jmqai (5w), /pthouse_very-cute-and-soft-yellow-unicorn/p/1jkmfv (5w), /nutri-fast-general-health-tonic-natural-multi-vitamin-good-health-capsule-complete-family-super-health-ever-health-perfect-health-wellness-tonic-for-general-weakness-liver-digestive-disorder-gastric-acidity-anemia-natural-source-of-vitamin-calcium-minerals-pack-of-4-100-capsule-900-ml/p/1nw6wi (5w), /velvet-cushion-cover-pack-of-2/p/1jmq9t (5w), /mi-redmi-9a/p/1qjcyb (5w), /dakshya-industries-waterproof-semi-automatic-washing-machine-cover-biege/p/1iw1gr (5w), /cover2sell-vintage-leather-flip-cover-for-redmi-9i-redmi-9a-attractive-dark-blue/p/1ieu0b (5w), /feeding-zip-maternity-dress-yellow/p/1jgeqe (5w), /soni-jew
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.
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.
0.420 (field data from CrUX) — poor.
Fix: A layout that shifts while loading makes an AI agent mis-click the element it targeted. Eliminate CLS by setting explicit width/height on images and embeds, avoiding inserted content above existing content, and reserving space for ad slots.
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 9 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).
Lighthouse accessibility score: 78/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.
Fix: Resolve the failing accessibility audits below — each one removes an element or relationship an agent would otherwise be blind to.
`[aria-*]` attributes match their roles passed.
`[aria-hidden="true"]` is not present on the document `<body>` 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.
All audits passed
0
273ms (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.
Homepage returned 403.
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.
HSTS max-age=86400 is below six months.
Fix: Raise max-age to at least 15768000 (six months). The HSTS preload list requires 31536000 (one year).
Homepage returned 403 — couldn't scan for error markers.
Homepage returned 403 — couldn't scan for mixed content.
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.
Homepage scheme is https:.
http://meesho.com → https://www.meesho.com/ (1 hop).
Valid for 63 more days (Sep 23 01:22:07 2026 GMT, issuer: WR3).
Server / X-Powered-By headers don't leak product version.