AgentProbe
wagerx.io
62/ 100
5.6s·6/12 passed·9/27/2026

Access

Whether AI bots can actually reach your content

67
▲

AI Bot Access

Partial

1/3 AI bots appear blocked: GoogleBot.

✓

JS Independence

Pass

Rich text content (20088 chars) and 39 heading(s) available without JavaScript.

▲

Performance

Partial

Response time: 2102ms.

Agent-Native

Support for agent-specific protocols and formats

33
✗

Markdown Support

Fail

No markdown content negotiation support detected.

✗

MCP Protocol

Fail

No MCP (Model Context Protocol) configuration found.

✓

Structured API

Pass

OpenAPI/Swagger spec found at /openapi.json.

Discovery

How easily AI agents can find and understand your site

63
✓

llms.txt

Pass

llms.txt found with proper title and links. llms-full.txt also available.

▲

robots.txt AI Bot Rules

Partial

robots.txt blocks 2/8 AI bots: Amazonbot, cohere-ai.

✓

XML Sitemap

Pass

sitemap.xml found. Sitemap index found with 10 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

100
✓

Schema.org

Pass

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

✓

HTML Metadata

Pass

All key HTML metadata present.

Recommendations

4 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

Consider unblocking these AI bots in robots.txt: Amazonbot, cohere-ai.

Scan another URL