Static pre-check · Fri, 07 Aug 2026 06:49:16 GMT
perplexity.ai
AI agents struggle with dynamic JavaScript rendering and lack of structured metadata, unable to parse content or discover resources without machine-readable guidelines.
Watch a real agent use your site →
A live Claude Code run against perplexity.ai, streamed step by step.
Test this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
Discovery 15.3/22.2
Homepage has a meta descriptiondetailsFAIL
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".
Homepage has a descriptive titledetailsFAIL
no <title> element on the homepage
Fix: Add a <title> of 10–70 characters naming the product and what it does — it is the first thing an agent reads to decide what this site is.
Canonical URL declareddetailsWARN
no <link rel="canonical">
Fix: Add <link rel="canonical"> to the homepage so agents and crawlers converge on one URL for this page.
Open Graph tags presentdetailsWARN
no Open Graph tags
Fix: Add og:title and og:description meta tags.
robots.txt allows agent crawlersdetailsPASS
all 6 agent crawlers may fetch /
robots.txt existsdetailsPASS
HTTP 200, 480 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
7 URL(s) listed
API reference linked from the homepagedetailsN/A
no homepage links to inspect
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Documentation linked from the homepagedetailsN/A
no homepage links to inspect (see the accessibility checks — the homepage produced no parseable navigation)
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed
Accessibility 12.5/33.3
Homepage responds to an agent requestdetailsFAIL
HTTP 403 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 is publisheddetailsFAIL
/llms.txt not served (HTTP 403)
Fix: Publish /llms.txt: a plain-markdown index that tells an agent what this product is and where the authoritative docs live. It is the cheapest high-leverage file you can add.
Homepage has readable text without JavaScriptdetailsFAIL
only 0 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.
Structured data (JSON-LD) on the homepagedetailsWARN
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 is publisheddetailsWARN
/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.
Serves markdown when asked for itdetailsWARN
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.
Served over HTTPSdetailsPASS
https://www.perplexity.ai/
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 403
No long redirect chain on the homepagedetailsPASS
1 redirect(s)
Docs are readable without JavaScriptdetailsN/A
/docs not served (HTTP 403) — docs may live on another path or host
Links in llms.txt resolvedetailsN/A
no llms.txt
llms.txt is structured markdowndetailsN/A
no llms.txt to parse
Content-to-markup ratio is reasonabledetailsN/A
no homepage HTML to measure
Usability 22.2/44.4
agents.md is publisheddetailsWARN
/agents.md not served (HTTP 403)
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.
A documentation endpoint respondsdetailsWARN
/docs → HTTP 403
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
Errors are machine-readabledetailsWARN
a nonexistent path returned HTTP 403, 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 document publisheddetailsWARN
/openapi.json not served (HTTP 403)
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 advertises an MCP serverdetailsWARN
/.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.
The /api root behaves predictablydetailsN/A
/api → HTTP 403 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document
Payments not applicable — excluded from the score
Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/perplexity.ai)<a href="/score/perplexity.ai"><img src="/api/badge/perplexity.ai" alt="agent readiness score" /></a>