Access
Whether AI bots can actually reach your content
AI Bot Access
PassAll 3 tested AI bots receive full page content.
JS Independence
PassRich text content (3390 chars) and 3 heading(s) available without JavaScript.
Performance
PassFast response (148ms), no redirects.
Agent-Native
Support for agent-specific protocols and formats
Markdown Support
FailNo markdown content negotiation support detected.
MCP Protocol
FailNo MCP (Model Context Protocol) configuration found.
Structured API
FailNo structured API or OpenAPI specification detected.
Discovery
How easily AI agents can find and understand your site
llms.txt
FailNo llms.txt file found at the root of the domain.
robots.txt AI Bot Rules
Partialrobots.txt blocks 3/8 AI bots: GPTBot, ClaudeBot, Amazonbot.
XML Sitemap
FailNo sitemap.xml found at the root of the domain.
AI Manifest
FailNo AI manifest files found (.well-known/ai-plugin.json or .well-known/mcp.json).
Metadata
Structured data and metadata quality
Schema.org
PassFound 1 JSON-LD block(s) with standard types: WebSite, Organization, WebPage.
HTML Metadata
PartialMissing: description.
Recommendations
7 suggestionsAdd a /llms.txt file to help AI models understand your site content and structure.
Add a /sitemap.xml to help AI crawlers discover all your pages.
Add a /.well-known/ai-plugin.json or mcp.json to declare AI capabilities.
Support content negotiation for text/markdown to serve agent-friendly content.
Consider implementing MCP (Model Context Protocol) for richer AI integration.
Expose an OpenAPI/Swagger spec so AI agents can discover your API endpoints.
Consider unblocking these AI bots in robots.txt: GPTBot, ClaudeBot, Amazonbot.