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

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://suno.com/

165 characters

'Suno | AI Music Generator' (25 chars)

og:title and og:description present

all 6 agent crawlers may fetch /

HTTP 200, 335 bytes

robots.txt has a Sitemap: line

18 URL(s) listed

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

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.

no markdown links

Fix: Structure /llms.txt as markdown: an `# H1` naming the product, then `## Sections` of `[title](url): description` links.

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.0277 — 6095 readable chars in 219899 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://suno.com/

4 valid block(s) (WebSite, Organization, SoftwareApplication)

HTTP 200, 11840 bytes

both User-Agents got HTTP 200

6095 characters of text in the served HTML

0 redirect(s)

/agents.md not served (HTTP 404)

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.

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

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

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.

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