AgentProbe
www.zenpirlanta.com
50/ 100
0.5s·5/12 passed·4/30/2026

Access

Whether AI bots can actually reach your content

67
✗

AI Bot Access

Fail

All 3 AI bots appear blocked or receive reduced content.

✓

JS Independence

Pass

Rich text content (17829 chars) and 15 heading(s) available without JavaScript.

✓

Performance

Pass

Fast response (186ms), no redirects.

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

63
▲

llms.txt

Partial

llms.txt found but missing proper title or resource links.

✓

robots.txt AI Bot Rules

Pass

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

✓

XML Sitemap

Pass

sitemap.xml found. Sitemap index found with 5 entries.

✗

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 2 JSON-LD block(s) with standard types: Organization, JewelryStore, WebSite.

▲

HTML Metadata

Partial

Missing: description.

Recommendations

5 suggestions
1

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

2

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

3

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

4

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

5

Ensure AI bot user agents receive the same content as browser visitors.