Access
Whether AI bots can actually reach your content
AI Bot Access
PassAll 3 tested AI bots receive full page content.
JS Independence
PartialLimited content without JavaScript (0 chars, 0 heading(s)).
Performance
PartialResponse time: 1514ms.
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
Passllms.txt found with proper title and links. llms-full.txt also available.
robots.txt AI Bot Rules
Failrobots.txt blocks all 8 AI bots.
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: Organization.
HTML Metadata
PartialMissing: canonical, h1.
Recommendations
7 suggestionsReview your robots.txt to ensure AI bots like GPTBot and ClaudeBot are not blocked.
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.
Increase the amount of server-rendered content for better AI agent accessibility.