Documentation
ScraperBlock
Overview

WindCodex ScraperBlock

Overview

WindCodex ScraperBlock protects your WordPress content from AI training bots, web scrapers, and unwanted automation tools. It operates at multiple layers - from HTTP-level .htaccess rules, to WordPress-level user-agent matching, to robots.txt directives and HTML <meta> tags - giving you comprehensive coverage without requiring external services or API keys.

How It Works

Incoming Request


┌--------------------------┐
│  .htaccess layer (opt.)  │  ← Fastest - rejected before WordPress loads
└------------┬-------------┘
             │ (if not blocked by htaccess)

┌--------------------------┐
│  WordPress loads         │
│  ScraperBlock checks:    │
│  1. User-agent match     │  ← Against 50+ bot signatures
│  2. Rate limit check     │  ← Requests per minute threshold
│  3. Per-page rule        │  ← Page-specific override
└------------┬-------------┘
             │ Bot detected?
      ┌------┴------┐
     YES            NO
      │              │
      ▼              ▼
  Block (403)    robots.txt + meta noai
                 tags added to HTML output

ScraperBlock does not require WooCommerce or any third-party API. It works on any WordPress installation.


Requirements

RequirementMinimum
WordPress5.8
PHP7.4
Apache (for .htaccess blocking)2.4+
Write permission to .htaccessRequired for htaccess blocking

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