Sample report — scan of example.com

Category breakdown

• Crawler Access 85/100
  Weight in overall score: 22%
• Crawlability & Rendering 65/100
  Weight in overall score: 13%
• Structured Data 32/100
  Weight in overall score: 20%
• Discoverability 0/100
  Weight in overall score: 9%
• Content Accessibility 0/100
  Weight in overall score: 5%
• Bot Access Control 0/100
  Weight in overall score: 10%
• Protocol Discovery 0/100
  Weight in overall score: 14%
• Entity & Knowledge Graph 45/100
  Weight in overall score: 25%

What the scanner checked

39 individual signals were evaluated. Findings, worst-first:

• fail schema.jsonld — No Schema.org JSON-LD found — AI engines have to infer what your entity is.
• fail meta.canonical — No canonical tag — duplicate-content ambiguity for crawlers.
• fail meta.social — Open Graph: 0/3 core tags; Twitter card: missing.
• warn crawler.ai_bots_named — No robots.txt at all — AI crawlers are not addressed, so you signal no intentional AI-access policy.
• warn crawl.js_render — Only ~21 words of text in the raw HTML — thin or partially JS-dependent content.
• warn crawl.llms_txt — No /llms.txt — AI crawlers have no curated manifest of your important pages.
• warn crawl.llms_full — No /llms-full.txt — the full-corpus companion to llms.txt is missing.
• warn meta.title_description — Title present (14 chars); no meta description.
• warn entity.org_schema — No Organization/Brand JSON-LD — models have to infer your identity from prose.
• warn entity.sameas — Few or no sameAs links — AI can’t connect your site to your authoritative profiles.
• warn entity.about — No About page detected — add one with a consistent company description.
• pass crawler.search_access — All 9 major AI search crawlers (OpenAI, Anthropic, Perplexity, Google, Bing, Apple…) are allowed to read your site.
• pass crawler.training_access — AI training crawlers are allowed, so future models can learn about your brand.
• pass crawler.waf_challenge — No CDN/WAF bot-challenge detected on the homepage fetch.
• pass crawler.x_robots_tag — No restrictive X-Robots-Tag header on the homepage.
• pass crawler.meta_robots — No restrictive robots meta tag on the homepage.
• pass crawl.http_ok — Homepage returns HTTP 200.
• pass crawl.https — Served over HTTPS.
• pass crawl.no_login_wall — No login/paywall wall detected over the homepage content.
• pass meta.headings — Exactly one <h1> on the homepage.
• pass meta.lang — Document language declared (lang="en").
• pass entity.wikidata — Recognised as a Wikidata entity (Q306656) — a core LLM knowledge-graph signal.
• pass entity.wikipedia — Has a linked Wikipedia article — the single strongest entity-trust signal for LLMs.
• info agent.robots — No robots.txt — agents and crawlers have no published access policy to read.
• info agent.sitemap — No sitemap found — agents must guess your URL structure.
• info agent.link_relations — No service-desc / describedby Link headers — agents have no pointer to a machine description.
• info agent.dns_aid — No DNS-AID record — agents can’t discover your agent endpoint straight from DNS.
• info agent.markdown — Homepage returns only HTML for Accept: text/markdown — agents parse markup instead of clean text.
• info agent.ai_bot_rules — robots.txt has no rules covering AI crawlers — access is implicit/undeclared.
• info agent.content_signals — No Content-Signal directives — search / ai-input / ai-train preferences are unstated.
• info agent.web_bot_auth — No Web Bot Auth key directory — your bots can’t sign requests to prove identity. (Measures the signer side only.)
• info agent.mcp_server_card — No MCP server card under /.well-known/mcp/ — agents can’t discover callable tools.
• info agent.agent_skills — No agent-skills manifest — agents have no declared list of what your site can do.
• info agent.a2a_card — No A2A agent card at /.well-known/agent-card.json — agent-to-agent interop isn’t advertised.
• info agent.api_catalog — No /.well-known/api-catalog (RFC 9727) — agents must guess where your APIs live.
• info agent.webmcp — No WebMCP manifest at /.well-known/webmcp. Note: real WebMCP registers tools at runtime, which this scan can’t execute.
• info agent.oauth_protected_resource — No /.well-known/oauth-protected-resource (RFC 9728) — no discoverable auth for an OAuth-protected agent surface.
• info agent.oauth_discovery — No OAuth/OIDC discovery document — authenticated agent flows have no documented entry point.
• info agent.auth_md — No /auth.md — no plain-language guide for how agents authenticate to your services.