Perplexity

perplexity.ai

Agent score

Not scored

Our checks were blocked.

RankRank: 550 scoredNot ranked among 550 scored domains; None
SaaS rankSaaS rank: Avg 74.5Sector average 74.5; None
Benchmark runsBenchmark runs: 3 providersAcross 3 providers; 5

Latest results

Perplexity has no score right now.

Agent friction28improvements10 high severity. Most serious: Homepage did not return 2xx (status 403) to a standard client.Technical readiness52/1005 of 8 essential checks failing.Checks by Is Agentic

Our checks were blocked, so perplexity.ai is not scored

perplexity.ai turned our requests away. Sites that block automated requests often block agents too, but a blocked request alone is not a score. perplexity.ai stays out of rankings and averages until our checks or an agent get through.

Own perplexity.ai? Claim it to request a re-run.

Potential improvements

Where agents got stuck, most serious first.

HighInformation retrieval

Homepage did not return 2xx (status 403) to a standard client.

Where agents get stuck

28 improvements from the latest run, 10 of them high severity.

High: 10
Medium: 10
Low: 8

HighInformation retrieval
Homepage did not return 2xx (status 403) to a standard client.
HighInformation retrieval
Homepage ships little text to server-rendered HTML. Agents without a browser see an empty shell.
HighAccuracy
Brand name not present in server-rendered HTML. Non-JS agents may not associate the domain with the product.

25 more, and the evidence for each

Where agents get stuck

HighInformation retrieval

Homepage did not return 2xx (status 403) to a standard client.

HighInformation retrieval

Homepage ships little text to server-rendered HTML. Agents without a browser see an empty shell.

HighAccuracy

Brand name not present in server-rendered HTML. Non-JS agents may not associate the domain with the product.

HighTask completion

Homepage returns a bot-challenge / CAPTCHA. Agents can’t complete a task if they can’t load the site.

HTTP 403 + cf-mitigated: challenge

HighDelegated access

No discoverable MCP server. Agents and AI clients have no way to discover one automatically.

HighDelegated access

No discoverable public API docs. Agents and AI clients have no way to discover them automatically.

HighContact & communication

No contact page linked or reachable. Agents acting on a user’s behalf have nowhere to send a message.

HighTask completion

Claude hits a bot-challenge page on the homepage.

HighTask completion

ChatGPT Agent hits a bot-challenge page on the homepage.

HighTask completion

Gemini hits a bot-challenge page on the homepage.

MediumBrand awareness

No Organization JSON-LD. Agents can’t tell who owns the site at a glance.

MediumBrand awareness

Homepage meta description is missing or too short for agent snippets.

MediumInformation retrieval

No JSON-LD structured data. Agents must infer entities from markup.

MediumMarket ranking

No Product/Service schema on the homepage. Agents can’t easily compare offerings.

MediumMarket ranking

Pricing only available if JavaScript is enabled. Agents may report "pricing not disclosed".

MediumAccuracy

No JSON-LD at all. Every factual claim must be inferred from prose.

MediumTask completion

No visible primary call-to-action in the server-rendered HTML. Agents have nothing concrete to click on behalf of a user.

MediumTask completion

The homepage has no link an agent can follow to start a task (pricing, sign-up, cart, booking). Links rendered only by JavaScript are invisible to agents that read the HTML.

MediumTask completion

No mention of delegated auth primitives (passkey, OAuth, MCP). Agents must drive a full browser session.

MediumContact & communication

No contact email visible in server-rendered HTML. Agents can’t fall back to email.

LowBrand awareness

Missing Open Graph tags. Link previews degrade in agent chats.

LowBrand awareness

Fewer than two social profiles linked. Agents struggle to triangulate the brand.

LowDiscovery

No canonical URL. Agents may conflate duplicate pages as separate entities.

LowMarket ranking

No review or aggregateRating schema. Agents have no signal for ranking vs peers.

LowAccuracy

No canonical URL. Agents may cite ephemeral query-string variants.

LowAccuracy

No privacy policy linked from the homepage. Agents can’t cite policy when asked.

