WordPress plugin intelligence profile

Spuncin

Blocks AI crawlers that collect your content to train models. Search engines and link previews are never touched.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version0.1.0
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 6.4 · PHP 7.4
Directory statusactive
Last directory update1 Sept 20262mo 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 Spuncin version 0.1.0 as active, updated 2mo ago and tested up to WordPress 7.0.

Overview

About this plugin

Spuncin turns away the crawlers that harvest your content to train AI models, and leaves everything that brings you readers alone.

It works on two levels at once, because one is not enough. txt, so a polite opt-out is all you need. Others ignore it entirely, and only a real refusal stops them.

Spuncin writes the opt-out and returns a 403, so both cases are covered.

You choose how strict

Three levels, each one including the previous. The settings page explains what each costs you, so you can decide with the facts in front of you.

  • Training only (recommended). Blocks GPTBot, ClaudeBot, Common Crawl, ByteDance and the rest of the crawlers that feed model training. Your Google ranking is untouched and you lose no visitors.
  • Training and AI search. Also blocks PerplexityBot and the ChatGPT Search crawler. Your site stops being cited in their answers, and those citations carry clickable links today, so this costs you something.
  • Everything except search engines. Also blocks the requests an assistant makes when a person asks it to open one of your pages. On the other side of those is a real reader.

Below the levels there is a full list with a checkbox per crawler, for when the level is not quite what you want.

What is never blocked

Google, Bing and the other search engines are always allowed, verified by reverse DNS so nobody gets through by copying a user agent. The same goes for the bots that build the preview when someone shares your link on Facebook, WhatsApp or elsewhere. Blocking those does damage that takes months to undo, so Spuncin does not offer it as an option.

The part nobody else tells you

Two of the most useful opt-outs are not crawlers at all. Google-Extended and Applebot-Extended have no user agent of their own: Google states that Google-Extended “doesn’t have a separate HTTP request user agent string”, and Apple says Applebot-Extended “does not crawl webpages itself”. txt.

A plugin that only inspects user agents can never act on them, whatever it claims. txt, which is the only thing that works.

Honest about the limits

Spuncin blocks crawlers that identify themselves. A scraper pretending to be Chrome is a different problem, and solving it needs tools that sit in front of PHP entirely. We would rather say so than promise something the plugin cannot do.

The list holds 154 known crawlers. On a normal blog you will see a dozen of them; the rest are in there because it costs nothing to keep them.

Privacy

Data collected. When a crawler is turned away, Spuncin adds one to a daily counter for that crawler’s name. Nothing else is recorded.

No IP address, no user agent string, no requested URL, no per-request rows.

External services. None. Spuncin does not connect to any third-party service and sends nothing anywhere.

Cookies. None.

Network traffic. When a request claims to be a search engine, Spuncin performs a reverse DNS lookup on the connecting IP to confirm it. That is a DNS query from your own server, sent to your server’s resolver, and it happens only for requests that already match a blocked crawler.

Credits

txt. How each crawler is categorised, and therefore what gets blocked at which level, is Spuncin’s own work: the upstream list is a catalogue of AI-related crawlers, not a list of things that should be blocked.

WordPress.org metadata

Plugin tags

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

  • ai
  • bots
  • crawler
  • privacy
  • robots
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 6.4 · PHP 7.4
Update activity1 Sept 20262mo 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.