Fix every AgentSpeed check.

Missing llms.txt

Your site has no /llms.txt file, so AI agents have to guess which pages matter most.

GPTBot is blocked by your robots.txt

OpenAI's crawler is disallowed, so ChatGPT cannot read your pages or cite them in answers.

Missing structured data (JSON-LD)

Your pages have no JSON-LD, so agents must guess what each page is about.

Missing XML sitemap

No /sitemap.xml means agents and search engines must discover every page through link-following alone.

Primary content requires JavaScript

Your main content is rendered by JavaScript, so most agents see an empty page.

Weak title and meta description

Your <title> and meta description are missing, generic, or duplicated, so agents can't tell what each page is about at a glance.

Poor heading structure

No H1, multiple H1s, or skipped levels, so agents can't build an outline of your page.

Slow server response (high TTFB)

Your server takes too long to return the first byte, so agents time out before reading your page.

ClaudeBot is blocked by your robots.txt

Anthropic's crawler is disallowed, so Claude cannot read your pages or cite them in answers.

Unclear primary call-to-action

Agents can't tell what action your page wants users to take, so they don't recommend it for buying or signup queries.

A reachable robots.txt exists at the site root.

robots.txt does not disallow well-known agent user-agents (GPTBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Applebot-Extended).

robots.txt advertises Content-Signal directives (e.g. `Content-Signal: ai-train=no, ai-summarize=yes`) that let agents respect granular usage preferences.

An llms.txt file at the site root helps agents locate your most-important content.

A sitemap.xml is reachable and referenced from robots.txt.

HTTP `Link:` response headers carry useful relations (canonical, alternate, describedby) that agents consume without parsing HTML.

A canonical URL is declared and resolves to the same page.

An MCP Server Card is reachable at `/.well-known/mcp/server-card.json` (or referenced from a Link header) and validates against the Model Context Protocol spec.

`/.well-known/oauth-authorization-server` is reachable and conforms to RFC 8414, letting agents discover authorization endpoints without out-of-band setup.

`/.well-known/oauth-protected-resource` is published per RFC 9728 so agents can discover required scopes and authorization servers programmatically.

An API catalog is published at `/.well-known/api-catalog` (RFC 9727) or an OpenAPI document is reachable at `/openapi.json` or `/openapi.yaml`.

The site signals support for the Web Bot Auth IETF draft (HTTP Message Signatures over a known JWKS) so well-behaved agents can prove identity.

Requests with `Accept: text/markdown` return a markdown representation of the page (Markdown content negotiation).

Visible text makes up at least 15% of the rendered DOM weight.

Primary content is visible without JavaScript.

Heading hierarchy is well-formed (one H1, no skipped levels).

A cookie-consent modal does not cover or block the primary content on first load.

A non-empty <title> is present and under 70 characters.

A meta description is present and between 50 and 200 characters.

At least one valid JSON-LD block is present.

JSON-LD validates against the declared schema.org type.

Declared JSON-LD types cover the apparent page purpose (e.g. a product page has Product, a blog post has Article).

Landing URL is not gated by a login or paywall.

A read-only LLM-driven probe can identify the primary offering and either its price or its primary call-to-action.

Landing URL returns a 2xx after at most one redirect.

An Agent Skills manifest is reachable (e.g. `/.well-known/agent-skills.json`) describing discrete tasks an agent can perform on the site.

The page exposes WebMCP (in-browser Model Context Protocol) so on-page agents can invoke tools without leaving the tab.

Time-to-first-byte is under 800ms from a US-East origin.

Full render (network idle) completes under 4 seconds.

Total page weight is under 3 MB.