WindCodex ScraperBlock

Overview

WindCodex ScraperBlock protects your WordPress content from AI training bots, web scrapers, and automation tools. It works on several layers - WordPress-level user-agent blocking, robots.txt directives, noai meta tags, and optional Apache .htaccess rules - without external services or API keys.

How It Works

Incoming request
      │
      ▼
┌--------------------------┐
│  .htaccess layer (opt.)  │  ← Apache only, before WordPress loads
└------------┬-------------┘
             ▼
┌-----------------------------------┐
│  WordPress loads                   │
│  ScraperBlock checks:              │
│  1. Protection disabled for this   │
│     post or page? → allow          │
│  2. User agent on the built-in     │
│     blocklist or your custom list? │
└------------┬----------------------┘
             │ Bot matched?
      ┌------┴------┐
     YES            NO
      │              │
      ▼              ▼
  Blocked (403)   Page served normally,
  and logged      with robots.txt rules and
                  noai meta tags in place

ScraperBlock doesn't require WooCommerce or any third-party API. It works on any WordPress site.

What's included

60+ built-in bot signatures, plus your own custom user agents
An option to allow AI search bots while blocking AI training crawlers
robots.txt directives, noai / noimageai meta tags, and optional .htaccess rules
Per-page control to turn protection off for specific posts and pages
A log of the last 50 blocked requests and a dashboard widget with the last 24 hours' count

Requirements

Requirement	Minimum
WordPress	6.9
PHP	7.4
Apache (for .htaccess blocking)	2.4+
Write permission to `.htaccess`	Required for .htaccess blocking

.htaccess blocking is optional. All other features work on Nginx, LiteSpeed and other servers.

Developer Reference Installation