Anker

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.

Per llmstxt.org, follow the H1 with a "> short summary" blockquote.

Fix: Add a "> One-sentence description of your site." blockquote under the H1.

Found a Markdown guide at /AGENTS.md.

Found https://anker.com/llms.txt.

Found at least one "[name](url)" markdown link.

First line is a top-level "# Title" heading.

Crawled 12 of 12 discovered pages beyond the homepage.

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.

Lighthouse Agentic Browsing audits ran.

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

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 ~1877 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.

79 of 86 images have alt attributes (92%).

Fix: Add alt text to the remaining images. Empty alt="" is fine for purely-decorative graphics.

Only 0/86 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.

Only 4 internal links on the homepage.

Fix: Add at least 5-10 internal links pointing to your top product, pricing, docs, blog and about pages so an AI agent can navigate to them from the homepage.

Found 2 <h1> tags. Most AI summarisers expect exactly one.

Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.

11 of 12 pages are missing <title> and/or <h1>: /blogs, /news, /story, /uk/blogs, /ca/blogs, /eu-de/blogs, /eu-en/blogs, /fr/blogs, /au/blogs, /ca-fr/blogs, /eu-pl/blogs.

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 1388 words of visible text — content is reachable without executing JavaScript.

Detected 1 cookie-banner element but none look agent-hostile (small, dismissible, or offer a reject option).

Language declared as "en-US".

All four landmark elements present (main, header, footer, nav).

All 12 pages return ≥80 words of visible text without JavaScript.

4 of 14 agent-critical accessibility audits failed (Buttons do not have an accessible name, Links do not have a discernible name, `<frame>` or `<iframe>` elements do not have a title, `[aria-*]` attributes do not have valid values) — 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 flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Fix invalid values on aria-* attributes.

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.

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Add a title to every <iframe> so agents can identify embedded content.

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Give every link discernible text (avoid bare icons / "click here") so agents know where it goes.

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.

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

Uses ARIA roles only on compatible elements 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.

Document has a `<title>` element passed.

1 of 1 visible interactive form fields have labels.

0

0.000 (field data from CrUX) — good.

568ms (field data from CrUX) — good.

1 form missing annotations

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.

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

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.

HSTS configured (max-age=31536000) but missing includeSubDomains.

Fix: Add `includeSubDomains` so subdomains inherit the policy.

CSP header present.

Homepage scheme is https:.

http://anker.com → https://www.anker.com/ (2 hops).

No stack-trace markers in the first 5KB.

Homepage HTML references no http:// resources.

Referrer-Policy: origin-when-cross-origin.

Valid for 35 more days (Aug 26 11:13:55 2026 GMT, issuer: E8).

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

X-Content-Type-Options: nosniff.

X-Frame-Options: ALLOW-FROM https://payload.anker-in.com.

Found the human-approval-for-checkout rule.

Content-Type: text/markdown; charset=UTF-8.

Mentions the store ("anker") — looks customised beyond the default.

References UCP / a UCP version or /.well-known/ucp.

No secret/token or admin-path references found.

Found at https://anker.com/agents.md.

References the UCP MCP endpoint (/api/ucp/mcp).

Manifest parses as JSON.

Manifest reachable at https://anker.com/.well-known/ucp.

Services: dev.ucp.shopping.

Transports: mcp, embedded.