Bot traffic now accounts for more than half of all web activity, and Kinsta‘s own infrastructure data puts a sharper edge on that statistic. In a single 24-hour period, bots hit add-to-cart URLs on Kinsta-hosted sites 7.67 million times. One crawler alone triggered 550 million requests across a 30-day window. For WordPress site owners watching server costs climb while their analytics show nothing obviously wrong, those numbers explain a problem that has been genuinely difficult to act on without outside help.
Kinsta has added Bot Protection directly into its MyKinsta dashboard, making it available to every customer on every plan at no extra cost. The feature gives site owners self-serve control over automated and AI-driven traffic at the environment level, without filing a support ticket or adding a third-party tool to the stack.
The configuration options cover four preset protection levels, ranging from blocking only confirmed malicious traffic to challenging every visitor during an active attack. A managed allow list handles common WordPress paths, WooCommerce routes, and trusted traffic sources automatically, while owners can add custom exceptions by IP address, user agent, or request path. A separate toggle lets sites opt out of AI crawler indexing entirely for those who want that line drawn cleanly. Verified search engine crawlers from Google pass through regardless of which protection level is active.
Daniel Pataki, CTO at Kinsta, described the design intention as putting the decision in the hands of site owners rather than forcing a binary choice. “Block too aggressively and you hurt your search visibility,” he said. “Do nothing, and bots are consuming server resources on endpoints that will never convert.”
The analytics component matters too. A dedicated dashboard tab breaks traffic down by category, separating verified bots, AI crawlers, automated traffic, and likely human visitors. For site owners whose data has been skewed by bot activity, that breakdown gives them something reliable to act on rather than trying to reverse-engineer anomalies in their existing reports.
Roger Williams, community manager at Kinsta, noted that customers had been telling the company their server costs kept rising despite analytics that looked normal. Bot traffic was driving it, and they had no straightforward way to respond without outside tools or support involvement.
The feature addresses that gap directly and without adding to the monthly bill.
