| 开发者 | codeforbroke |
|---|---|
| 更新时间 | 2026年10月3日 03:06 |
| PHP版本: | 6.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
Disallow rules for more than 30 known AI user agents to the robots.txt that WordPress already serves. Nothing is blocked until you choose. Block every one of them, or go down the list and pick only the ones you want to keep out. Each crawler comes with a short note on who runs it and what it's for, so you're never guessing.
What you get
noai, noimageai meta tag on every page, for crawlers that look for it.yoursite.com/robots.txt to see your new rules.robots.txt file sits in your site's root folder, see the FAQ below.No. Googlebot, the crawler behind Google Search, isn't on the list. Google-Extended only controls whether your content is used for Google's AI products like Gemini; Google says blocking it doesn't affect your Search ranking.
It can. Bots like OAI-SearchBot and PerplexityBot fetch pages so AI search tools can cite them. Block them and those tools are less likely to link to you. If that traffic matters to you, leave those two allowed and block the training crawlers.
Not while that file is there. When a physical robots.txt exists in your site's root folder, your server sends it directly and WordPress never gets the chance to add rules. AI Deny checks for this when you activate it. Copy any custom rules you need into WordPress, then remove the file and let AI Deny handle the rest.
It blocks every crawler that respects robots.txt, which includes the major AI companies' published crawlers. A bot that ignores robots.txt has to be blocked at the server or CDN level.
Visit yoursite.com/robots.txt. You'll see a User-agent and Disallow: / pair for each crawler you've blocked.
Let me know in the support forum and I'll look at adding it.