gumroad.com

no link to documentation found in the homepage HTML

Fix: Link your docs from the homepage with visible anchor text ("Docs", "Documentation", "Developers"). An agent that cannot find your docs from your homepage will guess your API.

sitemap.xml not served (HTTP 404)

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

no link to an API reference in the homepage HTML

Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.

https://gumroad.com/about

81 characters

'Earn your first dollar online with Gumroad' (42 chars)

og:title and og:description present

all 6 agent crawlers may fetch /

HTTP 200, 31687 bytes

robots.txt has a Sitemap: line

search-based checks are deferred — excluded from the score

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.

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.

ratio 0.0322 — 4143 readable chars in 128634 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://gumroad.com/

HTTP 200, 1832 bytes

5 sampled link(s) all resolve

has headings and markdown links

both User-Agents got HTTP 200

4143 characters of text in the served HTML

0 redirect(s)

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

/api → HTTP 200 text/html; charset=utf-8

Fix: Serve JSON from API paths, with an accurate content-type.

404 returns HTML, not a machine-readable body

Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.

/openapi.json not served (HTTP 404)

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.

/docs → HTTP 200

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.