Learning Center · Answers · Access

What's the difference between bot protection and bot verification?

Short answer

Bot protection blocks or challenges automated visitors to keep out scrapers, credential stuffers and fraud. Verification checks that a visitor claiming to be a known agent really is, using the proof its operator publishes. Use verification inside your bot protection, so verified AI assistants and AI search get through and impostors using their names don't.

Comparison · Last checked November 12, 2026 · Based on Bot protection and CAPTCHAs: stop blocking the agents you want, How to tell if an AI crawler is real

What's the difference between bot protection and bot verification?
Bot protectionVerification
What it doesBlocks or challenges automated visitorsChecks a visitor is the agent it claims to be
Question it asksDoes this visitor look like a person?Did this request come from the company it names?
How it worksCDN, firewall or bot product rules and challengesSignatures, published IP ranges or reverse DNS
Risk if set badlyTurns away AI assistants along with scrapersBlocking everything unverified shuts out real agents
Where to be strictLogin, sign-up and checkout submissionRequests that claim a name but fail the check
Usually owned byBot protection or CDN adminBot protection or CDN admin

In more detail

Bot protection is the most common reason AI assistants are turned away from sites that want them. Honest agents announce themselves, often don't run JavaScript and come from data centers, so they look like bots for legitimate reasons. In Ghost Agent Lab's study of 255 online stores, 13% blocked or challenged AI assistants somewhere. The fix is usually a settings change.

Verification answers one question. Did this request really come from the company it names? Use the strongest proof each operator offers. A Web Bot Auth signature comes first, then published IP ranges, then forward-confirmed reverse DNS. Never let traffic through on its name alone. Treat requests you can't verify as unknown, and handle them with rate limits instead of a hard block.

What to do

  1. Run AgentScore and review the bot protection, CAPTCHA and key pages checks.
  2. In your CDN or bot settings, allow the verified AI assistant and AI search categories.
  3. Remove any rule that lets traffic through on its user agent name alone.
  4. Handle requests you can't verify with rate limits instead of a hard block.

Read more

All answers

How does your own site do?

AgentScore checks your site in about a minute and ranks what to fix first.