Access
Whether AI bots can actually reach your content
AI Bot Access
PartialSite returned status 530 even for browser UA.
JS Independence
PartialCould not fetch homepage to check JS independence.
Performance
FailHomepage returned status 530.
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
PartialNo robots.txt found. AI bots can access freely but lack explicit guidance.
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
FailCould not fetch homepage to check Schema.org data.
HTML Metadata
FailCould not fetch homepage to check HTML metadata.
Recommendations
10 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.
Improve server response time — AI agents value fast, reliable responses.
Add JSON-LD structured data (Schema.org) to help AI understand your content.
Improve HTML metadata: add lang, description, canonical, and proper heading structure.
Increase the amount of server-rendered content for better AI agent accessibility.