AgentProbe
schiesser.com
44/ 100
3.4s·4/12 passed·4/18/2026

Access

Whether AI bots can actually reach your content

83
✓

AI Bot Access

Pass

All 3 tested AI bots receive full page content.

✓

JS Independence

Pass

Rich text content (9739 chars) and 5 heading(s) available without JavaScript.

▲

Performance

Partial

Response time: 1188ms. 1 redirect(s).

Agent-Native

Support for agent-specific protocols and formats

0
✗

Markdown Support

Fail

No markdown content negotiation support detected.

✗

MCP Protocol

Fail

No MCP (Model Context Protocol) configuration found.

✗

Structured API

Fail

No structured API or OpenAPI specification detected.

Discovery

How easily AI agents can find and understand your site

25
✗

llms.txt

Fail

No llms.txt file found at the root of the domain.

✓

robots.txt AI Bot Rules

Pass

robots.txt found. All 8 AI bots are allowed.

✗

XML Sitemap

Fail

No sitemap.xml found at the root of the domain.

✗

AI Manifest

Fail

No AI manifest files found (.well-known/ai-plugin.json or .well-known/mcp.json).

Metadata

Structured data and metadata quality

75
✓

Schema.org

Pass

Found 1 JSON-LD block(s) with standard types: Organization.

▲

HTML Metadata

Partial

Missing: canonical.

Recommendations

6 suggestions
1

Add a /llms.txt file to help AI models understand your site content and structure.

2

Add a /sitemap.xml to help AI crawlers discover all your pages.

3

Add a /.well-known/ai-plugin.json or mcp.json to declare AI capabilities.

4

Support content negotiation for text/markdown to serve agent-friendly content.

5

Consider implementing MCP (Model Context Protocol) for richer AI integration.

6

Expose an OpenAPI/Swagger spec so AI agents can discover your API endpoints.