Harden Cloudflare Against Content Scrapers

We are using Cloudflare and need to block scraping and traffic.

My site’s articles are being lifted almost as soon as they go live. It is definitely content scraping and, despite the fact that I already block offending IPs and run basic rate-limiting through Cloudflare, the traffic keeps finding its way around those measures.

I need someone deeply familiar with Cloudflare’s firewall rules, Managed Challenge, Bot Management, and edge-side features to tighten things up without breaking the experience for legitimate users or search-engine crawlers. Please review my current rules, identify loopholes, and implement a layered defence that might include custom WAF rules, dynamic JavaScript challenges, threat score thresholds, or other techniques you know to be effective.

Deliverables
• Audit report outlining weaknesses in my current Cloudflare setup
• Updated configuration (rules, filters, or workers) ready for production
• Brief how-to so I can maintain the new settings going forward

Success is a measurable drop in scraping attempts while normal user traffic remains unaffected.