Sites in the Woods

What we'd find on

sitesinthewoods.com

A newer report exists: see the latest.

Nothing to fix.

Checked .

Watch it every day: start free

Can search engines and agents reach it?
Do they understand what it is?
Can an agent work with it?
Can they trust it?

What one look can't tell you

A look at the homepage and its public files, not a security test or a certification. Anyone can look once: we look every hour and tell you when a deploy breaks one of these.

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 →

Watch it every day: start free

Share

For agents: data.json and report.md.

Look at another

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.