Title: Agentimus – AI SEO, llms.txt & MCP for AI Agents
Author: Sheikh Heera
Published: جون 22, 2026
Last modified: اگست 2, 2026
---
پلگ ان ڳولو
# Agentimus – AI SEO, llms.txt & MCP for AI Agents
[Sheikh Heera](https://profiles.wordpress.org/heera/) کنوں
[ڈاؤن لوڈ](https://downloads.wordpress.org/plugin/agentimus.1.33.0.zip)
* [تفصیلاں](https://skr.wordpress.org/plugins/agentimus/#description)
* [ریویو](https://skr.wordpress.org/plugins/agentimus/#reviews)
* [انسٹال کرݨ](https://skr.wordpress.org/plugins/agentimus/#installation)
* [ڈیویلپمنٹ ](https://skr.wordpress.org/plugins/agentimus/#developers)
[معاونت](https://wordpress.org/support/plugin/agentimus/)
## تفصیل
Agentimus is an all-in-one AI SEO plugin for the age of AI agents — AEO (Answer
Engine Optimization) and GEO (Generative Engine Optimization) in one place. It does
two things.
**It makes your site legible and citable.** It helps AI assistants like ChatGPT,
Claude and Perplexity find your site, read it correctly, and cite it in your own
words — and shows you which AI bots are actually visiting. **You don’t need to understand
AI or web standards to use it:** a setup wizard walks you through everything in
about a minute, then it runs on its own.
**And it lets the AI tools you already use operate your site.** Turn on the built-
in Model Context Protocol (MCP) server and Claude Code, Claude Desktop, Cursor or
Codex can read your reports and — behind two more opt-in switches — **draft, edit
and publish posts** for you, every write running as the signed-in user, permission-
checked and audited. All three switches are off by default. Prefer to stay in wp-
admin? A built-in **writing assistant** drafts and revises posts there. (Full details
below.)
You also get a first-party log of the AI crawlers reading you, one-click blocking,
and an AEO/GEO readiness score that always names the next fix.
By default it makes no outbound requests, collects no analytics, and logs no IP
addresses — everything runs on your own site. Three optional, off-by-default features
change that only when you enable them: **AI Visibility**, **Verify bot identities**
and **Store IP addresses** (each disclosed in full under _External services_).
**📖 Full documentation** — a plain-English manual and developer reference, step-
by-step guides for every feature: https://heera.github.io/agentimus/
**With an SEO plugin — or instead of one**
* **No SEO plugin? You don’t need one.** Agentimus covers the search basics itself:
per-page SEO titles, social share cards (Open Graph), canonical links, meta descriptions,
and an XML sitemap that carries the last-changed dates core’s own leaves out.
* **Already running Yoast, Rank Math, SEOPress, AIOSEO or The SEO Framework?**
Agentimus detects it and steps aside on every overlapping surface — titles, cards,
schema, sitemap — automatically. No duplicate tags, ever: it adds only the AI
layer your SEO plugin doesn’t cover.
**Operate your site from your AI agent (MCP) — opt-in**
* **A Model Context Protocol server on your own site** — one switch (Settings
Discovery) runs an MCP server at `/wp-json/agentimus/v1/mcp`; the whole library
ships with the plugin, nothing extra to install.
* **Connect by approving, not by pasting keys** — an assistant asks _you_ for permission
on a consent page on your own site; you choose **Read only** or **Read and write**,
and each approved assistant gets its own key and its own Disconnect. Standards-
based (OAuth 2.1 with PKCE), nothing brokered by a third party; a revocable **
shared token** covers clients that can’t ask.
* **Read your site’s data** — connected agents run the read-only tools (readiness/
AEO-GEO score, AI traffic, request log, bot identification, page / JSON-LD /
Markdown previews) — the same ones WordPress’s built-in AI gets.
* **Draft, edit and publish posts — behind two more switches** — turn on **Let
connected agents write** and the agent can create and edit posts and pages fully
dressed (categories, tags, featured image, AI topics and descriptions) and apply
Readiness fixes; turn on a third switch and it may publish, otherwise it leaves
drafts for your review.
* **Safe by construction** — every write runs as the signed-in WordPress user,
never exceeding their permissions, and is recorded under **More Agent Access**.
Nothing is public, and with the write switch off the write tools don’t exist
on any surface. All three switches are off by default.
**Write with AI in wp-admin — the built-in assistant (opt-in)**
* **Idea draft without leaving wp-admin** — a quill button opens the writing assistant:
describe the post, edit the outline it proposes, and preview the complete draft—
real editor blocks, AI description, topics, categories, tags. Nothing is saved
until you click **Create draft**, and it never publishes.
* **Edit existing posts** — describe the change and it revises the content; a post’s
status never changes, and WordPress revisions keep every prior version.
* **Images where you write** — alt-filled placeholders in drafts, **Generate image
from the alt text** on every image block, a **Featured image (AI)** sidebar panel—
or pick from your library.
* **Ask AI on any block** — rewrite, shorten or extend any block with one instruction;
undo brings it back. Everything runs on WordPress’s built-in AI Client (7.0+,
Settings AI — Agentimus never sees your key), and every AI button hides until
a provider is set up.
**Control — who may use your content**
* **robots.txt content-signals + AI-training blocklist** — declare your content-
usage policy and block named model-training crawlers (GPTBot, CCBot, ClaudeBot,
Google-Extended, Bytespider, …) by name, while leaving read/cite bots free.
* **Block scanners & scrapers (opt-in hard block)** — robots rules are a polite
request; this enforces them, returning 403 to the user-agents on your denylist.
Your **always-allowed** list is never blocked: pre-trust well-known AI assistants
with one click; major search engines are recognised automatically, and SSL-renewal
requests always stay reachable.
**Reduce exposure — what your site reveals to bots**
* **Exposure controls (opt-in, all OFF by default)** — switches that quietly close
what stock WordPress reveals to anonymous crawlers: username enumeration, author
archives, the WordPress version, the auto-generated `` discovery links,
and XML-RPC. Nothing changes until you turn one on, and signed-in admins and
the block editor are never affected. Exposure hygiene, not a firewall.
**Visibility — who is reading you**
* **Agent activity log** — a dashboard of which AI crawlers and agents actually
fetch your content and endpoints (GPTBot, Claude, Perplexity, Googlebot, …),
recorded first-party in your own database, with no IP logging by default (an
optional setting stores IPs for flagged crawlers only).
* **Activity to review** — a nav-bar queue surfaces clients worth a second look—
new, unusually high-volume, or spoofing — with one-click **Block** or **Allow**.
Nothing is blocked unless you choose to.
* **Request Log** — every recorded request, one row each, under _More Request
Log_. Filter by client, endpoint, network, user-agent and date to see exactly
what a single bot fetched.
* **Agent Access** — the other side of the log: who _authenticates to and acts
on_ the machine surface (_More Agent Access_): assistants approved, keys created
or revoked, abilities run, requests refused. A record, not a guard — it names
the key used, never the person.
* **Traffic from AI** — the mirror of the crawler log: the real visitors an AI
assistant sent you, day by day, by assistant and by landing page (_More AI Traffic_)—
daily aggregate counts, never a row for one person, no IP. An opt-in **CDN mode**
keeps counts accurate behind a full-page cache.
* **Edge traffic (Cloudflare, opt-in)** — what Cloudflare answered or blocked _before
your server ever saw the request_ — the cache hits and edge blocks no server-
side log can see — read with your own token, and it warns when the edge disagrees
with your policy.
* **You decide how long it’s kept** — retention, nightly auto-delete, and a hard
size cap that always applies, so the log can never outgrow your host.
* **AI Visibility (opt-in)** — track **each brand, product or person you choose**
across ChatGPT, Perplexity, Gemini and Claude: whether it gets **mentioned, linked,
and how it ranks against its rivals** — over time, against the questions your
audience actually types. Off by default; **you bring your own API key** (the
one feature that makes an outbound request — see _External services_).
**Classic search, measured — Bing & Google (opt-in)**
* **Search Performance & Opportunities** — connect Bing Webmaster Tools and/or
Google Search Console (a key held on your own server, no third-party proxy) and
see what people searched, how often you appeared, and which pages sit one improvement
from page one. Every number is the engine’s own — never estimated — and automated
probe traffic is named, not blended in.
* **In Google’s Index / Found by AI Search** — whether the indexes behind AI Overviews,
Gemini, ChatGPT search and Copilot actually hold your pages: a daily watchlist
plus a whole-site rotation, every verdict in the engine’s own words, problems
grouped with deep links to where the fix lives, any page’s answer one lookup
away — plus week-on-week trend, Google Discover, and the health of the sitemap
you registered.
**Content — clean, machine-readable output**
* **Markdown delivery** — request any page as clean markdown by appending `.md`
to its URL. (An `Accept: text/markdown` mode also exists, off by default.)
* **/llms.txt** & **/llms-full.txt** — an [llmstxt.org](https://llmstxt.org) index
of your pages, topics and recent posts, plus a full-text edition an agent can
ingest in a single request.
* **JSON-LD** — WebSite + Person/Organization, plus BlogPosting and BreadcrumbList
on posts. Automatically **defers to Yoast, Rank Math, SEOPress, AIOSEO and The
SEO Framework** so you never ship duplicate schema.
* **Topics for AI** — say what each post is about in plain words, right in the
editor; those topics become the JSON-LD `keywords` and a line in the page’s `.
md`, so assistants understand each page’s subject. Type your own, or let Agentimus
fill them in from the post’s own tags and categories. Nothing shows on the visible
page.
* **AI description** — write a one-line summary of each post in the editor; it
becomes the JSON-LD `description`, the lead of the page’s `.md`, and the page’s`
` (replacing your theme’s, unless an SEO plugin owns
it). Blank falls back to the excerpt. A sub-switch can keep it out of your `<
head>`.
* **XML sitemap** — with no SEO plugin, Agentimus serves your sitemap (index +
paginated sub-sitemaps, with last-changed dates) at WordPress’s standard `/wp-
sitemap.xml` address — old addresses redirect, so a search-console registration
never goes stale — and advertises it in robots.txt and llms.txt; with one installed,
it links theirs instead.
* **Change feed** — a JSON feed at `/agentimus-changes.json` lists recently added,
updated and removed pages (with a `?since=` filter), so an assistant re-checks
only what changed. On by default, advertised in discovery.
**Identity & contact**
* **Author / site identity** — a profile sentence, expertise topics and linked
profiles (`sameAs`) feed llms.txt and JSON-LD — the highest-signal lines for
agent retrieval.
* **security.txt** — optionally publish an RFC 9116 disclosure contact at `/.well-
known/security.txt`.
**Readiness report**
* A one-screen score of how machine-readable your site is, with a plain-English
checklist of what’s enabled and what’s still missing.
* **Agent preview** — open it from the Readiness tab to see the exact JSON-LD _and_
Markdown an AI agent receives for the whole site or any page, then copy it. It
shows what would ship even when the feature is off, and a matching read-only
preview sits in the post editor.
* **AI Readability tips** — as you write, a panel flags what makes a page hard
for an assistant to read and cite: thin content, missing headings, no opening
summary, a nav-heavy page, images without alt text. Editor-only — nothing shows
to visitors.
**Machine discovery (forward-looking)**
Agentimus also publishes a single, normalized discovery document — the conventions
the agent ecosystem is converging on (`.well-known`, A2A agent cards, MCP-shaped
tools) — putting identity, capabilities and APIs in one predictable place:
* **/.well-known/discovery.json** — an owner-curated document describing the site’s
identity, capabilities, APIs and agent cards. Other plugins can declare themselves
through one optional hook.
* **/.well-known/agent-card.json** and **/.well-known/mcp.json** — an A2A agent
card and an MCP manifest, generated automatically.
* **Standards-aligned `.well-known` endpoints** — an RFC 9727 `api-catalog`, plus—
_only when the capability actually exists_ — an MCP server card and an Agent
Skills index. Optional **response signing** (Web Bot Auth / HTTP Message Signatures,
RFC 9421) signs the discovery documents with an Ed25519 key so agents can verify
they came from you; on by default, and the private key stays on your server.
* **WordPress Abilities API** — Agentimus registers its own **read-only abilities**(
readiness/AEO-GEO score, AI traffic, request log, bot checks, and page / JSON-
LD / Markdown previews), so WordPress’s built-in AI — and, with the MCP adapter,
external agents — can read them, each gated by the same capability as its screen.
A separate, off-by-default switch adds the write abilities above.
* **Zero-config auto-discovery** — reads your REST namespaces, public post types
and the Abilities API, so a site is described even when no plugin declares itself;
the **Discovery Hub** screen shows what an agent sees, and you decide what is
published.
**What’s read today vs. what it readies you for**
The content signals above are read by search engines and AI tools **today**; the
discovery document is **forward-looking**, preparing your site for agents as they
adopt these conventions.
**Why it’s useful**
Most tools cover one slice — an llms.txt file, a bot blocker, or structured data.
Agentimus brings the whole job together in one lightweight package — and tells you
what’s still missing.
### External services
Agentimus makes no outbound requests by default: no remote scripts, fonts or analytics,
and the agent-activity log stays in your own database with no IP addresses. (IP
storage is optional, off by default — see the FAQ.)
**Two opt-in features go outbound; both are off by default.**
**Verify bot identities** makes DNS lookups and, once a day, downloads the IP-range
files bot operators publish to verify their crawlers (Google, Microsoft, DuckDuckGo,
Apple, OpenAI, Perplexity — or a URL you add yourself). Only those files are fetched;
nothing about your site is sent.
The same setting verifies **Web Bot Auth** signatures — the standard where an AI
agent signs its request cryptographically. To check one, Agentimus fetches (and
caches) the signing operator’s **public key directory** at `/.well-known/http-message-
signatures-directory`, only when a signed request arrives, and sends nothing about
your site with it. Operators publishing one today:
* **OpenAI** — https://chatgpt.com/.well-known/http-message-signatures-directory·
https://openai.com/policies/terms-of-use · https://openai.com/policies/privacy-
policy
* **Google** — https://agent.bot.goog/.well-known/http-message-signatures-directory·
https://policies.google.com/terms · https://policies.google.com/privacy
**AI Visibility:** when you enable it and add your own API key for a provider, Agentimus
sends the prompts you configured to that provider to check whether it mentions and
cites your site — only for the engines you turn on, and only when a check runs.
Your keys are stored on your own site and used solely for these calls. The providers,
with their terms and privacy policies:
* **OpenAI (ChatGPT)** — https://openai.com/policies/terms-of-use · https://openai.
com/policies/privacy-policy
* **Perplexity** — https://www.perplexity.ai/hub/legal/terms-of-service · https://
www.perplexity.ai/hub/legal/privacy-policy
* **Google (Gemini)** — https://ai.google.dev/gemini-api/terms · https://policies.
google.com/privacy
* **Anthropic (Claude)** — https://www.anthropic.com/legal/consumer-terms · https://
www.anthropic.com/legal/privacy
URL-like strings in the plugin’s output are labels, not requests — the discovery
documents’ `$schema` value names the format (never fetched), and the `example.com`
URLs in `examples/` are documentation placeholders.
## سکرین شاٹاں
[⌊Dashboard — your AEO/GEO score across five plain rungs (Findable, Readable, Trusted,
Optimized, Cited) with the one next step worth taking, alongside a first-party log
of which AI agents and crawlers fetched your endpoints, who reads you most, and
the real visitors AI assistants sent. Every day bar opens that day's full report.⌉⌊
Dashboard — your AEO/GEO score across five plain rungs (Findable, Readable, Trusted,
Optimized, Cited) with the one next step worth taking, alongside a first-party log
of which AI agents and crawlers fetched your endpoints, who reads you most, and
the real visitors AI assistants sent. Every day bar opens that day's full report
.⌉[
Dashboard — your AEO/GEO score across five plain rungs (Findable, Readable, Trusted,
Optimized, Cited) with the one next step worth taking, alongside a first-party log
of which AI agents and crawlers fetched your endpoints, who reads you most, and
the real visitors AI assistants sent. Every day bar opens that day’s full report.
[⌊In Google's Index — whether Google's index actually holds your pages: a daily
watchlist (homepage, busiest pages, newest posts) with every verdict in Google's
own words, then the whole site in rotation — healthy pages as a count, problems
as rows grouped by state, each with a Search Console link. The index behind classic
Google Search and AI Overviews, AI Mode and Gemini alike.⌉⌊In Google's Index — whether
Google's index actually holds your pages: a daily watchlist (homepage, busiest pages,
newest posts) with every verdict in Google's own words, then the whole site in rotation—
healthy pages as a count, problems as rows grouped by state, each with a Search
Console link. The index behind classic Google Search and AI Overviews, AI Mode and
Gemini alike.⌉[
In Google’s Index — whether Google’s index actually holds your pages: a daily watchlist(
homepage, busiest pages, newest posts) with every verdict in Google’s own words,
then the whole site in rotation — healthy pages as a count, problems as rows grouped
by state, each with a Search Console link. The index behind classic Google Search
and AI Overviews, AI Mode and Gemini alike.
[⌊Search Performance — what people searched, how often you appeared, how often those
results were clicked, and the pages that earned them. Every number is the engine's
own; connect both Google and Bing and a switch appears, because the two count different
searchers and are never merged. Searches that are really scraper probes are marked,
not hidden.⌉⌊Search Performance — what people searched, how often you appeared,
how often those results were clicked, and the pages that earned them. Every number
is the engine's own; connect both Google and Bing and a switch appears, because
the two count different searchers and are never merged. Searches that are really
scraper probes are marked, not hidden.⌉[
Search Performance — what people searched, how often you appeared, how often those
results were clicked, and the pages that earned them. Every number is the engine’s
own; connect both Google and Bing and a switch appears, because the two count different
searchers and are never merged. Searches that are really scraper probes are marked,
not hidden.
[⌊Readiness report — a plain-English pass/warn checklist of what's enabled and what's
still missing, and beneath it the Optimize worklist: exactly which posts and pages
an answer engine would struggle to quote, and why. Set aside anything not meant
to be cited, page by page or a whole check at once.⌉⌊Readiness report — a plain-
English pass/warn checklist of what's enabled and what's still missing, and beneath
it the Optimize worklist: exactly which posts and pages an answer engine would struggle
to quote, and why. Set aside anything not meant to be cited, page by page or a whole
check at once.⌉[
Readiness report — a plain-English pass/warn checklist of what’s enabled and what’s
still missing, and beneath it the Optimize worklist: exactly which posts and pages
an answer engine would struggle to quote, and why. Set aside anything not meant
to be cited, page by page or a whole check at once.
[⌊Crawler policy & bot identity — declare your content-usage signals, block AI-training
crawlers by name, turn away spoofed traffic, and verify bots against what each operator
publishes: reverse DNS for the search engines, published IP ranges for GPTBot and
PerplexityBot, cryptographic signatures for agents that sign. The verified-bots
registry is yours to edit.⌉⌊Crawler policy & bot identity — declare your content-
usage signals, block AI-training crawlers by name, turn away spoofed traffic, and
verify bots against what each operator publishes: reverse DNS for the search engines,
published IP ranges for GPTBot and PerplexityBot, cryptographic signatures for agents
that sign. The verified-bots registry is yours to edit.⌉[
Crawler policy & bot identity — declare your content-usage signals, block AI-training
crawlers by name, turn away spoofed traffic, and verify bots against what each operator
publishes: reverse DNS for the search engines, published IP ranges for GPTBot and
PerplexityBot, cryptographic signatures for agents that sign. The verified-bots
registry is yours to edit.
[⌊Request Log — every request an agent made, in one filterable table: narrow by
client, endpoint, network, verification verdict, User-Agent or date to see exactly
what a single bot fetched. A Status column carries one honest mark per request —
verified, signed, spoofed, forged, refused or unchecked. Your own logged-in visits
are never recorded.⌉⌊Request Log — every request an agent made, in one filterable
table: narrow by client, endpoint, network, verification verdict, User-Agent or
date to see exactly what a single bot fetched. A Status column carries one honest
mark per request — verified, signed, spoofed, forged, refused or unchecked. Your
own logged-in visits are never recorded.⌉[
Request Log — every request an agent made, in one filterable table: narrow by client,
endpoint, network, verification verdict, User-Agent or date to see exactly what
a single bot fetched. A Status column carries one honest mark per request — verified,
signed, spoofed, forged, refused or unchecked. Your own logged-in visits are never
recorded.
[⌊MCP server — one switch runs a Model Context Protocol server on your own site.
Your server address leads: give it to an assistant and it asks you for approval —
no keys to paste — and every approved assistant is listed with its scope, its last
call and its own Disconnect. Above it, the trust ladder: a second switch lets agents
write, a third decides whether they may publish or only leave drafts.⌉⌊MCP server—
one switch runs a Model Context Protocol server on your own site. Your server address
leads: give it to an assistant and it asks you for approval — no keys to paste —
and every approved assistant is listed with its scope, its last call and its own
Disconnect. Above it, the trust ladder: a second switch lets agents write, a third
decides whether they may publish or only leave drafts.⌉[
MCP server — one switch runs a Model Context Protocol server on your own site. Your
server address leads: give it to an assistant and it asks you for approval — no
keys to paste — and every approved assistant is listed with its scope, its last
call and its own Disconnect. Above it, the trust ladder: a second switch lets agents
write, a third decides whether they may publish or only leave drafts.
[⌊Data sources — the outside services Agentimus reads from, all optional and read-
only, each with one key held on your own server and no third-party proxy: Cloudflare
for what the edge answered or blocked before your server saw it, Google Search Console
and Bing Webmaster Tools for classic search and index coverage. Numbers land in
your own database, so your history outlives each service's own reporting window.⌉⌊
Data sources — the outside services Agentimus reads from, all optional and read-
only, each with one key held on your own server and no third-party proxy: Cloudflare
for what the edge answered or blocked before your server saw it, Google Search Console
and Bing Webmaster Tools for classic search and index coverage. Numbers land in
your own database, so your history outlives each service's own reporting window.⌉[
Data sources — the outside services Agentimus reads from, all optional and read-
only, each with one key held on your own server and no third-party proxy: Cloudflare
for what the edge answered or blocked before your server saw it, Google Search Console
and Bing Webmaster Tools for classic search and index coverage. Numbers land in
your own database, so your history outlives each service’s own reporting window.
[⌊AI Visibility — an opt-in, bring-your-own-key scoreboard showing whether ChatGPT,
Perplexity, Gemini and Claude mention and link each brand, product or person you
track: seen-in-answers and linked-your-site rates, rank against each item's own
rivals, and question-by-question results with the sources each engine cited.⌉⌊AI
Visibility — an opt-in, bring-your-own-key scoreboard showing whether ChatGPT, Perplexity,
Gemini and Claude mention and link each brand, product or person you track: seen-
in-answers and linked-your-site rates, rank against each item's own rivals, and
question-by-question results with the sources each engine cited.⌉[
AI Visibility — an opt-in, bring-your-own-key scoreboard showing whether ChatGPT,
Perplexity, Gemini and Claude mention and link each brand, product or person you
track: seen-in-answers and linked-your-site rates, rank against each item’s own
rivals, and question-by-question results with the sources each engine cited.
[⌊Discovery Hub — everything your site tells AI agents, in one place: the providers
describing it, the read capabilities they expose, the public APIs, and the MCP &
tools surface — your own MCP server alongside the WordPress Abilities API, with
the tools each carries. Each summary tile jumps to its own countable list, and any
registration problem is listed with a plain-English fix.⌉⌊Discovery Hub — everything
your site tells AI agents, in one place: the providers describing it, the read capabilities
they expose, the public APIs, and the MCP & tools surface — your own MCP server
alongside the WordPress Abilities API, with the tools each carries. Each summary
tile jumps to its own countable list, and any registration problem is listed with
a plain-English fix.⌉[
Discovery Hub — everything your site tells AI agents, in one place: the providers
describing it, the read capabilities they expose, the public APIs, and the MCP &
tools surface — your own MCP server alongside the WordPress Abilities API, with
the tools each carries. Each summary tile jumps to its own countable list, and any
registration problem is listed with a plain-English fix.
[⌊The writing assistant — a quill button on every Agentimus screen opens the drawer:
describe the post you want, edit the outline it proposes, preview the fully dressed
draft, then create it as a draft and land straight in the editor. Nothing is saved
until you say so, and it never publishes.⌉⌊The writing assistant — a quill button
on every Agentimus screen opens the drawer: describe the post you want, edit the
outline it proposes, preview the fully dressed draft, then create it as a draft
and land straight in the editor. Nothing is saved until you say so, and it never
publishes.⌉[
The writing assistant — a quill button on every Agentimus screen opens the drawer:
describe the post you want, edit the outline it proposes, preview the fully dressed
draft, then create it as a draft and land straight in the editor. Nothing is saved
until you say so, and it never publishes.
[⌊In the post editor — the "Agentimus" box, AI Readability tab: a per-page pass/
warn check of what makes the page hard for an assistant to read and cite — enough
substance, an opening summary, section headings, heading order, prose vs links,
and image alt text. Each row that needs work offers "Fix with AI", which drafts
a concrete fix using the AI provider you set up in WordPress.⌉⌊In the post editor—
the "Agentimus" box, AI Readability tab: a per-page pass/warn check of what makes
the page hard for an assistant to read and cite — enough substance, an opening summary,
section headings, heading order, prose vs links, and image alt text. Each row that
needs work offers "Fix with AI", which drafts a concrete fix using the AI provider
you set up in WordPress.⌉[
In the post editor — the “Agentimus” box, AI Readability tab: a per-page pass/warn
check of what makes the page hard for an assistant to read and cite — enough substance,
an opening summary, section headings, heading order, prose vs links, and image alt
text. Each row that needs work offers “Fix with AI”, which drafts a concrete fix
using the AI provider you set up in WordPress.
## انسٹال کرݨ
1. Upload the `agentimus` folder to `/wp-content/plugins/`, or install via Plugins
Add New.
2. Activate the plugin.
3. A setup wizard opens automatically on your first visit to the admin and walks you
through your identity and content choices in about a minute. After that everything
runs on its own — open **Agentimus** any time to review the readiness report or
adjust settings.
## ہرہک دے سوال
### Where is the documentation?
The full documentation — a plain-English user manual and a developer reference —
is at https://heera.github.io/agentimus/. It has step-by-step guides for every feature,
plus the hooks, filters and endpoints for developers.
### Do I need to be technical to use this?
No. A setup wizard opens automatically the first time you visit the admin and walks
you through everything in about a minute — you write a sentence about who you are
and tick what AI assistants may read. Everything else runs on its own, and you can
change any of it later.
### What does Agentimus change on my site? Will my visitors notice?
Nothing your visitors see changes — there’s no new front-end script, style or layout.
Behind the scenes it publishes machine-readable files and signals (like llms.txt
and a discovery document) that only AI assistants and crawlers read. It also stands
down automatically next to SEO plugins, so it won’t duplicate or fight your existing
setup.
### What’s the quickest way to set this up for my site?
Activate Agentimus and run the one-minute setup wizard — that covers most sites.
Then, depending on what you do:
* **Consultant, freelancer or personal brand:** fill in your Identity — your name,
a one-sentence bio, your expertise topics, and links to your other profiles.
That’s the highest-signal information an AI assistant uses to describe and cite
you correctly.
* **Business or agency:** set the entity type to Organization, list the services
you offer, and add a contact email so an agent can point enquiries the right
way.
* **Blog or publisher:** the defaults are already right — your posts and pages
flow into llms.txt automatically. Just add a profile sentence so an assistant
knows whose site it is.
Whatever your case, the Readiness report always tells you the single next thing
worth improving.
### Does Agentimus make external requests or send my data anywhere?
By default, no — Agentimus makes no outbound HTTP requests out of the box, sends
nothing to any external service, collects no analytics or telemetry, and stores
the agent-activity log in your own database with no IP addresses. (One opt-in setting,
_Store IP addresses for flagged clients_, can store IPs locally for flagged crawlers
only — off by default; see _External services_.) Two opt-in features go outbound.**
Verify bot identities** makes DNS lookups and downloads, once a day, the crawler-
IP lists that bot operators publish (Google, OpenAI, Perplexity, …) so impostors
can be caught; when a request arrives carrying a Web Bot Auth signature, it also
fetches that operator’s public key file so the signature can be checked on your
own server. Only those public files are fetched, and nothing about your site is
sent. **The other is the optional AI Visibility feature:** if you enable it and
add your own API key, Agentimus queries the AI provider(s) you chose (OpenAI, Perplexity,
Gemini and/or Anthropic) to check whether they mention and cite you — only for the
engines you turn on, and only when a check runs (on demand or on your schedule).
Your keys stay on your server and nothing else is sent anywhere. See _External services_
for the full disclosure. The discovery document includes a `$schema` value that
_identifies_ the document format (the same way a schema.org URL identifies a vocabulary);
it is a label in the output, never fetched. The one place a request is made is the
optional “Verify live” self-check on the readiness report — and that runs in _your
browser_, fetching your own public URLs only when you click it; the server itself
still makes no request.
### Do I need an SEO plugin alongside Agentimus?
No. With no SEO plugin installed, Agentimus covers the search essentials itself:
per-page SEO titles (an “SEO title” field in the editor), Open Graph/X share cards,
canonical links, meta descriptions, and an XML sitemap with last-changed dates.
Each has its own switch under Settings Discovery Search basics. If you install
an SEO plugin later, Agentimus notices on the next page load and steps aside on
everything the plugin owns — your per-page values are kept, and everything returns
if that plugin leaves.
### Does this conflict with my SEO plugin?
No. When Yoast, Rank Math, SEOPress, AIOSEO or The SEO Framework is active, Agentimus
stands down on every overlapping surface — JSON-LD, SEO titles, share cards, canonicals,
meta descriptions and the sitemap — automatically, so nothing is ever emitted twice.
A card on the dashboard names the division of labour. The AI-facing endpoints (llms.
txt, markdown twins, the discovery documents) don’t overlap with SEO plugins and
keep working the same either way.
### My robots.txt rules aren’t showing.
If a static `robots.txt` file exists at your site root, or your CDN serves its own,
it overrides WordPress’s virtual robots.txt. The readiness report flags this. Remove
the static file to let Agentimus manage the rules.
### I turned something on but nothing seems to happen — is it broken?
Almost always it’s working — here’s how to confirm. The generated AI files are cached
for up to an hour, so a change may not show instantly: open the file directly (for
example `yoursite.com/llms.txt`) and refresh. The Readiness report’s **Verify live**
button fetches your real URLs from your browser and shows exactly what an agent
receives — including anything your CDN is caching. If a file still isn’t appearing,
check that a static file or your CDN isn’t overriding it (the report flags a static
robots.txt, for instance).
### How do I tell AI not to train on my content?
Set **Allow AI training** to off under Settings Crawler policy. That one switch
publishes your choice in three places at once, so a crawler that ignores one still
sees the others:
1. **robots.txt** — a `Content-Signal: … ai-train=no` line (advisory).
2. **A response header** on your pages — `tdm-reservation: 1` (the W3C TDM Reservation
Protocol), which reaches bots that never read robots.txt.
3. **An opt-out file** at `/.well-known/tdmrep.json` — the recognized, machine-readable
reservation, relevant under EU text-and-data-mining rules.
The header and file are on by default and can be toggled per channel under “Published
beyond robots.txt”. You can optionally also send the non-standard `X-Robots-Tag:
noai, noimageai` (off by default, honored by some platforms) and link an AI-usage
policy URL.
**Important — these are signals, not a wall.** robots.txt, the header and tdmrep.
json are standardized _requests_ that compliant crawlers honor; they do not forcibly
stop a bot. To actually refuse a crawler with a `403`, add it to the crawler list
or use scanner blocking (Crawler policy Block specific crawlers / Block scanners),
which Agentimus enforces at its generated endpoints.
### Can I block only specific AI bots?
Yes — list them under **Block specific crawlers**. That writes a per-name `Disallow:/`
to robots.txt for each. The `/.well-known/tdmrep.json` opt-out file and the `tdm-
reservation` header are **site-wide** — the standard has no per-bot dial — so per-
bot blocking lives in robots.txt (and in scanner blocking for a hard 403), while
the file and header carry your overall site-wide choice. (Those site-wide signals
are published only when you block AI training; an open site publishes none.)
### Which AI agents are allowed by default?
Out of the box Agentimus blocks nothing — it’s a discovery layer, so every agent
is served until you turn on the optional scanner blocking. Even then, an **always-
allowed** list keeps trusted clients flowing: the major search engines (Googlebot,
Bingbot, DuckDuckBot, Applebot, Yandex) are recognised automatically and never blocked
or flagged, and the _AI access_ tab shows them read-only so you know exactly what’s
trusted. You can add well-known AI assistants and answer engines (ChatGPT, Claude,
Perplexity, …) with one click, or mark any client **Allow** from the activity review
queue. Training crawlers (GPTBot, ClaudeBot, …) are deliberately not on the trust
list — those belong to your separate AI-training choice, so trusting them here wouldn’t
quietly undo an opt-out you may have set.
### Can I see if AI is sending me visitors?
Yes — the dashboard’s “Traffic from AI” card counts real people who landed on your
site from an AI assistant (ChatGPT, Perplexity, Gemini, …), detected from the visit’s
referrer and the `utm_source` tag some AI tools add to their links. It’s the mirror
of the activity log: that shows bots _reading_ your content; this shows AI _bringing
you readers_, with a by-source and top-landing-pages breakdown. Like the rest of
the log it’s first-party and aggregate-only — no IP, no per-visitor records, nothing
sent anywhere. Some AI visits can’t be detected (stripped referrers, Google’s AI
Overviews, cached pages), so read the figure as a floor: at least this many.
### Will Agentimus get my site mentioned by ChatGPT or improve my AI rankings?
Honestly: it helps with one half of that, not the other. Agentimus makes your site**
discoverable and correctly understood** — when an AI assistant looks at your site,
it can find your content, read a clean version, and describe you accurately. That
is what the plugin controls, and it does it well. But whether an AI **spontaneously
mentions you** when someone asks a broad question (“best resources for X”) is a
matter of **authority and reputation** — earned over time through genuinely notable
content that others reference. No plugin, llms.txt, or schema can manufacture that,
and any tool promising “instant AI visibility” is overselling. Agentimus makes sure
that when authority does bring an agent to your door, nothing is lost in translation.
### Will it slow my site down?
No. The text endpoints are cached and CDN-friendly; there is no front-end JavaScript
or CSS for your visitors (the optional, off-by-default WebMCP bridge adds a tiny
script only when you enable it, and it stays inert in browsers without the API).
The admin app loads only on the plugin’s own screen.
### Does it expose anything private, or let agents change my site?
No. Agentimus only describes what your site already makes public; it grants no new
access. Removing or suppressing an item changes what is _advertised_, not what is
reachable — the underlying endpoints behave exactly as before, behind their own
authentication.
### Does Agentimus run an MCP server?
Yes — as an opt-in, on WordPress 6.9 or newer. Turn on **Settings Discovery MCP
server** and the AI assistants you already use can talk to your site over the Model
Context Protocol and run the same permission-checked tools your admin AI gets —
ten read-only ones (readiness, AI traffic, bot identification, per-page readability,
internal-link suggestions and previews), plus the write tools if you separately
allow those (see the next question). Connecting is usually one approval: give the
assistant your server address and it asks you for permission on a page served by
your own site, where you choose read-only or read-and-write. Claude, ChatGPT and
Cursor work this way today (ChatGPT behind its Developer-mode switch); Codex cannot
ask, so it takes a shared token you create on the card and send as a Bearer header.
A WordPress application password still works too, for one key per tool tied to a
specific user. Nothing becomes public — every request signs in, each tool keeps
the same permission checks as the admin screens, and every call is recorded under**
More Agent Access**. Off by default, and everything needed ships with the plugin.
### Can an AI agent write to my site?
Only if you say so, twice. The MCP server starts read-only; a second switch — **
Let connected agents write** — adds the write tools: draft and edit posts and pages
complete with categories, tags and a featured image (from your media library, or
imported from a URL), set their AI topics and descriptions, and apply Readiness
fixes (a fixed list of safe switches that can only turn documented features on,
never loosen a protection). Even then, agents can’t publish: they leave drafts and
pending posts for your review, unless you flip a third switch that allows going
live. Writes are held to the site’s own quality bar too: the write tools show agents
the same readability rules the in-admin assistant drafts to, and every create or
update returns the post’s AI-readability grade. Every write runs as the signed-in
user — an agent can never do more than that user could in the editor: filing under
existing categories, creating new ones, and uploading images each follow that user’s
own permissions — and every call is recorded under **More Agent Access**, attributed
to the key that made it.
### Can AI help me write the description, topics and fixes?
Yes, if you’re on WordPress 7.0 and have set up an AI provider under Settings AI.
Then **Draft with AI** appears on the AI description field, **Suggest with AI**
on the Topics field, and **Fix with AI** on any AI Readability row that needs work.
Agentimus asks _your_ AI through WordPress’s shared connectors — it never sees or
stores your API key, and nothing is sent anywhere if you haven’t set a provider
up (the buttons simply don’t appear). Every suggestion arrives as ordinary editable
text in the field: you read it, change it, and save the post yourself. Nothing is
written for you.
### Can AI write a whole post for me?
Yes — the writing assistant (the quill button on Agentimus’s own screens) turns
a described idea into a complete draft. It proposes an outline you can edit first,
then writes the title, body, AI description and topics with suggested categories
and tags, and shows you everything before a single thing is saved. **Create draft**
opens the post in the editor, where image placeholders arrive with their alt text
ready — fill them from your library, or generate them with AI. It can also revise
an existing post you pick, without ever changing its status. It needs the **Let
connected agents write** switch on and an AI provider under Settings AI, and it
never publishes: drafts and pending review only.
### Does AI Visibility use the AI provider I set up in WordPress?
No — it needs its own API keys, and that’s on purpose. A visibility check is graded
on the **sources each engine cited**, and WordPress’s shared connectors hand back
only the answer text; the list of cited sources is dropped before Agentimus could
read it. Reading those sources means talking to each engine’s own API, so AI Visibility
keeps its own keys (Settings AI Visibility). They stay on your server and are used
for nothing else.
### How do I make my plugin appear in the discovery document?
Add a single optional action — no dependency, no library. If Agentimus isn’t installed
the hook simply never fires:
```
add_action( 'wpdiscovery_register', function ( $registry ) {
$registry->register( array( 'id' => 'acme', 'title' => 'Acme', 'type' => 'commerce' ) );
} );
```
Agentimus also fires the product-aliased `agentimus_register`; you may hook either.
See `examples/integrate-your-plugin.php` for the full resource schema (capabilities,
endpoints, auth, agent cards, MCP tools).
### Which hooks can my plugin use?
Registration is a single action, but Agentimus exposes more for deeper integrations,
grouped by stability:
* **Stable** — frozen at WP_Discovery spec 1.0; build on these: the `wpdiscovery_register`
action with its `$registry->register()` / `add_well_known()` API, plus `agentimus_entity_types`
and the `agentimus_cache_flushed` action.
* **Extension** — supported output-shaping filters (signatures may evolve between
releases): tune the discovery document, MCP/agent surfaces, llms.txt, schema.
org, sitemap, REST discovery and security.txt — e.g. `agentimus_envelope`, `agentimus_documents`,`
agentimus_mcp`, `agentimus_agent_skills`, `agentimus_well_known_routed`, `agentimus_post_types`,`
agentimus_security_txt`.
* **Internal** — advanced site-owner tuning (Guard, Classifier, Activity, Settings);
not a third-party integration surface.
Every hook, with its signature and tier, is catalogued in `examples/all-hooks-reference.
php`.
### Is the discovery format an open standard I can read?
Yes. The discovery document implements the **WP_Discovery Protocol**, an openly-
licensed (CC BY 4.0) specification — not a format private to this plugin. Read the
spec, the 1.0 JSON Schema and worked examples at https://heera.github.io/wp-discovery-
protocol/ (source and conformance tests: https://github.com/heera/wp-discovery-protocol).
Agentimus is its reference implementation.
### Does Agentimus store IP addresses?
Not by default. The agent-activity log records who fetched your endpoints with no
IP addresses at all. One opt-in setting — _Store IP addresses for flagged clients_—
records the IP only of clients flagged as impersonating or spoofed crawlers (never
ordinary traffic), so you can block them at your host or CDN. When on, those IPs
are personal data: stored on your own site only, kept for a short retention period,
cleared when you clear the activity log, and deleted if you turn the setting back
off. Nothing is ever sent off your server. If you enable it, disclose it in your
privacy policy (Agentimus adds suggested text at Settings Privacy).
### Is the admin interface built from source I can inspect?
Yes — there is no minified-only code. The admin interface is built from Vue 3 source
in `resources/` with Vite; the source and `vite.config.js` ship in this package
and also live in the public repository at https://github.com/heera/agentimus . Run`
npm install && npm run build` to regenerate `assets/admin/` from source.
## ریویو
### [A complete AI-readiness plugin that actually delivers](https://wordpress.org/support/topic/a-complete-ai-readiness-plugin-that-actually-delivers/)
[Nowshad Jawad](https://profiles.wordpress.org/jawad0501/) جولائی 4, 2026
As a WordPress developer, I like adopting tools that solve real problems rather
than chasing trends, and Agentimus genuinely impressed me. It goes far beyond generating
an llms.txt file by providing a complete AI discovery layer, clean machine-readable
content, crawler visibility, and a readiness report that helped me identify gaps
in my site’s AI accessibility. I especially appreciate its developer-friendly architecture,
privacy-first approach, and the fact that it makes no unrealistic SEO claims—it
simply helps AI systems understand your site better. It’s now part of my default
toolkit for every new WordPress project. Highly recommended.
[ سارے 1 ریویو پڑھو ](https://wordpress.org/support/plugin/agentimus/reviews/)
## Contributors & Developers
“Agentimus – AI SEO, llms.txt & MCP for AI Agents” is open source software. The
following people have contributed to this plugin.
حصہ پاوݨ آلے
* [ Sheikh Heera ](https://profiles.wordpress.org/heera/)
[ “Agentimus – AI SEO, llms.txt & MCP for AI Agents” دا آپݨی زبان وچ ترجمہ کرو۔](https://translate.wordpress.org/projects/wp-plugins/agentimus)
### ڈیویلپمنٹ وچ دلچسپی ہے؟
[Browse the code](https://plugins.trac.wordpress.org/browser/agentimus/), check
out the [SVN repository](https://plugins.svn.wordpress.org/agentimus/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/agentimus/) by [RSS](https://plugins.trac.wordpress.org/log/agentimus/?limit=100&mode=stop_on_copy&format=rss).
## تبدیلی لاگ
#### 1.33.0
* New: Classic search, measured — Search Performance and Search Opportunities screens
for Bing Webmaster Tools and Google Search Console: what people searched, how
often you appeared, and which pages sit one improvement from page one. Every
number is the engine’s own, and automated probe traffic is named, never blended
in.
* New: In Google’s Index — a daily watchlist plus a whole-site rotation through
Google’s URL Inspection: every verdict in Google’s own words, problems grouped
with Search Console deep links, any page’s answer one lookup away — plus week-
on-week trend, Google Discover, and the health of the sitemap you registered.
* New: Found by AI Search — how much of your site Bing’s index holds and how cleanly
its crawler gets in; ChatGPT search and Copilot read this index today.
* New: Cloudflare edge panel (opt-in, your own token) — what the edge answered
or blocked before your server ever saw the request, with a warning when the edge
disagrees with your crawler policy.
* New: a setup wizard on first visit, and an agent-ready front door — SKILL.md,
auth.md, and an MCP handshake that answers strangers politely.
* Fixed: the promoted XML sitemap now serves at WordPress’s standard /wp-sitemap.
xml, and the old addresses redirect to it — a moved sitemap had been silently
failing search-console registrations.
* Improved: every data screen names whose behavior it counts — people or machines—
and every external data pull is chunked or budgeted, resumes after failure, and
reports what happened in words.
#### 1.32.0
* New — **Connect an assistant by approval, not by key.** Give an AI assistant
your MCP address and it asks _you_ for permission: a consent page on your own
site names what it calls itself, where it will return, and lets you choose **
Read only** or **Read and write** — you can grant less than it asked for. Approving
gives that one assistant its own key; every connection is listed under **Connected
assistants** with its own Disconnect, so cutting one off leaves the others working.
Standards-based (OAuth 2.1 with PKCE, dynamic client registration), all on your
own site — nothing is brokered by anyone else. Verified with Claude, Cursor and
ChatGPT (ChatGPT connects behind its Developer-mode switch).
* New — **A shared token for assistants that can’t ask.** One revocable secret,
created in a click, for clients that don’t support the approval flow (Codex among
them). Read-only or read-and-write, shown once, rotated or revoked whenever you
like — Agentimus stores only a fingerprint, never the secret.
* New — **A read-only key is shown read-only tools.** An assistant you granted
read access no longer sees the five write tools at all, so it can’t discover
the boundary by bumping into refusals. Whatever the key, an agent still can never
exceed your write settings — and publishing stays off unless you allow it.
* Fixed — **Discovery for clients that compute the address themselves.** The standard
lets a client derive the OAuth discovery address from the MCP endpoint’s own
URL instead of reading the hint the server sends on a 401 — ChatGPT does exactly
that, found a 404 there, and concluded the server “does not implement OAuth”.
The same discovery document is now served at both addresses.
* Improved — **Agent Access grew a proper table.** The events feed is a real table
with column headings on wide screens — same discs, pills and stamps, without
repeating “First seen” on every row — and it re-stacks into the familiar cards
on smaller screens. The Request Log and the dashboard’s Recent Requests gained
the same card treatment on phones, so nothing scrolls sideways any more.
* Improved — **The roster says how each key got in.** Every Connected-assistants
row carries a small “approval” or “token” chip, the setup guides became boxed
sections with real weight, and the card’s notes now distinguish Revoke — which
ends every connection using the shared token — from rotating it for a fresh secret.
* Improved — **The MCP card, rebuilt around the address.** One status line (running,
tool count, last call), your server address up front with a Copy button — that
address _is_ the setup now — then Connected assistants, then setup steps folded
away and shown for the one assistant you pick. Everything the old card did, in
a screen you can take in at once.
* New — **Conflict honesty in Readiness.** Agentimus checks its own `/llms.txt`
and home page the way an agent would, and says plainly when another plugin is
serving them instead of taking credit for it. A new scoreless row names any plugin
emitting duplicate description or social-card tags on your home page.
* New — **Robots watch.** If your robots.txt changes — by another plugin, a host
setting, or your own hand — Readiness and the weekly email say what changed,
once, in plain words, and the notice retires itself after two weeks. Reconstructed
locally: no extra requests to your own site.
* Fixed — **The internal-link tool reaches agents at last.** 1.30.0 promised connected
agents the same “link to your own posts” suggestions through a read-only MCP
tool; the tool was built but never added to the server’s list, so it wasn’t there.
It is now.
* Fixed — **Assistants that use their own callback address can connect.** Desktop
clients register a private return address (`claude://…`); these were being silently
discarded, so registration failed with a misleading error. Executable and malformed
addresses are still refused.
* Fixed — **Screens stop waiting to be reloaded.** Approving a connection happens
in another window, so the settings card now refreshes itself when you come back
to it, and Agent Access re-reads its list whenever you arrive instead of showing
you an older page with a “new” badge above it.
* Improved — **Agent Access names the door.** A call made with the shared token
reads “via connection token”, and one made by an approved assistant reads “via
Claude’s connection” — the identity you approved, not a name the caller claimed
for itself.
#### 1.31.0
* New — **Share drafts, written from the post.** The editor panel grows a **Share**
tab: ready-to-post drafts for X, Facebook, LinkedIn, WhatsApp, Telegram and Reddit,
each written locally from the post’s own title, description and topics, with
the link preview beside them. With an AI provider connected, a per-card polish
rewrites any one draft on request. Nothing is ever posted for you — you copy,
or click through to the network’s own composer (and where a network refuses prefilled
text, the card copies first and says so). Editor-only; switch it off under Settings.
* New — **Ask AI about this post.** A small row after each post lets a reader open
ChatGPT, Claude, Perplexity, Google AI Mode or Grok pre-filled with the post’s
address — one click turns a reader into an assistant visit your own Request Log
can see. Plain links, no script, nothing sent anywhere until a reader clicks,
and off in one switch under Settings. The row also respects your own bot policy:
a button is hidden when your blocklists forbid that assistant from reading the
page (notably Google, whose single Google-Extended token governs both AI training
and AI-Mode reading), and the Settings toggle names any hidden button and why.
* Improved — **Screens load like screens.** The Request Log, AI Traffic, AI Visibility
and Agent Access screens show the same quiet loading placeholder the dashboard
uses while their data is on its way, instead of a bare “Loading…” — or, on Agent
Access, nothing at all.
* Fixed — **The request-log tool answers MCP clients again.** Its response had
outgrown its declared schema (the Status column’s two switch states arrived in
1.30.0 without being declared), so the tool rejected its own output. The schema
now declares everything the log returns, and a test holds the two ends together.
* New — **Signed agents, verified mathematically.** Some AI agents now cryptographically
sign their requests — Google’s agent and OpenAI’s already do. With **Verify bot
identities** on, Agentimus checks the signature right on your own server (Web
Bot Auth, the emerging open standard): a genuine agent earns a **signed** mark
in the Request Log, and a forged signature — someone pretending to be a signer—
is flagged for review and, with blocking on, refused. Unsigned crawlers lose
nothing: signing is extra proof, never a requirement. The only outbound request
is fetching the operator’s public key file (see _External services_).
* New — **Link to your own posts.** A new editor box suggests which of your own
posts the one you’re writing should link to — found from your topics, categories
and text, instantly, no AI needed — and inserts the link at a real phrase in
your prose with one click, as an ordinary edit you can undo. With an AI provider
connected, one optional call picks nicer anchor phrases and explains each suggestion.
Connected agents get the same suggestions through a read-only MCP tool that never
spends your AI budget.
* New — **A refusal is never silent.** Requests turned away at your AI endpoints—
proven impostors, forged signatures — are now recorded: they show in the Request
Log as **refused** and count toward the review queue and the weekly email’s impostors,
but toward none of your read totals, because a refusal is not a read.
* Improved — **Agent Access reads as a feed.** Connected-agent activity became
a card feed with the subject up front, and its header now tells you what the
watching has seen: how many events, how many of the available abilities have
actually been used, and when the last call landed.
* Improved — **The Request Log says more per row.** A new Status column carries
one honest mark per request — verified, signed, spoofed, forged, refused — with
the explanation on hover, plus a “Requested at” column; and every timestamp in
the admin now follows your site’s own date and time format settings.
* Improved — **The Optimize worklist works in bigger strokes.** Each check’s section
gains a one-click **Ignore All** — every page that check flags, including the
ones past the “Showing 6 of 8” preview — the aside list gains a matching **Restore
All**, and each set-aside page is now its own card showing what it was flagged
for, so a parked page still tells you why it was parked.
* Fixed — **One broken discovery extension no longer silences the rest.** If another
plugin extending Agentimus’s discovery documents fails, its entry is skipped
and named in an admin notice — everyone else’s still ships.
Earlier releases — the full history, in the same words — live in [CHANGELOG.md](https://github.com/heera/agentimus/blob/main/CHANGELOG.md)
in the plugin’s source repository.
## میٹا
* Version **1.33.0**
* Last updated **22 گھنٹے پہلے**
* Active installations **10+**
* WordPress version ** 6.0 یا ودھ **
* Tested up to **7.1**
* PHP version ** 7.4 یا ودھ **
* Language
* [English (US)](https://wordpress.org/plugins/agentimus/)
* Tags
* [agent-readiness](https://skr.wordpress.org/plugins/tags/agent-readiness/)[ai agents](https://skr.wordpress.org/plugins/tags/ai-agents/)
[ai seo](https://skr.wordpress.org/plugins/tags/ai-seo/)[llms.txt](https://skr.wordpress.org/plugins/tags/llms-txt/)
[mcp](https://skr.wordpress.org/plugins/tags/mcp/)
* [اعلیٰ منظر](https://skr.wordpress.org/plugins/agentimus/advanced/)
## ریٹنگ
5 out of 5 stars.
* [ 1 5-star review ](https://wordpress.org/support/plugin/agentimus/reviews/?filter=5)
* [ 0 4-star reviews ](https://wordpress.org/support/plugin/agentimus/reviews/?filter=4)
* [ 0 3-star reviews ](https://wordpress.org/support/plugin/agentimus/reviews/?filter=3)
* [ 0 2-star reviews ](https://wordpress.org/support/plugin/agentimus/reviews/?filter=2)
* [ 0 1-star reviews ](https://wordpress.org/support/plugin/agentimus/reviews/?filter=1)
[Your review](https://wordpress.org/support/plugin/agentimus/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/agentimus/reviews/)
## حصہ پاوݨ آلے
* [ Sheikh Heera ](https://profiles.wordpress.org/heera/)
## معاونت
Got something to say? Need help?
[معاونت فورم ݙیکھو](https://wordpress.org/support/plugin/agentimus/)