| 开发者 | ddosnull |
|---|---|
| 更新时间 | 2026年10月5日 21:45 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0+ |
| 版权网址: | 版权信息 |
Disallow rules are added to your robots.txt, so well-behaved crawlers stop visiting.OAI-SearchBot, ChatGPT-User, ChatGPT AgentPerplexityBot, Perplexity-UserClaude-SearchBot, Claude-UserApplebot (Siri, Spotlight, Safari). The AI-training opt-out, Applebot-Extended, is blocked.Google-Agent, GoogleAgent-URLContext. The AI-training opt-out, Google-Extended, is blocked.DuckAssistBotMistralAI-UserAmzn-User, AmazonBuyForMefacebookexternalhit (link previews on Facebook, WhatsApp, and Instagram), meta-externalfetcherNo. Googlebot and Bingbot are not in the list. Google-Extended is only a robots.txt token that tells Google not to use your content for Gemini training. Blocking it does not affect Google Search.
Yes, with the default settings. Their search crawlers and user-triggered fetchers are allowed. Only their model-training crawlers, such as GPTBot and ClaudeBot, are blocked.
User-agent blocking only stops bots that identify themselves honestly. A scraper that pretends to be a browser needs behavioral detection, such as ddosNull Shield. Pretending to be one of the allowed AI bots gains a scraper nothing, because a browser user agent would already get it through.
Yes, on purpose. robots.txt is always served, so compliant crawlers can read your rules and stop visiting.
Your web server serves a physical robots.txt file directly, so WordPress can't add rules to it. The settings page warns you when one exists. You can delete or rename the file, or copy the rules into it by hand. User-agent blocking works either way.
Page caches can serve a stored copy of a page before WordPress plugins run. In that case a blocked bot may receive the cached page, although the robots.txt rules still apply. With ddosNull Shield in Auto-Prepend mode, bots are blocked before the cache loads. Pages cached at a CDN edge (for example, Cloudflare's "Cache Everything") never reach your server, so no WordPress plugin can block those requests.
A copy of the list ships with the plugin and is refreshed with every plugin release, so protection works from the first second without any external requests. To get new bots between releases, turn on Automatic bot list updates under Settings → AI Crawler Blocker. The plugin then downloads the list once a day through WP-Cron, and you can click the refresh icon to check right away. This setting is off by default.
It stays in your list with your setting, labeled "Removed upstream".
Yes. Developers can adjust the list with the aicsb_trusted_bots filter. You can also block or allow any individual bot from the settings page.
Uninstalling removes the plugin's database table and all its settings. Deactivating keeps your settings and stops all blocking.