

Dashboard — AI Visibility Score ring with pillar breakdown and action checklist
AgentGarrison is an AI visibility toolkit for WordPress. It helps your site get discovered, understood, and cited by AI assistants such as ChatGPT, Perplexity, Gemini, and Claude, while giving you precise control over which AI crawlers can access your content.
Citation Monitor is the standout feature of AgentGarrison: it queries AI assistants for your target questions and reports whether your site is actually cited, with a per-competitor breakdown, so you can measure and track your AI visibility over time — not only publish signals for AI to read, but see the result.
It combines fifteen modules in one plugin: AI bot access control, AI agent control (Abilities/MCP governance for WordPress 7.1), read-only MCP content tools for AI agents, llms.txt generation with a built-in validator, Markdown output for AI agents, an AI-ready Q&A block, local bot analytics with a live activity feed, LLM referral tracking, an AI readability content scorer, structured data with E-E-A-T trust signals, a citation monitor, a honeypot bot trap, email reports, white-label reports, and a composite AI Visibility Score.
Everything runs on your own WordPress install: analytics, logs, and settings live in your own database, and every core feature works with no account and no external service. The only optional outbound calls — the Citation Monitor and the AI assists — use the WordPress 7.0+ core AI Client (or your own key); see External Services below.
Take back control of who can crawl your site. AgentGarrison ships with a built-in database of 26+ known AI bots across five categories — AI Trainers, AI Assistants, AI Search Engines, General Scrapers, and SEO Crawlers.
/robots.txt automatically via WordPress’s native filternoai, noimageai)robots.txt on first setup and maps it to the known bot list so no previous configuration is lostWordPress 7.1 mapped the Abilities API onto MCP, so AI agents can now run actions on your site — not just read it. Agent Control is the write/act counterpart to Bot Control: govern which Abilities agents may access over MCP (allow or block a whole category, or override individual Abilities — built on the core mcp_exposed_abilities filter, off by default so activation never disrupts an existing setup), and keep a local audit log of every Ability execution (Ability, who, source, outcome), pruned on your retention schedule. Dormant on WordPress 6.x; activates automatically once the Abilities API is present.
Let AI agents query your published content over the Model Context Protocol, using the standard WordPress Abilities API — no scraping. Registers three read-only tools (search content, fetch a page as clean Markdown, site overview) under the agentgarrison namespace, so Agent Control governs them alongside every other Ability. Only already-public content is exposed — drafts, private, password-protected, and llms.txt-excluded posts never are. Activates automatically on WordPress 6.9+; a no-op on older versions.
llms.txt is the emerging standard that tells AI models what your site is about and which pages matter most.
/llms.txt and /llms-full.txt — always up to date, no manual editing[name](url) hyperlink lists, exactly as the llms.txt standard (llmstxt.org) requiresLlms-txt: to your robots.txtServe clean, token-efficient Markdown to AI agents on your normal URLs. Runs entirely on your own site, free, on any host. Off by default; enable it in Settings, Modules.
Accept: text/markdown, AgentGarrison returns Markdown instead of HTML on the same canonical URL (the correct way, not a separate .md suffix that ignores the header). Roughly 5 to 6 times fewer tokens.<link rel="alternate" type="text/markdown"> tag and Link header, plus a bookmarkable ?rayetun_ag_md=1 URL, so agents can find the Markdown version.X-Markdown-Tokens header: lets agents budget context before reading.Vary: Accept so caches stay correct.A Gutenberg block for question-and-answer content, designed to be extraction-friendly for AI engines.
<details> element (no JavaScript required on the front end).Know exactly which AI systems are crawling your site, how often, and which pages they’re most interested in.
When someone asks ChatGPT a question and it recommends your article, that visitor clicks through to your site. AgentGarrison catches those visits.
AI models prefer content that is clear, well-structured, and fact-dense. The Content Scorer gives every post a 0–100 AI Readability Score across five dimensions:
Scores appear in a post editor sidebar metabox, an “AI Score” post list column, and a bulk dashboard with filtering and pagination. Fix the lowest-scoring posts first for the fastest gains.
Help AI models and Google understand your content with a connected JSON-LD @graph — nodes linked by @id the way Yoast and Rank Math do it, which LLMs parse best.
<details>/<summary> blocks, no shortcodes needed@graph for any post right in the adminA single composite 0–100 score — shown on the dashboard as a ring gauge — that reflects your overall AI-readiness across five pillars: Bot Access, llms.txt quality, Analytics activity, Content Quality, and Schema setup. Grade A–F at a glance with an actionable checklist to improve each pillar.
Every core AgentGarrison feature works entirely on your own server with no external requests. The only outbound connections are the optional, opt-in integrations below — none of them run unless you explicitly provide an API key.
The optional AI assists — “Suggest with AI” for your llms.txt summary, and “Get AI fixes” in the Content Scorer — use the same AI provider you configure below (the WordPress core AI Client on 7.0+, or your own key). They send only the relevant content (your site name and recent page titles, or the post you are editing) and only when you click the button.
On WordPress 7.0 and later, Citation Monitor uses the built-in core AI Client instead of the direct API calls below. In that case the site owner configures the AI provider once under Settings Connectors, WordPress core manages the credentials and the outbound request, and AgentGarrison does not send data to any AI provider directly. The direct integrations below apply only on WordPress 6.x, or when a core AI provider is not configured.
llms.txt Health Check — self-ping (not a third party)
The health check requests your own site’s /llms.txt URL using wp_remote_get() to confirm it is reachable. This is a request from your server to itself. No data is sent to any third party.
Anthropic (Claude) — Citation Monitor (optional)
Only used if you enter an Anthropic API key in Citation Monitor. When a scan runs, AgentGarrison sends your tracked questions to Anthropic’s Messages API to determine whether your pages are cited.
Data sent: your tracked question strings and your API key.
Sent when: only when an Anthropic API key is saved and a citation scan runs.
Service URL: https://www.anthropic.com
Terms of Service: https://www.anthropic.com/legal/consumer-terms
Privacy Policy: https://www.anthropic.com/legal/privacy
OpenAI (ChatGPT) — Citation Monitor (optional)
Only used if you enter an OpenAI API key in Citation Monitor. When the daily scan runs, AgentGarrison sends your tracked keywords to OpenAI’s Chat Completions API to determine whether your pages are cited.
Data sent: your tracked keyword strings and your API key.
Sent when: only when an OpenAI API key is saved and the daily citation scan runs.
Service URL: https://openai.com
Terms of Service: https://openai.com/policies/terms-of-use/
Privacy Policy: https://openai.com/policies/privacy-policy/
Perplexity — Citation Monitor (optional)
Only used if you enter a Perplexity API key in Citation Monitor. AgentGarrison sends your tracked keywords to Perplexity’s Chat Completions API and reads the returned citations.
Data sent: your tracked keyword strings and your API key.
Sent when: only when a Perplexity API key is saved and the daily citation scan runs.
Service URL: https://www.perplexity.ai
Terms of Service: https://www.perplexity.ai/hub/legal/terms-of-service
Privacy Policy: https://www.perplexity.ai/hub/legal/privacy-policy
On WordPress 7.0+, if you have configured an AI provider (such as Anthropic / Claude) under Settings Connectors, the Citation Monitor uses the built-in WordPress core AI Client instead of the direct API calls above. WordPress core manages the credential and the outbound request in that case.
Without any AI provider or API key, the Citation Monitor runs in Demo Mode and generates example citations from your own posts — no external requests are made.