Mostly invisible to buyers and agents

50/ 100

D
Grade: 23
Agent readiness
Board average 73 Scanned 2 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does perplexity.ai do and how do I use it? A fetch-only agent finds out.

12 fetches5 found7 missing

⋯home

/robots.txt⋯/sitemap.xml
/llms.txt⋯/llms-full.txt
/pricing
/docs
/openapi.json
mcp.json⋯MCP initialize
/privacy · /terms

⋯404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached perplexity.ai over HTTPS in 64 ms and identified it from its title as “Perplexity”. Little of the page survives without JavaScript, so a fetch-only agent sees mostly an empty shell. It looked for pricing, docs, an OpenAPI spec and an MCP server and found none.

Critical access needs attention

Whether an ordinary agent can enter, read, and operate the public site.

✓
Agents can reach the site
Crawler access and bot defenses.
4 / 4 passed
~
Core content is available
Useful content remains accessible without a fragile browser-only path.
0 / 2 passed
✓
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
2 / 2 passed
✓
Controls are understandable
Forms and interactive controls expose usable names and structure.
1 / 1 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

01
Clear call to actionConverts
Put one primary CTA (Get started, Start free, Book a demo) above the fold.
+8 pts
02
OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts
03
Pricing page linkedConverts
Link a pricing page from the homepage; buyers look for it first.
+6 pts
04
Analytics installedMeasured
Install analytics (PostHog, Plausible, GA4) before spending on traffic.
+6 pts
05
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable5 of 5 passed · 19/19 pts›

✓Served over HTTPS5/5
https://www.perplexity.ai/
✓Responds in under 1.5s5/5
64 ms to first byte
✓robots.txt present2/2
# https://www.robotstxt.org/robotstxt.html User-agent: * Disallow: /*?*q= Disall…
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata6 of 7 passed · 20/24 pts›

✓Title tag 10–70 characters5/5
"Perplexity" (10)
✓Meta description 50–160 characters5/5
"Perplexity is a free AI-powered answer engine that provides accurate, trusted, and real-time answers…" (117)
✓Canonical URL set3/3
https://www.perplexity.ai
✕Exactly one H10/4
no <h1>
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width,initial-scale=1
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
/favicon.svg

Shareable2 of 3 passed · 11/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✓Twitter/X card type set3/3
twitter:card = summary_large_image
✕Links to X or LinkedIn0/3
no X / LinkedIn links found
→ Link your X and LinkedIn so visitors can follow and verify you.

Converts1 of 3 passed · 3/17 pts›

✕Clear call to action0/8
no sign-up / get-started / demo CTA found
→ Put one primary CTA (Get started, Start free, Book a demo) above the fold.
✕Pricing page linked0/6
no /pricing link
→ Link a pricing page from the homepage; buyers look for it first.
✓HTML under 2 MB3/3
16 KB of HTML

Measured0 of 1 passed · 0/6 pts›

✕Analytics installed0/6
no analytics tag detected
→ Install analytics (PostHog, Plausible, GA4) before spending on traffic.

Agent-ready5 of 18 passed · 10/44 pts›

✕Structured data (JSON-LD)0/4
no JSON-LD
→ Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
✕Machine-readable pricing0/3
no /pricing page and no Offer JSON-LD
→ Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.
✕llms.txt present0/1
no /llms.txt
→ Publish /llms.txt: a short markdown summary of the product, pricing and docs links for AI agents.
✕llms-full.txt present0/1
no /llms-full.txt
→ Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
✓No noai / TDM reservation2/2
no opt-out signals
✕Serves markdown on request0/1
Accept: text/markdown → text/html; charset=UTF-8
→ Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.
✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
✕Docs or API link from the homepage0/3
no docs / API link and no /docs
→ Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
✕Content readable without JavaScript0/3
921 chars of visible text, 5.5% of HTML
→ Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
✕Semantic landmarks (main, single H1)0/3
no <main>, 0 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
1/1 images have alt
—Form fields are labelledn/a
—Descriptive link textn/a
✓Agent-friendly 404s2/2
nonexistent path → HTTP 403
✓Trust pages (privacy, terms, security)2/2
found: /privacy, /security
✕Organization schema complete0/2
no Organization in JSON-LD
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
✕llms.txt says what you are and links out0/2
no /llms.txt
→ Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.
✕Contact route discoverable0/2
no contact link or email on the homepage
→ Link /contact or a mailto: so an agent (or a human it hands off to) can reach you.

APIn/a›

—Spec parses and declares a versionn/a
—Operations have summaries and operationIdsn/a
—Error responses documentedn/a
—Auth scheme declaredn/a
—Versioned paths or serversn/a
—Spec within a model context budgetn/a

MCPn/a›

—Server answers initializen/a
—Tools listedn/a
—Tools carry descriptionsn/a
—Tool parameters have schemasn/a

AI visibility

Do AI assistants actually recommend Perplexity? Grounded LLM checks plus ecosystem presence, folded into the score.

✕Category share of voice0/6
not in the shortlist; assistants name: Here, AI, Zapier, Widely
Publish comparison and use-case content so AI assistants have grounds to recommend perplexity.ai for its category.
✓Brand name discoverability3/3
Perplexity (perplexity.ai) is an AI-powered search engine that provides direct, summarized answers to user queries with verifiable sources a
✓Wikipedia / Wikidata presence2/2
article: Perplexity
✓SDK package on npm1/1
npm: @openclaw/perplexity-plugin
✕Listed in the MCP registry0/1
not listed
Publish your MCP server to registry.modelcontextprotocol.io so agents can find it.

Perplexity is not currently shortlisted by major AI assistants, impacting its category share of voice. However, the brand is discoverable, has a Wikipedia presence, and an npm SDK, though it lacks an MCP registry listing.

AI-analyzed 2 hours ago · cached 7 days · grounded via web search

The report is free. Visibility is the bid.

Perplexity sits at #29 of 33. $1 moves it above Lenny's Newsletter.

Bid $1 →

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-25T11:39:34.358Z.

← Back to the board