You found this from your server logs
You're probably here because you saw KnownGood-Verifier in your access logs. This page tells you exactly what it does, what it fetched, how to slow it down or block it entirely, and how to confirm it's really us. No dark patterns — the opt-out is right at the top.
If you want us gone, add this to your robots.txt. We check it on
every visit and honour it immediately; a disallow takes effect on our next request,
and we cache your rules so we won't re-probe you.
User-agent: KnownGood-Verifier Disallow: /
Prefer to stay listed but slow us down? Set a crawl delay:
User-agent: KnownGood-Verifier Crawl-delay: 30
And if your only concern is AI use of your content generally, the Content Signals standard lets you say so once, to every AI crawler at once. We treat ai-input=no as a hard stop: we will not list or re-probe a site that declares it, regardless of anything else on the page.
Every “no” we honour, in order. robots.txt Disallow for our user-agent — binding (RFC 9309). ai-input=no — the Content Signals convention; we treat it as binding. Content-Usage: search=n as a header or a robots.txt line — the IETF AI Preferences draft, not yet an RFC, honoured now. X-Robots-Tag: noai or the equivalent meta tag — informal, no standard behind it, honoured as a courtesy because a site that wrote it meant it.
How a site comes to be checked. We check a site when it declares agents welcome in robots.txt, or publishes an agent endpoint — an MCP server card, an API catalog, an llms.txt — or appears in a public MCP registry, or an owner asks at /submit. Publishing an endpoint for agents is an invitation to agents; we treat it as one. If that is not what you meant, the lines above stop us.
KnownGood-Verifier checks whether an AI agent — the kind a real person now sends to browse, compare, and act on their behalf — can actually read and use your site. It's how we build Known-Good, an index of the sites that pass. It is a verifier, not a scraper: it reads a handful of standard files to assess readiness. It does not harvest your content, your prices, or your customer data.
Anyone can put our name in a user-agent string. To confirm a request is genuinely from KnownGood-Verifier and not an impostor borrowing our name, check that the source IP falls within our published range — spoofed traffic wearing our UA will not.
Seeing our name from an IP outside that range? That's someone spoofing us — block it, and if you like, tell us at the address below so we can flag it.
robots.txt for our user-agent, every visit.ai-input=no as a hard opt-out — never listed, never re-probed.Questions, complaints, or a request to stop entirely — reach a human at bot@knowngood.sh. We answer, and we act on it.
The reason we exist is that the web has a second reader now. Alongside people and search crawlers, AI agents — sent by real customers — are starting to read sites, compare options, and complete tasks. Most of the web is invisible or unusable to them. That's what we measure, and it's increasingly what decides whether an agent can recommend, book, or buy from you.
If you're the kind of person who looks up a crawler in their logs, you're exactly the kind of person who'll want to know how your site scored. We'll walk your site with you and show you what an agent sees.
Free · 30 minutes · over video
Book a free agent-readiness review — we'll screen-share your site, show you where an agent gets stuck, and what to fix first. No pitch, no obligation.
Book your free review →