AgentProbe
gemini.google.com
43/ 100
1.5s·3/12 passed·4/18/2026

Access

Whether AI bots can actually reach your content

67
✓

AI Bot Access

Pass

All 3 tested AI bots receive full page content.

▲

JS Independence

Partial

Limited content without JavaScript (0 chars, 0 heading(s)).

▲

Performance

Partial

Response time: 396ms. 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

38
✗

llms.txt

Fail

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

▲

robots.txt AI Bot Rules

Partial

No robots.txt found. AI bots can access freely but lack explicit guidance.

✓

XML Sitemap

Pass

sitemap.xml found. Contains 315 URLs.

✗

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: WebSite.

▲

HTML Metadata

Partial

Missing: h1.

Recommendations

6 suggestions
1

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

2

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

3

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

4

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

5

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

6

Increase the amount of server-rendered content for better AI agent accessibility.