| 开发者 | elis85 |
|---|---|
| 更新时间 | 2026年11月6日 14:34 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
docs/USER-MANUAL.md (site owners) and docs/DEVELOPER.md (hooks & architecture).
More from A-in
This plugin is complete on its own: no licence key, no locked features. Premium plugins, add-ons and support from the same developer are available at a-in.co.il.
No, with the default configuration. Search engines are allowed and DNS-verified, and throttling uses 429/503 with Retry-After, which search engines treat as "come back later".
Yes. Apply the "Protect content from AI training" preset. AI search and assistant agents stay allowed.
Not without blocking Google Search. AI Overviews use regular Googlebot. Google-Extended only controls Gemini training/grounding use.
No. It complements them. Large DDoS attacks must be stopped before they reach PHP.
No. Out of the box it makes no outgoing requests: search engine bots are verified with DNS lookups through your own server's resolver. Two features can download data, and both are off until you turn them on in the Bot Lists tab: the official crawler IP lists (from Google, Bing, Apple, OpenAI and Perplexity) and a bot-list feed URL of your own. See "External services" below for exactly what is requested.
OpenAI and Perplexity bots have no reverse DNS, so without their published IP lists All-IN Crawler & AI Agent Manager can't tell a real GPTBot or PerplexityBot from a scraper using the same name; they stay "unverified". With the lists on, a request claiming to be one of those bots from an unlisted IP is treated as an impostor. A list is only used while it is fresh (under 7 days old), so a failed download never blocks a genuine bot.
Pages served from a full-page cache don't run WordPress, so All-IN Crawler & AI Agent Manager doesn't see them. Those requests are cheap anyway. Denials are sent with Cache-Control: no-store and are never cached.
data/bots.json) are bundled and always used; no network request is needed for them.