AgentProbe
blog.ft.ia.br
60/ 100
0.2s·7/12 passed·4/18/2026

Access

Whether AI bots can actually reach your content

100
✓

AI Bot Access

Pass

All 3 tested AI bots receive full page content.

✓

JS Independence

Pass

Rich text content (2264 chars) and 11 heading(s) available without JavaScript.

✓

Performance

Pass

Fast response (70ms), 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

50
✓

llms.txt

Pass

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

✓

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

100
✓

Schema.org

Pass

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

✓

HTML Metadata

Pass

All key HTML metadata present.

Recommendations

5 suggestions
1

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

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.

Scan another URL