ZetaRank AI Agent Access Control
ZetaRank AI Agent Access Control
Description
Most “AI SEO” plugins guess. ZetaRank AI Agent Access Control gives you direct control.
It manages per-bot Allow/Disallow rules injected straight into your site’s robots.txt,
serves a dynamic /llms.txt summarizing your site for AI agents, and outputs baseline
JSON-LD structured data (WebSite + Article/WebPage) — all from one settings screen,
with no separate server or API key required.
What it does:
- Per-bot Allow/Disallow control for 20 known AI crawlers and agents, including GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, Claude-SearchBot, Google-Extended, PerplexityBot, Perplexity-User, Meta-ExternalAgent, Meta-ExternalFetcher, Applebot-Extended, Amazonbot, DuckAssistBot, MistralAI-User, CCBot, Bytespider, cohere-ai, anthropic-ai, and Diffbot
- Sensible defaults out of the box: training crawlers default to blocked, live “answer engine” crawlers default to allowed — edit any of them individually
- A dynamic
/llms.txtlisting your pages and recent posts, with an editable site summary - JSON-LD structured data on every page, describing your site and content for AI consumption
- Works entirely through WordPress’s native
robots_txtfilter and rewrite rules — no physical files written, no separate server
What this plugin won’t do: promise to “submit your site to ChatGPT.” No such public
mechanism exists. This plugin controls crawler access and machine-readable context —
which is the lever site owners actually have.
Want more?
MetaRankSEO Pro adds scheduled monitoring with alerts, site-wide schema audits (every
post/page, not just the homepage), IndexNow auto-submission on publish, and white-label
client reports for agencies. Learn more
Installation
- Upload the plugin files to
/wp-content/plugins/zetarank-ai-agent-access-control/, or install directly through the WordPress admin. - Activate the plugin through the ‘Plugins’ screen.
- Go to Settings ZetaRank AI Agent Access Control to review bot rules and enable llms.txt.
Faq
No — there’s no public API for that. This plugin controls whether your site is
reachable by AI crawlers and gives them a clean, structured entry point.
The plugin edits WordPress’s dynamic robots.txt via the robots_txt filter. If a
physical robots.txt file exists on your server, your webserver serves that file
directly instead, and this plugin’s rules never take effect. The admin page detects
this and gives you a ready-to-paste rules block to add to your physical file manually.
No — it relies on WordPress rewrite rules, which Plain permalinks don’t use. Switch to
any other permalink structure under Settings Permalinks.
No, it runs independently. If you already output WebSite/Article schema via another
plugin, you may want to disable the schema output here to avoid duplicate JSON-LD.
No meaningful impact — robots.txt and llms.txt are generated on request via core
WordPress hooks, and the schema output is a single small script tag.
Reviews
Changelog
1.1.0
- Added 4 AI bots to the registry: anthropic-ai, Meta-ExternalFetcher, DuckAssistBot, MistralAI-User.
- Added a warning when Plain permalinks are active, since /llms.txt requires pretty permalinks to resolve.
- Added full translation-string wrapping across the admin screen (text domain was declared but unused).
- Added uninstall.php to remove plugin settings on deletion.
1.0.0
- Initial release: per-bot robots.txt rules, dynamic llms.txt, JSON-LD schema output.