Cloudflare Pro for Bot Traffic

We’re looking for a Cloudflare specialist to help investigate and reduce recurring suspicious traffic that is polluting GA4 reporting for a client website. The issue we’re seeing in GA4 is a very consistent traffic pattern: - Source / medium: (direct) / (none) - Location: Columbia, MD - Device / browser: Desktop Chrome - Volume: roughly 31,000 users, about 19.5% of total site traffic - Behavior: 100% new users, very low key-event rate, no revenue - Pattern: traffic spikes every other day, mostly in the evening / overnight hours The pattern looks like a scheduled job, crawler, scraper, uptime monitor, SEO tool, or security scanner. Since GA4 does not expose IP addresses, we need someone who knows Cloudflare well enough to help us identify the request-level details and determine the safest way to challenge or block the traffic. The client is on Cloudflare Pro and will grant me read access. Their developer is available but does not know Cloudflare well enough to lead the investigation. What we need help with: - Review Cloudflare traffic and security data for the suspicious spike windows - Identify likely IPs, ASNs, user agents, paths, and request patterns tied to the Columbia, MD traffic - Determine whether the traffic is bot, crawler, scanner, monitor, or another automated source - Recommend the safest Cloudflare rule strategy using the tools available on the Pro plan - Help create or advise on WAF/custom rules to challenge or block the traffic - Avoid blocking legitimate users or Google/Bing/known good bots - Provide a short summary of findings and recommended next steps Ideal experience: - Strong hands-on Cloudflare experience - Comfortable with Cloudflare Pro plan limitations - Experience investigating bot traffic, crawlers, scrapers, and analytics pollution - Familiarity with WAF rules, firewall events, bot signals, ASNs, user agents, and request patterns - Bonus if you understand GA4 enough to connect analytics behavior back to server/CDN logs Deliverable: A clear set of findings showing which IPs, ASNs, user agents, or request patterns are likely causing the issue, plus the Cloudflare rule recommendations needed to reduce or block the traffic safely. Please include examples of similar Cloudflare bot traffic investigations you’ve handled.