ScrapeLock – Content & AI Bot Protection
Most content protection plugins disable right click in the browser. Scrapers and AI crawlers don’t click or copy: they download the raw HTML, read the REST API and the feeds, or drive a (headless) browser. ScrapeLock works on the server, where automated copying actually happens, and leaves real visi
Most content protection plugins disable right click in the browser. Scrapers and AI crawlers don’t click or copy: they download the raw HTML, read the REST API and the feeds, or drive a (headless) browser. ScrapeLock works on the server, where automated copying actually happens, and leaves real visitors, customers and search engines alone.
- Runs on your own server. No account and no API key needed, and no visitor data sent anywhere by default. It downloads public IP lists; only if you turn on CDN blocking does it send the IPs it blocks to your own Cloudflare or Bunny account, with your API token (see External services).
- Starts in Monitor only. For its first 7 days a new install blocks nobody: requests that would be refused are logged as “Would block”, so you can see what it would do and adjust before it enforces. You can switch Monitor only on again at any time.
What it stops, and what it cannot
Who Result How
AI training crawlers that say who they are (GPTBot, ClaudeBot, CCBot, Bytespider…) Stopped Bot list, 403
Fake Googlebot or Bingbot Stopped Official IP lists plus reverse and forward DNS
Fast scrapers from one IP (IPv6: one /64) Stopped Per-IP limits and temporary blocks
Scanners asking for .env, .git or backups Stopped (optional) Ban on the first probe
Scrapers spread over many IPs Slowed Data center limit, surge email, Emergency Mode
Headless browsers on home connections Slowed Human check, bot trap, limits
Copying by hand, screenshots, logged-in scraping Cannot be stopped Watermark, source link and TDM leave traces
Attackers who can run PHP on your server Out of scope No plugin can stop them
Whatever a visitor sees has already reached their device, so nothing stops a determined human. ScrapeLock closes the automated routes and leaves traces.
Who it is for
- Publishers, recipe, course and news sites: block AI training but stay in AI search, keep post text out of the REST API, GraphQL and full-text RSS, TDM opt-out.
- WooCommerce shops: limits for the product catalogue (Store API too), cart actions and coupon attempts, private feeds for price comparison sites and Google Merchant.
- Photographers: watermarks with the clean originals kept, hotlink rules for Nginx, Apache and Cloudflare.