Gabriel CorralEngineer, with three Cloudflare colleaguesCloudflare
Platform operator. Customer sites that blocked PerplexityBot. Report published August 4, 2025.
The Cloudflare Blog, published Read the write-up (opens The Cloudflare Blog in a new tab)
Observation
Cloudflare caught Perplexity using undeclared crawlers on sites that had blocked it, and de-listed it as a verified bot.
- Takeaway
- If your company publishes content, check whether Perplexity can reach pages you block, and ask legal whether that matters before you buy seats.
- What happened
- After complaints from customers who had disallowed Perplexity in robots.txt and blocked its declared crawlers with firewall rules, Cloudflare's tests showed Perplexity reaching those sites through undeclared crawlers with rotating IP addresses and a generic browser user agent. After the incident, on August 4, 2025, Cloudflare de-listed Perplexity as a verified bot and added managed rules that block the stealth crawling for every customer.
“We received complaints from customers who had both disallowed Perplexity crawling activity in their robots.txt files and also created WAF rules to specifically block both of Perplexity’s declared crawlers: PerplexityBot and Perplexity-User.”
- Public engineering write-up
- Tests run by Cloudflare
Deployment details
Platform operator. Customer sites that blocked PerplexityBot. Report published August 4, 2025.
- Public engineering write-up
- Tests run by Cloudflare
- Team
- Cloudflare's bot management engineers
- Workload
- Detecting crawler traffic against robots.txt rules
- Product version
- Perplexity's crawlers






