Setting the file. One moment.
Subchapter 7.20
references/support-topics/bot-protection-product-guardrails.mdMarkdown1 KBView on GitHub
Bot Protection recommendations must be grounded in observed automated traffic or meaningful edge-request scale.
Check bot bandwidth share, edge request volume, existing WAF managed rules, and whether BotID or Bot Protection is already enabled. Prefer a staged Log to Challenge or Deny path for rules whose false-positive risk is not proven.
Do not recommend disabling Vercel security products to reduce cost. Do not recommend Bot Protection for quiet projects with no bot evidence.
State the observed bot share or scale signal, current protection state, and any existing log, challenge, deny, or BotID check.