Block AI Crawlers Plugin vs WebDecoy
The Block AI Crawlers WordPress plugin vs WebDecoy: a robots.txt list vs robots.txt rules plus counts of which AI crawlers visit and a switch to refuse them.
Block AI Crawlers is a simple, focused WordPress plugin: install it and your robots.txt asks AI crawlers to stay away. If that is all you want, it does the job. This page compares it with WebDecoy, a free plugin that writes robots.txt rules too, and also shows you which AI crawlers actually visit and can refuse the ones that ignore robots.txt. Facts about Block AI Crawlers come from its WordPress.org listing; facts about WebDecoy come from the plugin’s source.
Short version: Block AI Crawlers sends a polite request. WebDecoy sends the same kind of request, then shows you who listened, and lets you refuse the rest.
What each one is
Block AI Crawlers
From its WordPress.org listing (version 1.6.3, 2,000+ active installations):
- robots.txt rules: it “tells AI companies not to crawl your site for their products via standard robots.txt rules”, naming crawlers from OpenAI, Google, Meta, Anthropic, Perplexity, Apple and Amazon, “and 150+ more via ai.robots.txt”.
- A noai meta tag: an optional, experimental “noai, noimageai” directive in your pages’ meta tags.
- Per-crawler toggles (added in 1.6.0) to opt individual bots out of the robots.txt block.
- Free, with no paid tier listed.
What the listing says it does not do, or cannot do:
- It “cannot guarantee complete protection”, because “some bots may disregard robots.txt directives”.
- If your server has a physical robots.txt file, you cannot activate the plugin.
- It requires WordPress 7.0 or higher and PHP 8.2 or higher.
- The listing describes no reporting of crawler visits.
WebDecoy WordPress plugin
WebDecoy is free, runs on your own server, and needs no account or API key. For AI crawlers it:
- Writes robots.txt rules by category: choose categories such as AI training crawlers, SEO tools or commercial scrapers, and it adds a rule for every known crawler in them. One click covers the 32 AI training crawlers it knows by name, including GPTBot, ClaudeBot, CCBot and Google-Extended. The list stays current with each plugin update, your sitemap lines and other plugins’ rules stay as they are, and you can see the exact rules in settings. It is off until you choose categories.
- Refuses AI crawlers outright with the Block AI crawlers setting: AI training crawlers and AI agents (GPTBot, ClaudeBot, Bytespider, CCBot and others) are refused, including ones that ignore robots.txt. Search engines are unaffected, and AI search crawlers such as PerplexityBot and OAI-SearchBot stay allowed.
- Shows who visits: an AI Traffic & Analytics page with 7- and 30-day views of known crawlers and AI agents, each with its operator and type, plus a dashboard widget for the last 24 hours.
- Checks the big crawlers are real: Googlebot, Bingbot, Applebot, DuckDuckBot, Yandex, Baidu and the major social crawlers are checked with reverse and forward DNS, so an impersonator is flagged.
- Counts visits from AI assistants: ChatGPT, Perplexity, Claude, Gemini, Copilot and others, by AI product and landing page. Only a daily count is kept.
Side by side
| Block AI Crawlers | WebDecoy | |
|---|---|---|
| Price | Free | Free |
| Account | None | None |
| robots.txt rules for AI crawlers | Yes, from the ai.robots.txt list | Yes, by category, from WebDecoy’s registry |
| Choose individual crawlers | Per-crawler toggles | By category |
| Other categories (SEO tools, scrapers) | Not described | Yes |
| noai meta tag | Yes, optional | No |
| Refuse crawlers that ignore robots.txt | No | Yes, Block AI crawlers setting |
| See which crawlers visit | Not described | Yes, 7- and 30-day views |
| Check a crawler is genuine | Not described | Reverse and forward DNS for search and social crawlers |
| Count visits from AI assistants | Not described | Yes |
| Physical robots.txt file | Will not activate | Activates, shows the rules to copy in |
| Requires | WordPress 7.0+, PHP 8.2+ | WordPress 6.1+, PHP 7.4+ |
Where Block AI Crawlers is better
- Simplicity. It does one thing. If you want a robots.txt list and nothing else in wp-admin, it is lighter than a plugin that also counts traffic and protects forms.
- Per-crawler control. You can opt out individual crawlers. WebDecoy’s robots.txt rules work by category.
- The noai meta tag. If you want that directive in your pages, Block AI Crawlers adds it. WebDecoy does not.
- A community-maintained list. It draws on ai.robots.txt, an open list of AI crawler names.
What WebDecoy adds
- Proof, not just a request. robots.txt is voluntary. After you add rules, WebDecoy’s AI Traffic page shows whether GPTBot, ClaudeBot and the rest are still arriving, and how often.
- A real refusal. For crawlers that ignore robots.txt, the Block AI crawlers setting refuses them inside WordPress, without touching search engines.
- Impersonator checks. A scraper calling itself Googlebot from an address that fails Google’s DNS check is flagged, not trusted.
- The other side of AI traffic. Blocking AI training is half the decision. WebDecoy also counts the visitors ChatGPT, Perplexity, Claude and others send you, by landing page, so you can see what you might give up.
Two honest limits. First, the plugin only sees requests that reach WordPress: pages served from a page cache are not counted or refused. Since version 2.15.0 it tells you when a cache is hiding crawler visits, and an optional setting lets known crawlers skip WP Super Cache, W3 Total Cache, LiteSpeed Cache or WP Rocket. Second, refusing a request inside WordPress still uses your server; blocking at a CDN or firewall happens earlier.
Which to choose
- You only want a robots.txt list, with per-crawler control or the noai tag: Block AI Crawlers.
- You want to see which AI crawlers visit, refuse the ones that ignore robots.txt, and count what AI assistants send you: WebDecoy.
- Not both for robots.txt. Two plugins writing AI crawler rules into the same robots.txt is harder to reason about. Pick one to own it.
Related reading: Block AI crawlers in WordPress without editing robots.txt and Understand your AI traffic in WordPress, without an account.
Get started
Install WebDecoy free from WordPress.org. Choose your robots.txt categories under Settings > Good Bots, then watch the AI Traffic page to see who listens.
Frequently Asked Questions
What does the Block AI Crawlers plugin do?
Per its WordPress.org listing, it adds rules to the robots.txt WordPress serves, asking AI crawlers from OpenAI, Google, Meta, Anthropic, Perplexity, Apple, Amazon and 150+ more (via the ai.robots.txt list) not to crawl your site. It can also add an experimental noai, noimageai meta tag, and since version 1.6.0 lets you opt individual crawlers out of blocking.
Does robots.txt actually stop AI crawlers?
Only the ones that choose to follow it. Block AI Crawlers' own listing says it cannot guarantee complete protection because some bots may disregard robots.txt. WebDecoy writes robots.txt rules too, and adds a Block AI crawlers setting that refuses AI training crawlers and AI agents outright, including ones that ignore robots.txt, for requests that reach WordPress.
Can I see whether AI crawlers are still visiting after I block them?
Not with Block AI Crawlers; its listing describes no visit reporting. WebDecoy counts known crawler visits on your server, by bot and by day, over 7 or 30 days, so you can see which crawlers still come after you add robots.txt rules.
Will blocking AI crawlers hurt my search rankings?
Neither plugin blocks search engines. Block AI Crawlers' FAQ says it will not stop search engines indexing your site. WebDecoy's Block AI crawlers setting leaves search engine crawlers alone, and AI search crawlers such as PerplexityBot and OAI-SearchBot are treated like search engines and stay allowed.
What if my server has a physical robots.txt file?
Block AI Crawlers' listing says you cannot activate it if a physical robots.txt file exists. WebDecoy activates either way; WordPress cannot add to a physical file, so WebDecoy's settings page tells you and shows the rules to copy into it.
Need help choosing a bot protection solution?
Our team can help you compare options and find the right fit for your needs.