One look, the way crawlers and agents see it.
Type a domain and we'll read it once, the way search engines and agents do, and say what we found in plain words, with the fix for anything missing. No account.
Reading robots.txt, the homepage, llms.txt, Agent card, OpenAPI, MCP manifest and security.txt. Slow sites take up to 20 seconds.
Each report is kept at the site's own address (/check/example.com), with our findings only: never the site's text or your address. A site can keep us out with User-agent: site-monitor and Disallow: / in its robots.txt.
What we look at
- Can search engines and agents reach it?
- robots.txt, read for Googlebot, Bingbot and the AI search crawlers, on the homepage and llms.txt, and whether the homepage asks not to be indexed.
- Do they understand what it is?
- The homepage's description, its share card's title and image, its structured data, and llms.txt.
- Can an agent work with it?
- An OpenAPI description, an MCP manifest and an agent card: expected of a site with an API, and not counted against one without.
- Can they trust it?
- security.txt: how to report a security problem, and whether it's still in date.
What one look can't tell you
Whether your edge lets each crawler in (we try the door with their user agents once you've added the site), whether the share image loads, what your MCP server's tools are and when they change, and whether an agent can really sign up or check out. That's the monitoring: every hour, from two places, with an alert when something that worked stops. What agents need →
Anyone can look once: we look every hour and tell you when a deploy breaks one. Your first site is free, with no card. Pricing →
Last updated .