coinbase.com

no <meta name="description">

Fix: Add a <meta name="description"> of 50–200 characters summarising what the product does. Agents use it as the one-line answer to "what is this site".

no <title> element on the homepage

Fix: Add a <title> of 10–70 characters naming the product and what it does — it is the first thing an agent reads to decide what this site is.

sitemap.xml not served (HTTP 403)

Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.

no <link rel="canonical">

Fix: Add <link rel="canonical"> to the homepage so agents and crawlers converge on one URL for this page.

no Open Graph tags

Fix: Add og:title and og:description meta tags.

all 6 agent crawlers may fetch /

HTTP 200, 3282 bytes

robots.txt has a Sitemap: line

no homepage links to inspect

search-based checks are deferred — excluded from the score

no homepage links to inspect (see the accessibility checks — the homepage produced no parseable navigation)

registry lookup not implemented in v1 — excluded from the score rather than guessed

HTTP 403 for an agent User-Agent

Fix: Return 200 for agent requests to the homepage. A non-2xx here means nothing downstream can be evaluated.

only 0 characters of readable text in the served HTML

Fix: Server-render the homepage's core content (SSR, static export, or prerendering). A client-rendered shell is empty to every agent.

no JSON-LD blocks on the homepage

Fix: Add a JSON-LD block (schema.org Organization or SoftwareApplication) so agents get your name, description and links as data rather than prose.

/llms-full.txt not served

Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.

Accept: text/markdown → text/html; charset=UTF-8

Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.

https://www.coinbase.com/

HTTP 200, 5070 bytes

5 sampled link(s) all resolve

has headings and markdown links

both User-Agents got HTTP 403

1 redirect(s)

/docs not served (HTTP 403) — docs may live on another path or host

no homepage HTML to measure

/agents.md not served (HTTP 403)

Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.

/docs → HTTP 403

Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.

a nonexistent path returned HTTP 403, not 404

Fix: Return 404 for paths that do not exist. A 200 on a missing page makes an agent believe it found something.

/openapi.json not served (HTTP 403)

Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.

/.well-known/mcp.json not served (HTTP 404)

Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.

/api → HTTP 403 (no API at the conventional root)

no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)

no listed MCP tools to inspect

no listed MCP tools to inspect

no MCP endpoint to probe

no parseable OpenAPI document

no parseable OpenAPI document

no parseable OpenAPI document

no parseable OpenAPI document

x402 is declared but no probed endpoint answered HTTP 402

Fix: Your documents advertise x402 but the endpoints do not issue a 402 challenge. Return 402 with the challenge on metered endpoints, or drop the claim.

x402 referenced in a published document (x402)

no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.