Agent Readiness
Can AI agents actually use your site?
Scan any root URL for agent readiness. 28 checks across standards and 34 AI crawlers, a headless-browser render of what an agent sees, and a read on whether it can understand the page.
How it works
From root URL to readiness report.
One scan probes the whole access path: who can crawl you, what a headless agent renders, and whether the content reads clearly. No setup, no crawl scheduling.
- 01Give
Give
A root URL
Agent Readiness runs infrastructure-level checks, so it starts at your root domain, not a single page.
https://geotoolbox.ai
- 02Probe
Probe
28 checks across 3 layers
Standards and a 34-crawler access matrix, a headless-Chromium render of what an agent actually sees, and a content-intelligence read of clarity and entities.
28/28 · Static · Visual · Content
- 03Fix
Fix
A readiness report
The bot matrix, the above-fold capture, the JS-parity diff, and the exact fixes. The PDF adds full hop transcripts and screenshots.
Report · transcripts + screenshots
28 checks, 3 layers
Reach, render, and read.
An agent has to get past your robots and firewall, render the page without a real browser, and pull meaning out of it. Each layer checks one of those.
Standards + crawler access
- robots.txt vs 34 AI crawlers
- Sitemap + Link headers
- Content Signals
- Markdown content negotiation
- Agentic content readiness
- Google agent-UX guidance
- schema.org @type validation
What a headless agent sees
- Above-fold screenshot (1280×800)
- JS-rendering parity (JS vs no-JS)
- Console + network health
- JS framework detection
- Form-action detection
Can an agent understand it
- BLUF clarity score
- Entity-density analysis
28 of 28 checks live. Real results show per-check evidence, the source line, and the exact fix.
What makes it different
The access path, not just the page.
34 crawlers
Every AI agent user agent
We test your robots.txt and live access against 34 AI crawler user agents, including GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Amazonbot, Bytespider, Applebot, and meta-externalagent. For each, allowed or blocked, and the source of any block.
Visual capture
What an agent actually sees
A headless Chromium 138 capture of your above-the-fold render at 1280×800. Plenty of sites look fine in your browser and render empty or broken to a bot. This shows the page the way an agent receives it.
JS parity
Content that survives no-JS
Most AI crawlers do not execute JavaScript. We diff the JS and no-JS render and flag any content, navigation, or links that only exist after hydration.
Standards parity
Beyond robots.txt
Sitemap and Link headers, Content Signals, Markdown content negotiation, agentic content readiness, and Google's agent-UX guidance, so an agent can both reach and traverse the site.
Schema validation
Structured data that parses
schema.org @type validation, so the structured data an agent reads is well-formed and type-correct, not just present.
Entity intelligence
Clarity an agent can extract
A content-intelligence pass with Claude Haiku scores BLUF clarity and entity density: whether an agent can quickly extract who you are and what the page actually says.
FAQ
Frequently asked
- 01What is agent readiness?Agent readiness measures whether AI agents and crawlers can reach, render, and understand your site. Where a page-level audit asks whether one page is citable, agent readiness asks whether an autonomous agent can fetch, see, and parse the site at all. It runs 28 live checks across three layers: standards and crawler access, a headless-browser visual render, and a content-intelligence read.
- 02How is it different from Content Analyzer?Content Analyzer grades a single page A to F for citability. Agent Readiness works at the site and infrastructure level from a root URL: which of 34 AI crawlers can get in, what a headless agent actually sees, JS-rendering parity, and standards like sitemaps, Link headers, and markdown negotiation. Use Agent Readiness to clear the access path, then Content Analyzer to optimize the page once agents can reach it.
- 03Which AI crawlers does it check?34 AI crawler user agents, including GPTBot and OAI-SearchBot (OpenAI), ClaudeBot, PerplexityBot, Google-Extended, CCBot, Amazonbot, Bytespider, Applebot, and meta-externalagent. For each one it reports allowed or blocked and the source of any block: robots.txt, a response header, or a firewall rule.
- 04What does “what an AI agent sees” mean?We render your URL in a headless Chromium 138 browser and capture the above-the-fold view at 1280×800. Many sites look fine in your own browser but render empty or broken to a bot. The screenshot shows the page as an agent receives it, alongside console and network health.
- 05Does it check JavaScript rendering?Yes. We fetch the page with and without JavaScript execution and diff the two. Content, navigation, or links that only appear after hydration are flagged, because most AI crawlers do not run JS. We also detect the JS framework and any form actions.
- 06Can I export the report?Yes. Every probe produces a report you can download as a PDF, including the 34-crawler matrix, the above-fold capture, the JS-parity diff, full hop transcripts, and prioritized fixes. Clean enough to hand to a developer, detailed enough to debug.
Scan your site for agents.
Free while in beta. No credit card. One root URL is all it takes.