Bot Protection quickstart

Open Projects → your project → Security on a deployed static site or container project. Enable Bot Protection independently of Web Firewall. Custom serverless agent endpoints do not have these project security controls.

Select paths

Enter comma-separated path prefixes under Bot-protected routes, such as /login, /signup, then save. Leave the field blank to inspect all paths. Common-bot filtering uses managed traffic classifications; it does not guarantee that every bot is blocked or provide a guaranteed invisible browser challenge. Legitimate automated clients may also be affected, so test your integrations.

Inspect the result

The dashboard shows aggregate blocked, allowed, and counted request totals by rule. Choose a time window and refresh. It does not expose per-request traffic logs or a history of visitor challenges. Allow time for configuration changes to propagate.

Availability and cost

Review the live rate card and the prices beside the project controls before enabling. The shared security access fee applies once while either protection is enabled. Bot protection has a prorated monthly fee, plus project request and bot-inspection usage. Blocked traffic can still create inspection or network usage. Request settings are attributed in five-minute billing intervals.

See Web Firewall for explicit allow/block rules and the project-wide rate limit.