persona.com

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• !Sitemap present & freshrequirederror

  Could not fetch https://persona.com/sitemap.xml: Stream closed with error code NGHTTP2_PROTOCOL_ERROR

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✗Brand search discoverabilityrequired0/4

  Neither search ("PERSONA.COM", "PERSONA.COM sales marketing") cited persona.com. Cited instead: https://aibrandtracker.keywordseverywhere.com/website/persona.com, http://www.adrforum.com/domaindecisions/1458069.htm, https://www.texau.com/profiles/persona, https://www.adrforum.com/domaindecisions/644205.htm, https://worldmetrics.org/service/profile-verification/

  fix → Your domain doesn't surface when agents search "PERSONA.COM". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 1 User-agent group(s), 0 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✗AI crawler policyrequired0/5

  robots.txt blocks 12 of 12 AI crawler user-agents from /: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, anthropic-ai, PerplexityBot, Google-Extended, CCBot, meta-externalagent, Bytespider

  fix → robots.txt blocks GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, anthropic-ai, PerplexityBot, Google-Extended, CCBot, meta-externalagent, Bytespider. Add explicit `User-agent: <bot>` / `Allow: /` groups for the AI agents you welcome; a blanket Disallow makes you invisible to them.

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✗Content Signals directivesemerging0/2

  No Content-Signal lines in robots.txt

  fix → Declare Content Signals in robots.txt (e.g. `Content-Signal: search=yes, ai-train=no`) to express AI usage preferences machine-readably.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (7102 bytes)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• !agents.mdrecommendederror

  agents.md probes failed at the network layer: https://persona.com/agents.md (Stream closed with error code NGHTTP2_PROTOCOL_ERROR), https://persona.com/AGENTS.md (Stream closed with error code NGHTTP2_PROTOCOL_ERROR)

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Persona.com is a strategic-grade domain name available for sale, targeting established businesses and funded startups looking to enhance their long-term strategy, positioning, and operations.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ◐OpenGraph / social metadatarecommended1/2

  Homepage has og:title, og:description but is missing og:image (twitter:card="summary_large_image" present)

  fix → Add og:image meta tags to your homepage; agents and link unfurlers use them as your canonical summary.

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✗llms.txtrecommended0/4

  GET /llms.txt returned HTTP 404

  fix → Add /llms.txt: an H1 with your name, a one-line blockquote summary, and H2 sections of curated links to docs, pricing, and API.

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✗llms-full.txtbonusrecommended0/2

  GET /llms-full.txt returned HTTP 404

  fix → Add /llms-full.txt with expanded inline docs content so agents can load everything in one fetch.

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✗JSON-LD structured datarequired0/4

  No application/ld+json blocks found on homepage

  fix → Embed Organization + WebSite JSON-LD on your homepage (name, url, logo, sameAs) and Product/Offer JSON-LD on pricing.

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✗Markdown content negotiationrecommended0/3

  GET / with `Accept: text/markdown` returned HTTP 200 text/html; no .md twins found (1 probed)

  fix → Serve text/markdown when clients send `Accept: text/markdown` (or expose .md twins of key pages) — agents get far more signal per token.

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• —Developer resource discoverabilityrecommendedna

  No public API detected

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• —OpenAPI spec discoverablerequiredna

  No public developer API detected — API checks don't apply

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• !Docs discoverablerequirederror

  All 6 docs candidate fetches failed at the network layer (e.g. Stream closed with error code NGHTTP2_PROTOCOL_ERROR)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• !MCP server discoveryrequirederror

  MCP discovery probes all failed at the network layer: https://persona.com/.well-known/mcp/server-card.json: Stream closed with error code NGHTTP2_PROTOCOL_ERROR; https://persona.com/.well-known/mcp.json: Stream closed with error code NGHTTP2_PROTOCOL_ERROR; https://persona.com/mcp.json: Stream closed with error code NGHTTP2_PROTOCOL_ERROR

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• —npm SDKrecommendedna

  No public developer API detected — API checks don't apply

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• —PyPI SDKrecommendedna

  No public developer API detected — API checks don't apply

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No public developer API detected — API checks don't apply

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• —Docs qualityrecommendedna

  No documentation found to evaluate

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• —Quickstart / getting startedrecommendedna

  No public developer API detected — API checks don't apply

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No MCP endpoint known — tool lint requires a tools/list

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://persona.com/ upgrades to https in 1 hop(s), 1 redirect(s) total, final HTTP 200; no HSTS header

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ✓Response speed & weightrequired1/1

  Homepage TTFB 315ms, payload 7KB, Content-Encoding: gzip

  Measured homepage TTFB, payload size, and compression

  report issue
• !security.txtrecommendederror

  Fetch of https://persona.com/.well-known/security.txt failed at the network layer (The operation was aborted due to timeout)

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• —OAuth authorization server metadatarecommendedna

  No API or MCP server detected — OAuth metadata doesn't apply

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• —OAuth protected resource metadatarecommendedna

  No API or MCP server detected — OAuth metadata doesn't apply

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• —Auth documentationrecommendedna

  No public developer API detected — API checks don't apply

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✗Pricing discoverablerequired0/5

  No pricing page found: no homepage link matching pricing/plans/billing, and probes of /pricing and /plans returned no HTML page.

  fix → Expose a crawlable /pricing page with literal plan prices and link it from your homepage nav.

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• —Machine-readable pricingrecommendedna

  No pricing page found to evaluate

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• !x402 payment supportbonusrecommendederror

  Could not fetch /.well-known/x402 (The operation was aborted due to timeout).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• !AP2 readinessemergingerror

  Could not probe /.well-known/ap2: The operation was aborted due to timeout; no AP2 hints in fetched artifacts.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• !Agentic Commerce Protocolemergingerror

  Could not probe /.well-known/acp: The operation was aborted due to timeout; no Agentic Commerce Protocol hints in fetched artifacts.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• !Other agent payment protocolsbonusemergingerror

  No artifacts could be fetched for the UCP/MPP hint scan (/agents.md: Stream closed with error code NGHTTP2_PROTOCOL_ERROR).

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• —MCP handshake & tools listrequiredna

  No MCP endpoint known — nothing to handshake with

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• !NLWeb endpointemergingerror

  Could not probe NLWeb endpoints: /.well-known/nlweb.json failed (Stream closed with error code NGHTTP2_PROTOCOL_ERROR); /ask?query=hello failed (Stream closed with error code NGHTTP2_PROTOCOL_ERROR)

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ✗Semantic HTML structurerequired0/3

  Only 1/6 semantic signals present on the homepage (missing: <main> landmark, <nav> landmark, <header>/<footer>, exactly one <h1> (found 0), text-to-markup ratio ≥ 0.10)

  fix → Add landmark elements and a clean heading hierarchy — missing: <main> landmark, <nav> landmark, <header>/<footer>, exactly one <h1> (found 0), text-to-markup ratio ≥ 0.10.

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ◐Content readable without JavaScriptrequired1/2

  Homepage raw HTML contains only 605 chars of visible text (target ≥800)

  fix → Only 605 chars of your homepage are readable without JavaScript. Server-render or prerender key pages — most agent fetchers don't execute JS.

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✗Accessibility basicsrequired0/2

  Homepage accessibility: 2/5 checks passed — failing: <html lang> attribute; img alt coverage ≥80% (1/2 have alt); ≥2 landmarks (found 0: none)

  fix → Failing: <html lang> attribute; img alt coverage ≥80% (1/2 have alt); ≥2 landmarks (found 0: none). The accessibility tree is what browser-operating agents see.

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue