agentspeed.

example.com

scanned 7/20/2026, 7:17:52 PM · fresh · rubric 2026.07.1
↻ Rescan
robots.txt present: failrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: warnSitemap present: failLink response headers: failCanonical URL: failMCP server card: failOAuth authorization metadata: failOAuth resource metadata: failAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: failText-to-markup ratio: passContent without JavaScript: skipHeading hierarchy: passCookie wall blocks content: passPage title: passMeta description: failJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: passAgent Skills manifest: failWebMCP actions: failPrimary action reachable: failReachability: passTime to first byte: passFull render time: skipPage weight: pass52/ 100 · F
At risk

This is how AI agents (not browsers) experience example.com. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

Discoverability
20
Readability
67
Structured data
33
Actionability
50
Performance
100

✉ Email me this report + alert me when it changes ↓

Top fixes

failSitemap presentDiscoverability

No reachable sitemap.xml. Publish one and reference it in robots.txt.

Fix: Publish /sitemap.xml and reference it from robots.txt with a Sitemap: line.

failCanonical URLDiscoverability

No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.

Fix: Add <link rel="canonical" href="…"> pointing at the primary URL of each page.

failMeta descriptionReadability

No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.

Fix: Add `<meta name="description" content="...">` to your primary pages. Agents frequently use it as a summary.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

failPrimary action reachableActionability

Page text too sparse to probe; agent has nothing to read.

Fix: If agents cannot identify what you sell within 3 steps, your primary-offer page is under-structured. Add a visible headline, price (or "contact us"), and canonical CTA.

failrobots.txt presentDiscoverability

No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.

Fix: Add a `/robots.txt` file at the site root. Even an allow-all file signals intent to agents.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever example.com’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt
Publish this at https://example.com/llms.txt
# Example Domain

> What example.com offers, in one or two sentences an AI agent can quote.

## Key pages
- [Home](https://example.com/)
- [Example Domain](https://example.com/)

## About
Describe what example.com does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view
Example Domain Example Domain This domain is for use in documentation examples without needing permission. Avoid use in operations. Learn more

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

AgentSpeed score for example.com
<a href="https://agentspeed.com/scan/example.com"><img src="https://agentspeed.com/badge/example.com" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email and a heads-up when example.com’s agent-readiness changes.

Full breakdown

10 pass1 warn16 fail3 skip
Discoverability
fail
robots.txt present
No reachable robots.txt at the site root. Publish one so agents can discover your crawl policy and sitemap.
0/100
pass
robots.txt allows AI agents
All 9 known agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
warn
llms.txt present
Found /llms.txt but missing H1 header and markdown links.
60/100
fail
Sitemap present
No reachable sitemap.xml. Publish one and reference it in robots.txt.
0/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
fail
Canonical URL
No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.
0/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
pass
Text-to-markup ratio
Visible text is 25.4% of HTML weight (142/559 bytes). Healthy.
100/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
—
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 1 headings total).
100/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
pass
Page title
A concise <title> is present (14 chars).
100/100
fail
Meta description
No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.
0/100
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
—
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
fail
Primary action reachable
Page text too sparse to probe; agent has nothing to read.
0/100
pass
Reachability
HTTP 200.
100/100
Performance
pass
Time to first byte
TTFB 33ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 1 KB.
100/100
Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans