Monitoring for AI, not AI for monitoring.
Many monitors now come with an MCP server, so agents can set them up and ask them questions: that's AI for monitoring. Sites in the Woods is monitoring for AI: it checks whether search engines and AI agents can still find, read and use your site, with uptime included.
The first site is free, with every check and alerts to Discord, Slack, your own webhook, email or a browser notification. See pricing.
Where we're different
- Newest content. The newest pages in each sitemap are checked like pages, so a site that's up but has stopped publishing is caught.
- Search, watched. A noindex that ships, a canonical that flips, a sitemap that stops updating, robots.txt that starts blocking crawlers.
- The agent side, every hour. llms.txt, agent cards, OpenAPI and MCP servers, with MCP tool-list changes flagged, and an AI agent that tries the site with only the address and a goal.
Where others are stronger
- Many check locations. We check from two, in the US.
- On-call: phone calls, SMS, rotations and escalation. Our alerts go to Discord, Slack, your own webhook, email or a browser notification.
- Price for plain uptime. If all you need is up or down, an uptime monitor costs less.
The comparisons
- UptimeRobot vs Sites in the Woods
- A hosted uptime monitor with a generous free plan, status pages, many alert channels and an MCP server for your agents.
- Oh Dear vs Sites in the Woods
- One hosted product for uptime, certificates, dead links, sitemaps, Lighthouse, DNS, ports and cron jobs, with every feature on every plan.
- Agent-readiness scanners vs Sites in the Woods
- Agent-readiness scanners like Ora and Cloudflare's isitagentready.com compared with Sites in the Woods: a grade once, or agent files and MCP watched.
Every fact about another tool links to the page on its own website where we read it, with the date we checked. We add a comparison when someone asks about a tool, not all at once.
Last updated .