KillBot vs WindCodex ScraperBlock – Block AI Scrapers & Bots from WordPress & WooCommerce

The KillBot plugin for WordPress uses the external KillBot service to protect websites from bots and automated traffic. What is this service, and what is it used for? KillBot is an anti-bot system that analyzes traffic, detects bots, and can either block them or present a CAPTCHA. The plugin interacts with the KillBot service to check users for signs of automated behavior and detect the use of proxies or VPNs. What data is sent and when? The plugin sends the following data to the KillBot server upon each new visit session: – The window.navigator object – The window.screen object – The window object (excluding string-based parameter values) Important: KillBot does not receive any personal user data, such as names, email addresses, or account identifiers. Links to Terms of Service and Privacy Policy KillBot Terms of Service: https://my.kill-bot.net/node/7 KillBot Privacy Policy: https://my.kill-bot.net/node/29

WindCodex ScraperBlock is a free WordPress plugin that blocks AI scrapers, content crawlers, and unwanted bots from harvesting your site. Protect blog posts, product pages, and proprietary content from being fed into AI training datasets – without slowing your site down for real visitors. Setup takes under two minutes: install, enable the protections you want, save. Why Your Site Needs Bot Protection AI crawlers – including GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended, ByteSpider, CCBot (Common Crawl), and dozens more – continuously scrape WordPress sites for training data. For content creators, WooCommerce store owners, and publishers, this means: Your original content gets harvested and used without permission or attribution. AI training traffic inflates your server load and bandwidth costs. WooCommerce store owners face a specific threat – price bots and competitor scrapers continuously harvest product prices, stock levels, and catalog data to undercut your pricing in real time. Proprietary product descriptions, pricing strategies, and business data are exposed to competitors and AI systems. Scraper traffic can mask real user patterns in your analytics. ScraperBlock gives you practical, layered defences against these threats – all from one settings screen. Free Features Protection Controls * Master protection switch – Enable or disable all ScraperBlock protections with a single toggle. * 50+ default bot signatures – Pre-loaded, categorized list of known AI scrapers, content crawlers, and price bots including GPTBot (OpenAI), ClaudeBot (Anthropic), Google-Extended, ByteSpider (ByteDance), CCBot (Common Crawl), Diffbot, PerplexityBot, and more. Maintained and updated regularly. * Custom user-agent rules – Add your own bot signatures, one per line. Target bots not in the default list. Blocking Methods * Runtime user-agent blocking – Intercepts matching bots at the PHP layer before any content is served. Works on all server types. * robots.txt blocking – Automatically injects Disallow directives for blocked bots into your robots.txt file. Signals crawlers to stay away before they visit. * Apache .htaccess blocking – Adds server-level RewriteRule blocks for matched user-agents. Stops bots before they reach PHP (Apache only). AI Opt-Out Meta Tags * noai and noimageai meta tags – Outputs on your pages. Signals AI training opt-out to crawlers that respect meta directives. * Per-page meta control – Override protection settings on individual posts and pages using a meta box in the editor. Enable, disable, or customize protection per page. Monitoring * Basic block log – Stores the last 50 blocked request events with IP, user-agent, URL path, reason, and timestamp. * Live dashboard count – Shows a basic count of blocked requests from the last 24 hours. See activity at a glance without leaving wp-admin. * Basic rate limiting – Limit request frequency from individual IPs to reduce scraper throughput. Who Needs ScraperBlock? Bloggers and content creators – Protect original articles and creative work from AI training scrapes. WooCommerce store owners – Block competitor price scrapers and AI bots that harvest product prices, descriptions, and stock levels to undercut your pricing or feed your catalog into AI systems. News and media publishers – Opt out of AI content aggregation and training dataset inclusion. Membership and course sites – Prevent paid content from being scraped by bots that bypass login pages via API or sitemap traversal. Agencies – Deploy consistent bot protection across client sites. How It Works Install and activate ScraperBlock. Go to Settings > ScraperBlock. Enable the protection modules you want (runtime blocking, robots.txt, meta tags, per-page control). Save settings. Monitor blocked requests in the Logs panel and Dashboard count widget. 🚀 Pro Version Need content poisoning, honeypot traps, behavioural detection, real-time threat feed, geo-based blocking, IP allowlists, block scheduling, and advanced analytics? ScraperBlock Pro is available at windcodex.com ScraperBlock Pro adds advanced features for high-traffic sites and serious content protection: Content poisoning – Serve subtly corrupted content to detected scrapers, degrading the value of stolen data. Honeypot traps – Invisible links that only bots follow – automatically flag and block crawlers. Behavioural detection – Identify bots by traffic pattern, not just user-agent string. Real-time threat feed – Cloud-updated block list with new bot signatures pushed automatically. Geo-based blocking – Block all traffic from specific countries at the application layer. IP allowlists & blocklists – Block individual IP addresses and CIDR ranges in addition to user-agents. Block scheduling – Define time windows when protection is active or relaxed. Advanced analytics – Full traffic breakdown by bot, country, URL, and time range with CSV export. Requirements WordPress 5.8 or higher PHP 7.4 or higher Apache is required only for .htaccess blocking mode. All other modes work on any server. Privacy ScraperBlock stores technical security data (IP address, user-agent string, URL path, block reason, action, and timestamp) in your WordPress database for local monitoring purposes. The free plugin does not require or contact any third-party API. No data is transmitted off your server.