01
Per bot, not in general.

OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot and Google-Extended each get checked against your robots.txt on their own. A block on one is invisibility on that engine.
SEO auditor
We audited 383 Show HN launches. 27% could not be read by the crawlers behind ChatGPT and Claude, and one in ten was blocked by its own CDN while robots.txt said everyone was welcome. He finds what is blocking you, watches who gets named instead of you, and opens a PR with the fix.

you merge it
01

OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot and Google-Extended each get checked against your robots.txt on their own. A block on one is invisibility on that engine.
02

Block AI Scrapers is on by default on some plans and it quietly overrides robots.txt. He requests your site as each crawler and compares the answer against a control fetch.
03

AI crawlers mostly do not execute it. He compares your rendered text against the raw HTML and tells you how much of your site is simply not there.
04

The H1 gets answered in forty words before any throat clearing, and every H2 is phrased as the question a buyer asks with the answer directly beneath it.
He installs as a GitHub App on the one repo you pick, works in a clone, and opens a pull request. He does not push to main and he cannot.
Pull request
ready to mergefix: let ClaudeBot and OAI-SearchBot in

Whichever brands the engines already trust on your topic, which is rarely you on day one. The audit is a one time thing. This is the part that keeps mattering. He asks the engines your buying questions on a schedule and records which brands come back.
Paste your URL and he reads the site, writes his brief, and starts finding the threads where your buyers are asking. You approve, he posts, you ship.