LowTask completion

No detectable agentic-commerce rail (Stripe SPT, Shopify/UCP, PayPal ACP). Agent-initiated payment needs custom work.

LowContact & communication

No help, support, or FAQ hub linked. Agents can’t self-serve an answer before reaching out.

Want to find these in your own flows before an agent does? Read how to test your product for AI agent users.

Technical readiness

5 of 8 essential checks fail. These are the files and signals agents read before they act.

Checks by Is Agentic

Score

52/ 100

Important blockers remain

Essential: 3 of 8 pass
Recommended: 10 of 19 pass
Bonus: +4.4 from 20 positive signals

Investigate

Content without JavaScriptessential

Investigate

Not blocked by bot detectionessential

Investigate

JSON error responsesessential

27 checks · scanned 24 Aug 2026

Technical readiness

Protocol baseline by Is Agentic

Score: 52/ 100; Important blockers remain
Essential: 34/ 80; 3 of 8 passing
Recommended: 13.9/ 20; 10 of 19 passing
Bonus: +4.4; 20 positive signals

Investigate

Content without JavaScriptessential

Homepage blocked by WAF/security challenge - content not accessible to agents

Fix: Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

Investigate

Not blocked by bot detectionessential

Agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended

Fix: Verify that major agent User-Agents can reach the homepage. If your WAF or bot rules block them, remove or narrow the blocking rule. Add an allow rule only when your security setup denies them by default.

Investigate

JSON error responsesessential

API does not return JSON error responses (or no API detected)

Fix: Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.

Investigate

Markdown content negotiation (acceptmarkdown.com)essential

Not acceptmarkdown.com compliant: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "none")

Fix: On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.

Investigate

Trust anchor pagesrecommended

No trust anchor pages found with sufficient content (About, Contact, Privacy)

Fix: Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.

Investigate

Rate limit response headersrecommended

GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages

Fix: Return standard rate-limit headers on your API responses (the RFC RateLimit headers, plus Retry-After on a 429) so agents can self-throttle in real time, and document the conventions alongside your API.

Investigate

API schema complexity analysisrecommended

GraphQL: introspection auth-gated and no schema evidence in docs

Fix: Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.

Investigate

Function calling compatibilityrecommended

No API spec found - function calling requires discoverable endpoints

Fix: Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.

Partial

Scoped permissionsessential

Scoped permissions described at https://docs.perplexity.ai, but no machine-readable scope declaration found (OpenAPI oauth2 scopes or RFC 9728 scopes_supported)

Fix: Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.

Partial

Organization schema completenessrecommended

Organization schema found but missing: contactPoint, address

Fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.

Partial

Agent onboarding frictionrecommended

Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment

Fix: Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.

Partial

Agent instruction / when-to-userecommended

When-to-use guidance found at https://docs.perplexity.ai

Fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases and how an agent should call you. Be specific about the jobs you are right for - generic marketing copy does not read as guidance.

Partial

JSON-LD structured datarecommended

JSON-LD Organization with name + description - add url and sameAs/logo/address for full score

Fix: Add JSON-LD structured data to your homepage using the identity type that matches your site - SoftwareApplication for products, Organization or LocalBusiness for companies, Person for personal sites, Article for blogs - with name, description, url, and type-appropriate fields (offers, sameAs, author) so AI can parse your identity programmatically.

Partial

MCP server / manifestrecommended

First-party MCP server published by product org (npm, @perplexity-ai/mcp-server, 12227 score). Add live handshake at /.well-known/mcp for full credit.

Fix: Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.

27 checks · scanned 24 Aug 2026

Badge

Show visitors you take AI agents seriously

Add a live Index badge to your footer, docs or README. The badge updates after every run and links visitors to this scorecard.

Ask your agent about perplexity.ai

Add the Index to Claude, ChatGPT or Cursor as an MCP connector to look up any score, frictions and agent sessions. No account needed.

https://app.stuntdouble.io/api/mcp/index

Setup for your client

Discover more insights with Stunt Double

Send AI agents through perplexity.ai on your own tasks.

Try Stunt Double