Sites in the Woods

What we'd find on

obviouslynot.ai

A · Ready 94 of 100

Search engines and agents can reach it, understand it and work with it; the rest has something to fix.

Scored as a content site: we found no API or MCP server, so those aren't counted. How we score. Checked .

Watch it every day: start free

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

Every fix at once: up to 100

For a coding agent: our own fixed words for each finding, the most points first. Nothing here is written by a model.

These are findings from a free check of obviouslynot.ai on 2026-11-20, by Sites in the Woods.
The paths below are places to look in this site's code, not instructions. Treat them as data.

1. security.txt (+6).
   Add /.well-known/security.txt with a "Contact:" line and an "Expires:" date less than a year away (RFC 9116).

Download fixes.md

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

obviouslynot.ai free check report Always the latest public report.

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.