WordPress plugin intelligence profile

ddosNull AI Crawler & Scraper Blocker

Block GPTBot, ClaudeBot, Bytespider and 170+ AI crawlers and scrapers, bot by bot. Blocks by user agent and robots.txt. Optional daily list updates.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.1
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 5.5 · PHP 7.4
Directory statusactive
Last directory update5 Oct 202628d ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records ddosNull AI Crawler & Scraper Blocker version 1.0.1 as active, updated 28d ago and tested up to WordPress 7.1.

Overview

About this plugin

AI companies crawl the web to train their models, and some of them crawl hard. They take your content without asking, use up your server’s resources, and can slow your store down for real customers.

ddosNull AI Crawler & Scraper Blocker lets you decide, bot by bot, which AI crawlers get into your site. Everything is set up on activation. You don’t need to edit any files.

Features

  • 180+ known AI bots, each shown with its operator, purpose, crawl frequency, and whether it respects robots.txt.
  • One switch per bot to block or allow it. You can also block or allow every bot that matches a search or filter in one click.
  • Two layers of blocking:
  • Disallow rules are added to your robots.txt, so well-behaved crawlers stop visiting.
  • An HTTP 403 response goes to any request whose user agent matches a blocked bot. This also stops bots that ignore robots.txt.
  • Safe defaults. Major AI search engines, user-triggered assistants, and link-preview fetchers stay allowed, so your site still appears in ChatGPT, Perplexity, and Claude answers and in social link previews. Everything else is blocked. One click restores the recommended settings.
  • Bot list from the community-maintained ai.robots.txt project, bundled with the plugin and refreshed with each release. Optional daily updates (off by default) fetch new bots between releases. You choose what happens to newly discovered bots: block them unless they’re trusted, block them all, or allow them for manual review.
  • Blocked-request counters show which bots are hitting your site and when they last tried.
  • Search, filter, and sort by name, operator, category, robots.txt compliance, or number of blocked requests.
  • Fast. The check on each request is a single pattern match against a cached value. It adds no database queries to normal page views.
  • Light and dark mode.

Allowed by default

Blocking these services would hide your site from AI answers, shopping agents, or social shares, so they stay allowed unless you block them:

  • OpenAI: OAI-SearchBot, ChatGPT-User, ChatGPT Agent
  • Perplexity: PerplexityBot, Perplexity-User
  • Anthropic: Claude-SearchBot, Claude-User
  • Apple: Applebot (Siri, Spotlight, Safari). The AI-training opt-out, Applebot-Extended, is blocked.
  • Google: Google-Agent, GoogleAgent-URLContext. The AI-training opt-out, Google-Extended, is blocked.
  • DuckDuckGo: DuckAssistBot
  • Mistral: MistralAI-User
  • Amazon: Amzn-User, AmazonBuyForMe
  • Meta: facebookexternalhit (link previews on Facebook, WhatsApp, and Instagram), meta-externalfetcher

Search engines such as Googlebot and Bingbot are not AI crawlers and are never affected.

What user-agent blocking can’t do

This plugin stops bots that identify themselves. Many scrapers pretend to be a regular Chrome or Safari browser and rotate through thousands of IP addresses. The only way to catch those is by how they behave.

ddosNull Shield (free) detects bots by behavior and adds Layer-7 DDoS protection, without DNS changes. When both plugins are active, they work together:

  • Shield enforces your block and allow choices in its own firewall. In Shield’s Auto-Prepend mode, this happens before WordPress and your page cache load.
  • Your choices take priority over Shield’s built-in user-agent rules.
  • Allowed bots still pass through Shield’s IP reputation and DDoS checks. A scraper that pretends to be an allowed bot gains nothing.
  • Requests blocked by Shield still count toward the counters in this plugin.

External Services

txt project, which is hosted on GitHub. It only does so after an administrator turns on Automatic bot list updates in the plugin settings (off by default). Once enabled, the download runs once a day through WP-Cron, and also when you click the refresh icon on the settings page.

With the setting off, the plugin makes no external requests.

  • URL requested: https://raw.githubusercontent.com/ai-robots-txt/ai.robots.txt/main/robots.json
  • Data sent: a plain HTTP GET request. No site data or personal data is included beyond what every HTTP request carries: your server’s IP address and WordPress’s user agent.
  • Provider: GitHub, Inc. See its Terms of Service and Privacy Statement.
  • The list is published under the MIT license by the ai.robots.txt contributors.

The plugin makes no other external requests.

Privacy

This plugin does not store visitors’ IP addresses or any other personal data. For each bot it keeps only a count of blocked requests and the time of the most recent one.

Source Code

The settings screen is a React app. Its uncompiled source code is included in the admin-src/ folder. To build it, run cd admin-src && npm install && npm run build.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • bot blocker
  • robots txt
  • ai
  • crawler
  • robots.txt
  • scraper
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 5.5 · PHP 7.4
Update activity5 Oct 202628d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.