Merriam-Webster · Agent Readiness

Discoverability

Can agents find your site and its capabilities?

failWebMCP / agent-protocol tools discoveredAgent manifests

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.

passKey pages discoveredKey pages crawl

Crawled 12 of 12 discovered pages beyond the homepage.

infoLighthouse Agentic Browsing runLighthouse Agentic

Lighthouse Agentic Browsing audits ran.

infoWebsite platformplatform

Could not identify a known website platform (custom stack or unrecognised).

Understanding

Can agents understand your content?

failHTML readiness checks ranStructured data & HTML

Homepage returned 403 — couldn't analyse structure.

warnMarkdown content negotiationOpen agent protocols

Homepage returned 403 for Accept: text/markdown.

warnHomepage content is server-renderedCrawlability (Google)

Homepage returned 403.

warnKey pages have <title> and <h1>Key pages crawl

12 of 12 pages are missing <title> and/or <h1>: /sitemap-ssl/static.xml.gz, /sitemap-ssl/lexilicious-0.xml.gz, /sitemap-ssl/lexilicious-1.xml.gz, /sitemap-ssl/lexilicious-2.xml.gz, /sitemap-ssl/lexilicious-3.xml.gz, /sitemap-ssl/galleries.xml.gz, /sitemap-ssl/articles.xml.gz, /sitemap-ssl/quizzes.xml.gz, /sitemap-ssl/slang.xml.gz, /sitemap-ssl/video.xml.gz, /sitemap-ssl/az-0.xml.gz, /sitemap-ssl/az-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.

warnKey pages are server-renderedKey pages crawl

3 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /sitemap-ssl/static.xml.gz (14w), /sitemap-ssl/quizzes.xml.gz (57w), /sitemap-ssl/slang.xml.gz (74w).

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.

Operability

Can agents actually operate the page?

failWebMCP tools registered with the browserWebMCP tools

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.

warnOverall accessibility scoreAccessibility

Lighthouse accessibility score: 89/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.

warnCumulative Layout ShiftLighthouse Agentic

0.121

passAccessibility tree is agent-navigableAccessibility

All 12 agent-critical accessibility audits passed — an agent can perceive and operate the page through its accessibility tree.

pass`[aria-*]` attributes match their rolesAccessibility

`[aria-*]` attributes match their roles passed.

pass`[aria-hidden="true"]` is not present on the document `<body>`Accessibility

`[aria-hidden="true"]` is not present on the document `<body>` passed.

pass`[aria-hidden="true"]` elements do not contain focusable descendentsAccessibility

`[aria-hidden="true"]` elements do not contain focusable descendents passed.

pass`[role]`s have all required `[aria-*]` attributesAccessibility

`[role]`s have all required `[aria-*]` attributes passed.

pass`[role]` values are validAccessibility

`[role]` values are valid passed.

pass`[aria-*]` attributes are valid and not misspelledAccessibility

`[aria-*]` attributes are valid and not misspelled passed.

pass`[aria-*]` attributes have valid valuesAccessibility

`[aria-*]` attributes have valid values passed.

passButtons have an accessible nameAccessibility

Buttons have an accessible name passed.

passDocument has a `<title>` elementAccessibility

Document has a `<title>` element passed.

pass`<frame>` or `<iframe>` elements have a titleAccessibility

`<frame>` or `<iframe>` elements have a title passed.

passInput buttons have discernible text.Accessibility

Input buttons have discernible text. passed.

passLinks have a discernible nameAccessibility

Links have a discernible name passed.

passAccessibility tree is well-formedLighthouse Agentic

All audits passed

passCumulative Layout ShiftPerformance

0.010 (field data from CrUX) — good.

passTime to First BytePerformance

446ms (field data from CrUX) — good.

infoWebMCP form coverageLighthouse Agentic

4 forms missing annotations

infoWebMCP tools registeredLighthouse Agentic

Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.

infoTool catalog signpost publishedWebMCP tools

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.

Trust & Security

Can agents safely transact?

failHTTP Strict-Transport-Security headerSecurity & trust

No Strict-Transport-Security header on the homepage.

Fix: Add `Strict-Transport-Security: max-age=15768000; includeSubDomains` so browsers and agents refuse to downgrade to http for at least six months.

warnOAuth authorization server metadataOpen agent protocols

/.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.

warnOAuth protected-resource metadataOpen agent protocols

/.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.

warnWeb Bot Auth signature headerOpen agent protocols

Homepage returned 403.

warnHomepage shows no error outputSecurity & trust

Homepage returned 403 — couldn't scan for error markers.

warnNo mixed-content referencesSecurity & trust

Homepage returned 403 — couldn't scan for mixed content.

passCDN detectedSecurity & trust

cf-ray: a1ead6e29ccafea2-AMS (Cloudflare); Server: cloudflare

passContent-Security-Policy headerSecurity & trust

CSP header present.

passSite is served over HTTPSSecurity & trust

Homepage scheme is https:.

passhttp:// redirects to https://Security & trust

http://merriam-webster.com → https://www.merriam-webster.com/ (2 hops).

passReferrer-Policy headerSecurity & trust

Referrer-Policy: same-origin.

passTLS certificate is not near expirySecurity & trust

Valid for 162 more days (Dec 30 23:59:59 2026 GMT, issuer: Amazon RSA 2048 M04).

passNo tech-stack disclosure in headersSecurity & trust

Server / X-Powered-By headers don't leak product version.

passMIME-sniff protectionSecurity & trust

X-Content-Type-Options: nosniff.

passClick-jacking protectionSecurity & trust

X-Frame-Options: SAMEORIGIN.