Agentimus

Agentimus makes your site legible to AI agents and crawlers — and shows you which ones actually read it. You get a first-party log of every AI crawler that fetches your content, one-click blocking for the bots you don’t want, and the machine-readable signals search engines and AI tools read today: a clean llms.txt, JSON-LD, markdown delivery, and AI-crawl controls. A one-screen readiness report scores how machine-readable your site is and what’s still missing.

This is AI readiness — sometimes called AI SEO, GEO (Generative Engine Optimization), or AEO (Answer Engine Optimization): publishing the machine-readable signals AI systems need to find, read, and correctly represent your site.

Underneath, it ties these together with a single, normalized discovery document at /.well-known/discovery.json — an open, standards-aligned map of your site’s identity, capabilities and APIs, and a reference implementation of that open convention, not a private format. This is more than an llms.txt generator: llms.txt is one signal among several, sitting under a coherent discovery layer rather than being the whole product.

It makes no outbound requests, collects no analytics, and logs no IP addresses. Everything runs on your own site.

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. Turn it on to return 403 to the user-agents on your denylist, and optionally auto-deny agents that disguise themselves as ancient handsets (a classic scanner trick). Protected search engines and anything on your allow-list are never blocked, and /.well-known/acme-challenge/ (SSL renewal) always stays reachable.

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.
• Activity to review — a nav-bar queue surfaces the clients worth a second look — new, unusually high-volume, or spoofing what they are — names a recognised crawler where it can, and offers one-click Block or Allow (trust). Nothing is blocked unless you choose to.

Content — clean, machine-readable output

• Markdown delivery — request any page as clean markdown by appending .md to its URL (or, where your server allows it, with an Accept: text/markdown header).
• /llms.txt & /llms-full.txt — an 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.
• XML sitemap — an opt-in fallback sitemap (index + paginated sub-sitemaps), generated only when neither WordPress core nor an SEO plugin already provides one, and advertised in robots.txt and llms.txt.

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, so researchers and agents have a machine-readable way to report an issue.

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.

Machine discovery (forward-looking)

Agentimus also publishes a single, normalized discovery document, built to the conventions the agent ecosystem is converging on (the .well-known convention, A2A agent cards, MCP-shaped tools). It puts a site’s 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 a single optional hook, so what an agent needs is aggregated in one place.
• /.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): sign the discovery documents with an Ed25519 key published at /.well-known/http-message-signatures-directory, so agents can verify they came from you. Off by default.
• WordPress Abilities API → MCP tools — registered abilities are projected into MCP-shaped tool descriptors, and a running MCP server (if one is installed) is detected and linked. Agentimus advertises tools; it does not execute them.
• Zero-config auto-discovery — reads your registered REST API namespaces, public post types and the WordPress Abilities API, so a site is described even when no plugin declares itself. A Discovery Hub admin screen shows what an agent can see, and you decide what is published.

What’s read today vs. what it readies you for

Honest framing: the content signals above (JSON-LD, robots, llms.txt, markdown) are read by search engines and AI tools today. The discovery document is forward-looking and standards-aligned — it prepares your site for AI agents as they adopt these conventions, rather than claiming every agent already reads it. The discovery format is an open, openly-licensed convention with a public reference, not a private one, and the plugin works fully whether or not anything consumes that document.

Why it’s useful

Most tools cover one slice — an llms.txt file, an AI-bot blocker, or structured data. Agentimus brings content control, agent-traffic visibility, clean machine-readable output and a forward-looking discovery document together in one coherent, lightweight package — and tells you what’s still missing.

External services

Agentimus does not use, connect to, or send any data to any external or third-party service. Everything runs on your own site: it makes no outbound HTTP requests, loads no remote scripts, fonts or analytics, and stores the agent-activity log in your own database with no IP addresses.

The generated discovery documents contain a $schema value that names the document format (in the same way a schema.org URL identifies a vocabulary). It is a label inside the output only — it is never fetched.

The example URLs in examples/integrate-your-plugin.php (on example.com) are placeholders for documentation; they are not requested by the plugin.

Source & build

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.