RedHub AI
How the gate works
How the AI Bot & Scraper Traffic Control Readiness gate works
This tool grades one web property's control over AI bots and scrapers before you trust that your stated rules actually hold. It scores 6 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.
The 6 weighted controls
Two controls decide whether anything is enforceable: an enforcement layer and a way to verify real bots by IP, not by a spoofable user-agent string. Leave both below Ready and the property is EXPOSED regardless of the score — you can declare a stance you cannot make stick. Bring either control to Ready and the gate releases.
Why: Stance and directives are fully set and everything else is partway there — the readiness score is 65, which reads GAPS. But enforcement and bot-verification are both only partial: you can publish rules, but you can't enforce them on bots that ignore them and can't tell a real crawler from a spoofed one. The enforceability gate forces EXPOSED regardless of the 65.
A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Grades your control posture, never people. Not a bot detector or a WAF, and no tool guarantees a crawler obeys you. Not legal advice.