percy.io

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 <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-in-one visual testing and review platform | Percy' (53 chars)

all 6 agent crawlers may fetch /

HTTP 200, 139 bytes

robots.txt has a Sitemap: line

11 URL(s) listed

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

/docs returns only 0 characters of readable text

Fix: Server-render your documentation. Docs behind a client-side renderer are invisible to every agent that reads them, which is the whole audience for docs.

/llms.txt returns HTML, not markdown

Fix: Serve /llms.txt as text/plain or text/markdown. An HTML error page at this path is worse than a 404: it looks like content.

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.txt contains no resolvable links

Fix: Add markdown links to your actual docs pages — a description with no links leaves the agent where it started.

Accept: text/markdown → text/html

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

ratio 0.0 — 0 readable chars in 17428 bytes of HTML

Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.

HTTP 200 for / (agent UA)

https://percy.io/

HTTP 200, 17428 bytes

HTTP 200, 17428 bytes

both User-Agents got HTTP 200

0 redirect(s)

/openapi.json is served but is not valid JSON

Fix: Serve a parseable OpenAPI document at /openapi.json. What is there now cannot be read by any tooling.

/.well-known/mcp.json is served but is not valid JSON

Fix: Fix the JSON at /.well-known/mcp.json — as served it cannot be parsed, so the advertisement does nothing.

/agents.md returns HTML

Fix: Serve /agents.md as markdown (text/markdown or text/plain). An HTML page here is probably your SPA catch-all route.

a nonexistent path returned HTTP 200, not 404

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

/docs → HTTP 200

/api → HTTP 404 (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

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

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

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