teamcity.jetbrains.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 <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 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.

no <link rel="canonical">

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

title is only 4 characters: 'Ring'

Fix: Expand the <title> to 10–70 characters naming the product and what it does.

no Open Graph tags

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

robots.txt does not reference a sitemap

Fix: Add `Sitemap: https://<domain>/sitemap.xml` to /robots.txt so crawlers find it without guessing.

served, but contains no <urlset> or <sitemapindex>

Fix: Make /sitemap.xml a valid sitemap: a <urlset> of <url><loc> entries, or a <sitemapindex> pointing at more sitemaps.

all 6 agent crawlers may fetch /

HTTP 200, 112 bytes

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

HTTP 401 for an agent User-Agent

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

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

browser got HTTP 200, agent User-Agent got HTTP 401

Fix: Your CDN or WAF is blocking non-browser clients. Allow well-identified bots, or at least return a 200 with readable content instead of a challenge page.

only 145 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.

https://hub.jetbrains.com/auth/login?response_type=code&client_id=2de7f1c3-b96c-46aa-9c89-04ed4b654489&redirect_uri=https%3A%2F%2Fteamcity.jetbrains.com%2FhubPlugin%2Flogin.html&scope=0-0-0-0-0%202de7f1c3-b96c-46aa-9c89-04ed4b654489&state=%2F&access_type=online

HTTP 200, 2800 bytes

HTTP 200, 2800 bytes

ratio 0.0732 (145 chars of 1981)

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.

/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

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.

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