What it checks
We read /robots.txt on the checked host before anything else and apply its rules to our own User-Agent, QuietwatchBot, the way RFC 9309 describes: the most specific user-agent group wins, and inside a group the longest matching path rule wins. If that verdict is Disallow, we fetch nothing else on the host except the files robots.txt itself names.
Why it matters for search engines
Nothing about this check affects your ranking. It exists so that our other eleven checks can run, and so that a block is shown as a block rather than quietly reported as fine.
Why it matters for AI assistants
A robots.txt that blocks every unknown bot with a wildcard group also blocks the crawlers AI assistants use to read your pages. Seeing where our bot lands in your rules is a quick proxy for how any well-behaved crawler you have not named will be treated.
How to fix it
Add a group for QuietwatchBot with an Allow rule. Where the group sits in the file does not matter; under RFC 9309 the crawler picks the group whose user-agent token matches it best, so a named group always beats the wildcard group.
User-agent: QuietwatchBot
Allow: /Check one page right now, no account: the free Cloudflare and Googlebot check.
What quietwatch reports
ok when robots.txt allows us (with the group that decided it: a named group or the wildcard). warn when a rule blocks us, quoting the exact Disallow line and its group. unknown when robots.txt could not be read at all, for example a connection timeout. A 401 or 403 on robots.txt counts as no robots.txt, which RFC 9309 treats as allow.