One Site Measured 214 Bot Page Loads for Every Human Visitor — That Crawl Data Is a Sellable Audit Service for Every Content-Heavy Site.

PatronView didn't just complain about bot traffic.

It measured it, down to the exact ratio for every major crawler, and published the numbers.

That measurement is the business.

What the data actually says

PatronView runs a 1.5-million-page database of American philanthropists built from IRS 990 forms, public donor walls, and annual reports. In one week, the site's server "answered 2.5 million requests from the outside world and served 1.28 million full pages," while visitor-tracking software (self-hosted Plausible) "only recorded 5,977 pageviews." The gap: "214 bot page loads for every 1 human."

The peak was worse. "On April 22, my site took 3.6 million requests in a single day. They came from 361,844 unique IP addresses, and nearly all of them were in China." Cloudflare's Managed Challenge "absorbed 1.18 million of those in the first ten hours" — and the CAPTCHA solve rate across all traffic sat at "0.24%. The bots don't even try."

The most useful number for a service pitch is the crawl-to-referral ratio. PatronView measured Claude-SearchBot at "35,000 to 1" — for every human visitor Claude sent, its crawler read 35,000 pages — against Googlebot's 46:1 and Bingbot's 406:1. Amazon's search bot was worse than all of them: "reading 117,000 pages a day and has never sent me a single visitor."

The service

The audit itself is the deliverable PatronView already documented: pull real server logs (not JS analytics, which miss nearly all bots), compute a crawl-to-referral ratio per bot, and rank them. Bots with a high ratio and zero referrals — the Amazon pattern — get blocked. Bots that convert, like Bing at "158,610 requests for 680 visitors," stay unblocked because the referral pays for the crawl.

The fix layer is concrete and repeatable: Cloudflare firewall rules, managed AI Crawl Control (which "blocks the declared training bots... before my rules even run"), and geo-blocking for abusive regions. PatronView blocked Claude-SearchBot at the firewall and watched it "drop from 60,000 requests a day to about 25 attempts a day."

Who buys this

Any site carrying a large database, directory, or content library that has never looked past its JavaScript analytics dashboard — which, per PatronView, hides "about 500 visitors a day" while the server underneath answers millions of real requests.

Bottom line

PatronView proved the audit is measurable, not just anecdotal: a specific ratio per bot, a specific block list, and a specific before/after (60,000 requests a day down to 25). That's a scoped, priceable service — not a vague "bot problem."

Source: https://patronview.com/news/99-percent-of-my-website-traffic-is-bots/