{"id":328611,"date":"2026-06-22T15:02:49","date_gmt":"2026-06-22T15:02:49","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/agentify\/"},"modified":"2026-08-02T21:22:03","modified_gmt":"2026-08-02T21:22:03","slug":"agentimus","status":"publish","type":"plugin","link":"https:\/\/bn.wordpress.org\/plugins\/agentimus\/","author":8853146,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.33.0","stable_tag":"1.33.0","tested":"7.1","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Agentimus","header_author":"Sheikh Heera","header_description":"An AI-discovery layer for your site: a \/.well-known discovery document, machine-readable pages (llms.txt, markdown, JSON-LD), AI-crawl controls, and a first-party agent-activity log. Lightweight, no SEO bloat.","assets_banners_color":"f2f2eb","last_updated":"2026-08-02 21:22:03","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/github.com\/heera\/agentimus","header_author_uri":"https:\/\/heera.it","rating":5,"author_block_rating":0,"active_installs":10,"downloads":1679,"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"heera","date":"2026-06-22 15:51:17"},"1.1.0":{"tag":"1.1.0","author":"heera","date":"2026-06-23 00:12:00"},"1.10.0":{"tag":"1.10.0","author":"heera","date":"2026-06-29 22:22:19"},"1.10.1":{"tag":"1.10.1","author":"heera","date":"2026-06-30 00:59:44"},"1.12.4":{"tag":"1.12.4","author":"heera","date":"2026-07-02 12:34:33"},"1.13.0":{"tag":"1.13.0","author":"heera","date":"2026-07-04 13:20:26"},"1.14.0":{"tag":"1.14.0","author":"heera","date":"2026-07-05 17:36:39"},"1.14.1":{"tag":"1.14.1","author":"heera","date":"2026-07-05 18:16:39"},"1.15.0":{"tag":"1.15.0","author":"heera","date":"2026-07-08 02:10:07"},"1.16.0":{"tag":"1.16.0","author":"heera","date":"2026-07-09 18:22:31"},"1.17.0":{"tag":"1.17.0","author":"heera","date":"2026-07-10 17:39:33"},"1.18.0":{"tag":"1.18.0","author":"heera","date":"2026-07-10 20:32:42"},"1.19.0":{"tag":"1.19.0","author":"heera","date":"2026-07-11 17:30:35"},"1.2.0":{"tag":"1.2.0","author":"heera","date":"2026-06-23 13:32:45"},"1.20.0":{"tag":"1.20.0","author":"heera","date":"2026-07-12 02:22:13"},"1.20.1":{"tag":"1.20.1","author":"heera","date":"2026-07-12 03:16:43"},"1.21.0":{"tag":"1.21.0","author":"heera","date":"2026-07-13 00:41:55"},"1.21.1":{"tag":"1.21.1","author":"heera","date":"2026-07-13 01:49:01"},"1.21.2":{"tag":"1.21.2","author":"heera","date":"2026-07-13 02:18:18"},"1.22.0":{"tag":"1.22.0","author":"heera","date":"2026-07-14 05:55:06"},"1.22.1":{"tag":"1.22.1","author":"heera","date":"2026-07-16 00:20:37"},"1.22.2":{"tag":"1.22.2","author":"heera","date":"2026-07-16 02:44:49"},"1.23.0":{"tag":"1.23.0","author":"heera","date":"2026-07-16 05:50:05"},"1.24.0":{"tag":"1.24.0","author":"heera","date":"2026-07-18 01:23:08"},"1.25.0":{"tag":"1.25.0","author":"heera","date":"2026-07-20 06:11:36"},"1.26.0":{"tag":"1.26.0","author":"heera","date":"2026-07-20 20:06:45"},"1.27.0":{"tag":"1.27.0","author":"heera","date":"2026-07-22 11:44:46"},"1.27.1":{"tag":"1.27.1","author":"heera","date":"2026-07-22 11:53:13"},"1.28.0":{"tag":"1.28.0","author":"heera","date":"2026-07-25 11:11:11"},"1.29.0":{"tag":"1.29.0","author":"heera","date":"2026-07-25 11:28:48"},"1.3.0":{"tag":"1.3.0","author":"heera","date":"2026-06-23 19:34:27"},"1.30.0":{"tag":"1.30.0","author":"heera","date":"2026-07-27 06:40:50"},"1.31.0":{"tag":"1.31.0","author":"heera","date":"2026-07-28 09:05:50"},"1.32.0":{"tag":"1.32.0","author":"heera","date":"2026-07-30 12:00:49"},"1.33.0":{"tag":"1.33.0","author":"heera","date":"2026-08-02 21:22:03"},"1.4.0":{"tag":"1.4.0","author":"heera","date":"2026-06-24 21:50:49"},"1.4.1":{"tag":"1.4.1","author":"heera","date":"2026-06-24 22:29:35"},"1.4.2":{"tag":"1.4.2","author":"heera","date":"2026-06-24 23:22:11"},"1.4.3":{"tag":"1.4.3","author":"heera","date":"2026-06-25 02:09:38"},"1.5.0":{"tag":"1.5.0","author":"heera","date":"2026-06-27 01:11:34"},"1.6.0":{"tag":"1.6.0","author":"heera","date":"2026-06-27 17:35:52"},"1.7.0":{"tag":"1.7.0","author":"heera","date":"2026-06-28 03:50:17"},"1.8.0":{"tag":"1.8.0","author":"heera","date":"2026-06-28 23:00:56"},"1.9.0":{"tag":"1.9.0","author":"heera","date":"2026-06-29 02:56:13"}},"upgrade_notice":{"1.33.0":"<p>Classic search, measured: Search Performance and Opportunities for Bing and Google, an In Google&#039;s Index card with whole-site coverage and page lookup, a Cloudflare edge view, and a setup wizard. The sitemap returns to WordPress&#039;s standard \/wp-sitemap.xml \u2014 old addresses redirect, so registrations heal on their own. No breaking changes.<\/p>","1.32.0":"<p>Connect an AI assistant by approving it, not by pasting keys: give it your MCP address and it asks you for permission on your own site, where you choose read-only or read-and-write. Each assistant gets its own key and its own Disconnect. Plus a shared token for clients that can&#039;t ask, honest reporting when another plugin serves your llms.txt, and a robots.txt change watch. No breaking changes \u2014 existing keys keep working.<\/p>","1.31.0":"<p>Share drafts written from the post (six networks, editor-only, nothing auto-posted) and an &quot;Ask AI about this post&quot; row whose assistant visits show in your own request log \u2014 both with an off switch. Plus consistent loading screens and an MCP request-log fix. No breaking changes.<\/p>","1.30.0":"<p>Agents that cryptographically sign their requests (Google&#039;s agent, OpenAI) are now verified on your own server \u2014 forgeries flagged, unsigned crawlers never penalised. Plus internal-link suggestions in the editor, refused impostors on the record, and a clearer Request Log. No breaking changes.<\/p>","1.29.0":"<p>Agentimus now covers the search basics \u2014 titles, share cards, canonicals, sitemap \u2014 when no SEO plugin is active, and keeps deferring when one is. Plus: pick the weekly email\u2019s day and time.<\/p>","1.28.0":"<p>A short weekly email about what AI did on your site \u2014 quiet weeks send nothing, one-click stop inside every email \u2014 and the review queue\u2019s count now shows on the admin menu from every screen.<\/p>","1.27.1":"<p>Small ordering fix on the new review-ask endpoint (deny before validate). No security impact, no breaking changes.<\/p>","1.27.0":"<p>A quiet, one-time review ask that never nags (and retires the footer&#039;s rating line once answered), a first-run finish that shows what just went live, and standard auth vocabulary on the MCP server card. No breaking changes.<\/p>","1.26.0":"<p>Fairer AI-readability grading \u2014 no more penalty for your topic\u2019s vocabulary or your code samples \u2014 and AI agents now draft to your readability rules, graded on every write.<\/p>","1.25.0":"<p>Write with AI without leaving wp-admin: a built-in assistant drafts new posts (outline first, preview always, never publishes), revises existing ones without touching their status, and generates images right in the editor. Plus plain-language AI errors and a self-updating Cited rung. No breaking changes.<\/p>","1.24.0":"<p>Bot verification grows: bots are also checked against their operator&#039;s published IP ranges (GPTBot, PerplexityBot, \u2026), the verified list is now yours to edit, and with blocking on a proven impostor is refused \u2014 not just flagged. Plus a clearer review queue and a phone-friendly admin. No breaking changes.<\/p>","1.23.0":"<p>Agent-access alerts now fire on every visit, Markdown output is ready for WordPress 7.1&#039;s new blocks, and your Content Guidelines steer every AI draft \u2014 in the editor and over MCP. No breaking changes.<\/p>","1.22.2":"<p>Polish and fixes: clicking a Discovery tile now lands the section in view, the MCP settings card no longer logs a 401 in the browser console, the Discovery layout is tidier, and AI Visibility explains why it uses its own keys. No breaking changes.<\/p>","1.22.1":"<p>New opt-in write tier: connected AI tools can draft, edit and fully dress posts \u2014 categories, tags, featured image \u2014 and, behind a separate third switch, publish. Off by default, permission-checked per key, every write audited. Plus: the MCP card now connects your AI tool for you, and the score card counts what&#039;s left to fix.<\/p>","1.22.0":"<p>One switch now runs an MCP server on your own site \u2014 AI tools like Claude Code can use Agentimus&#039;s read-only tools, authenticated, permission-checked and fully audited. Off by default. Also: Agent access rows now name the user and key behind every event, and the dashboard&#039;s 7\/30-day counters count whole calendar days, so they no longer appear to lose hits.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3581957,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3581957,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon-512x512.png":{"filename":"icon-512x512.png","revision":3581957,"resolution":"512x512","location":"assets","locale":"","width":512,"height":512}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3609613,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3609613,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0","1.10.0","1.10.1","1.12.4","1.13.0","1.14.0","1.14.1","1.15.0","1.16.0","1.17.0","1.18.0","1.19.0","1.2.0","1.20.0","1.20.1","1.21.0","1.21.1","1.21.2","1.22.0","1.22.1","1.22.2","1.23.0","1.24.0","1.25.0","1.26.0","1.27.0","1.27.1","1.28.0","1.29.0","1.3.0","1.30.0","1.31.0","1.32.0","1.33.0","1.4.0","1.4.1","1.4.2","1.4.3","1.5.0","1.6.0","1.7.0","1.8.0","1.9.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3632101,"resolution":"1","location":"assets","locale":"","width":1440,"height":3664},"screenshot-10.png":{"filename":"screenshot-10.png","revision":3632101,"resolution":"10","location":"assets","locale":"","width":1440,"height":3283},"screenshot-11.png":{"filename":"screenshot-11.png","revision":3632101,"resolution":"11","location":"assets","locale":"","width":1440,"height":1040},"screenshot-12.png":{"filename":"screenshot-12.png","revision":3632101,"resolution":"12","location":"assets","locale":"","width":1440,"height":1015},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3632101,"resolution":"2","location":"assets","locale":"","width":1440,"height":1200},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3632101,"resolution":"3","location":"assets","locale":"","width":1440,"height":1200},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3632101,"resolution":"4","location":"assets","locale":"","width":1440,"height":5632},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3632101,"resolution":"5","location":"assets","locale":"","width":1440,"height":3211},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3632101,"resolution":"6","location":"assets","locale":"","width":1440,"height":3321},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3632101,"resolution":"7","location":"assets","locale":"","width":1440,"height":1200},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3632101,"resolution":"8","location":"assets","locale":"","width":1440,"height":1377},"screenshot-9.png":{"filename":"screenshot-9.png","revision":3632101,"resolution":"9","location":"assets","locale":"","width":1440,"height":3440}},"screenshots":{"1":"Dashboard \u2014 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.","2":"In Google's Index \u2014 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 \u2014 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.","3":"Search Performance \u2014 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.","4":"Readiness report \u2014 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.","5":"Crawler policy &amp; bot identity \u2014 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.","6":"Request Log \u2014 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 \u2014 verified, signed, spoofed, forged, refused or unchecked. Your own logged-in visits are never recorded.","7":"MCP server \u2014 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 \u2014 no keys to paste \u2014 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.","8":"Data sources \u2014 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.","9":"AI Visibility \u2014 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.","10":"Discovery Hub \u2014 everything your site tells AI agents, in one place: the providers describing it, the read capabilities they expose, the public APIs, and the MCP &amp; tools surface \u2014 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.","11":"The writing assistant \u2014 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.","12":"In the post editor \u2014 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 \u2014 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."}},"plugin_section":[],"plugin_tags":[268607,246305,236374,244604,242115],"plugin_category":[55],"plugin_contributors":[151449],"plugin_business_model":[],"class_list":["post-328611","plugin","type-plugin","status-publish","hentry","plugin_tags-agent-readiness","plugin_tags-ai-agents","plugin_tags-ai-seo","plugin_tags-llms-txt","plugin_tags-mcp","plugin_category-seo-and-marketing","plugin_contributors-heera","plugin_committers-heera"],"banners":{"banner":"https:\/\/ps.w.org\/agentimus\/assets\/banner-772x250.png?rev=3609613","banner_2x":"https:\/\/ps.w.org\/agentimus\/assets\/banner-1544x500.png?rev=3609613","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/agentimus\/assets\/icon-128x128.png?rev=3581957","icon_2x":"https:\/\/ps.w.org\/agentimus\/assets\/icon-256x256.png?rev=3581957","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-1.png?rev=3632101","caption":"Dashboard \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-2.png?rev=3632101","caption":"In Google's Index \u2014 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 \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-3.png?rev=3632101","caption":"Search Performance \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-4.png?rev=3632101","caption":"Readiness report \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-5.png?rev=3632101","caption":"Crawler policy &amp; bot identity \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-6.png?rev=3632101","caption":"Request Log \u2014 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 \u2014 verified, signed, spoofed, forged, refused or unchecked. Your own logged-in visits are never recorded."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-7.png?rev=3632101","caption":"MCP server \u2014 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 \u2014 no keys to paste \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-8.png?rev=3632101","caption":"Data sources \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-9.png?rev=3632101","caption":"AI Visibility \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-10.png?rev=3632101","caption":"Discovery Hub \u2014 everything your site tells AI agents, in one place: the providers describing it, the read capabilities they expose, the public APIs, and the MCP &amp; tools surface \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-11.png?rev=3632101","caption":"The writing assistant \u2014 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."},{"src":"https:\/\/ps.w.org\/agentimus\/assets\/screenshot-12.png?rev=3632101","caption":"In the post editor \u2014 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 \u2014 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."}],"raw_content":"<!--section=description-->\n<p>Agentimus is an all-in-one AI SEO plugin for the age of AI agents \u2014 AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) in one place. It does two things.<\/p>\n\n<p><strong>It makes your site legible and citable.<\/strong> It helps AI assistants like ChatGPT, Claude and Perplexity find your site, read it correctly, and cite it in your own words \u2014 and shows you which AI bots are actually visiting. <strong>You don't need to understand AI or web standards to use it:<\/strong> a setup wizard walks you through everything in about a minute, then it runs on its own.<\/p>\n\n<p><strong>And it lets the AI tools you already use operate your site.<\/strong> Turn on the built-in Model Context Protocol (MCP) server and Claude Code, Claude Desktop, Cursor or Codex can read your reports and \u2014 behind two more opt-in switches \u2014 <strong>draft, edit and publish posts<\/strong> 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 <strong>writing assistant<\/strong> drafts and revises posts there. (Full details below.)<\/p>\n\n<p>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.<\/p>\n\n<p>By default it makes no outbound requests, collects no analytics, and logs no IP addresses \u2014 everything runs on your own site. Three optional, off-by-default features change that only when you enable them: <strong>AI Visibility<\/strong>, <strong>Verify bot identities<\/strong> and <strong>Store IP addresses<\/strong> (each disclosed in full under <em>External services<\/em>).<\/p>\n\n<p><strong>\ud83d\udcd6 Full documentation<\/strong> \u2014 a plain-English manual and developer reference, step-by-step guides for every feature: https:\/\/heera.github.io\/agentimus\/<\/p>\n\n<p><strong>With an SEO plugin \u2014 or instead of one<\/strong><\/p>\n\n<ul>\n<li><strong>No SEO plugin? You don't need one.<\/strong> 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.<\/li>\n<li><strong>Already running Yoast, Rank Math, SEOPress, AIOSEO or The SEO Framework?<\/strong> Agentimus detects it and steps aside on every overlapping surface \u2014 titles, cards, schema, sitemap \u2014 automatically. No duplicate tags, ever: it adds only the AI layer your SEO plugin doesn't cover.<\/li>\n<\/ul>\n\n<p><strong>Operate your site from your AI agent (MCP) \u2014 opt-in<\/strong><\/p>\n\n<ul>\n<li><strong>A Model Context Protocol server on your own site<\/strong> \u2014 one switch (Settings \u2192 Discovery) runs an MCP server at <code>\/wp-json\/agentimus\/v1\/mcp<\/code>; the whole library ships with the plugin, nothing extra to install.<\/li>\n<li><strong>Connect by approving, not by pasting keys<\/strong> \u2014 an assistant asks <em>you<\/em> for permission on a consent page on your own site; you choose <strong>Read only<\/strong> or <strong>Read and write<\/strong>, 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 <strong>shared token<\/strong> covers clients that can't ask.<\/li>\n<li><strong>Read your site's data<\/strong> \u2014 connected agents run the read-only tools (readiness\/AEO-GEO score, AI traffic, request log, bot identification, page \/ JSON-LD \/ Markdown previews) \u2014 the same ones WordPress's built-in AI gets.<\/li>\n<li><strong>Draft, edit and publish posts \u2014 behind two more switches<\/strong> \u2014 turn on <strong>Let connected agents write<\/strong> 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.<\/li>\n<li><strong>Safe by construction<\/strong> \u2014 every write runs as the signed-in WordPress user, never exceeding their permissions, and is recorded under <strong>More \u2192 Agent Access<\/strong>. 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.<\/li>\n<\/ul>\n\n<p><strong>Write with AI in wp-admin \u2014 the built-in assistant (opt-in)<\/strong><\/p>\n\n<ul>\n<li><strong>Idea \u2192 draft without leaving wp-admin<\/strong> \u2014 a quill button opens the writing assistant: describe the post, edit the outline it proposes, and preview the complete draft \u2014 real editor blocks, AI description, topics, categories, tags. Nothing is saved until you click <strong>Create draft<\/strong>, and it never publishes.<\/li>\n<li><strong>Edit existing posts<\/strong> \u2014 describe the change and it revises the content; a post's status never changes, and WordPress revisions keep every prior version.<\/li>\n<li><strong>Images where you write<\/strong> \u2014 alt-filled placeholders in drafts, <strong>Generate image from the alt text<\/strong> on every image block, a <strong>Featured image (AI)<\/strong> sidebar panel \u2014 or pick from your library.<\/li>\n<li><strong>Ask AI on any block<\/strong> \u2014 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 \u2192 AI \u2014 Agentimus never sees your key), and every AI button hides until a provider is set up.<\/li>\n<\/ul>\n\n<p><strong>Control \u2014 who may use your content<\/strong><\/p>\n\n<ul>\n<li><strong>robots.txt content-signals + AI-training blocklist<\/strong> \u2014 declare your content-usage policy and block named model-training crawlers (GPTBot, CCBot, ClaudeBot, Google-Extended, Bytespider, \u2026) by name, while leaving read\/cite bots free.<\/li>\n<li><strong>Block scanners &amp; scrapers (opt-in hard block)<\/strong> \u2014 robots rules are a polite request; this enforces them, returning 403 to the user-agents on your denylist. Your <strong>always-allowed<\/strong> 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.<\/li>\n<\/ul>\n\n<p><strong>Reduce exposure \u2014 what your site reveals to bots<\/strong><\/p>\n\n<ul>\n<li><strong>Exposure controls (opt-in, all OFF by default)<\/strong> \u2014 switches that quietly close what stock WordPress reveals to anonymous crawlers: username enumeration, author archives, the WordPress version, the auto-generated <code>&lt;head&gt;<\/code> 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.<\/li>\n<\/ul>\n\n<p><strong>Visibility \u2014 who is reading you<\/strong><\/p>\n\n<ul>\n<li><strong>Agent activity log<\/strong> \u2014 a dashboard of which AI crawlers and agents actually fetch your content and endpoints (GPTBot, Claude, Perplexity, Googlebot, \u2026), recorded first-party in your own database, with no IP logging by default (an optional setting stores IPs for flagged crawlers only).<\/li>\n<li><strong>Activity to review<\/strong> \u2014 a nav-bar queue surfaces clients worth a second look \u2014 new, unusually high-volume, or spoofing \u2014 with one-click <strong>Block<\/strong> or <strong>Allow<\/strong>. Nothing is blocked unless you choose to.<\/li>\n<li><strong>Request Log<\/strong> \u2014 every recorded request, one row each, under <em>More \u2192 Request Log<\/em>. Filter by client, endpoint, network, user-agent and date to see exactly what a single bot fetched.<\/li>\n<li><strong>Agent Access<\/strong> \u2014 the other side of the log: who <em>authenticates to and acts on<\/em> the machine surface (<em>More \u2192 Agent Access<\/em>): assistants approved, keys created or revoked, abilities run, requests refused. A record, not a guard \u2014 it names the key used, never the person.<\/li>\n<li><strong>Traffic from AI<\/strong> \u2014 the mirror of the crawler log: the real visitors an AI assistant sent you, day by day, by assistant and by landing page (<em>More \u2192 AI Traffic<\/em>) \u2014 daily aggregate counts, never a row for one person, no IP. An opt-in <strong>CDN mode<\/strong> keeps counts accurate behind a full-page cache.<\/li>\n<li><strong>Edge traffic (Cloudflare, opt-in)<\/strong> \u2014 what Cloudflare answered or blocked <em>before your server ever saw the request<\/em> \u2014 the cache hits and edge blocks no server-side log can see \u2014 read with your own token, and it warns when the edge disagrees with your policy.<\/li>\n<li><strong>You decide how long it's kept<\/strong> \u2014 retention, nightly auto-delete, and a hard size cap that always applies, so the log can never outgrow your host.<\/li>\n<li><strong>AI Visibility (opt-in)<\/strong> \u2014 track <strong>each brand, product or person you choose<\/strong> across ChatGPT, Perplexity, Gemini and Claude: whether it gets <strong>mentioned, linked, and how it ranks against its rivals<\/strong> \u2014 over time, against the questions your audience actually types. Off by default; <strong>you bring your own API key<\/strong> (the one feature that makes an outbound request \u2014 see <em>External services<\/em>).<\/li>\n<\/ul>\n\n<p><strong>Classic search, measured \u2014 Bing &amp; Google (opt-in)<\/strong><\/p>\n\n<ul>\n<li><strong>Search Performance &amp; Opportunities<\/strong> \u2014 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 \u2014 never estimated \u2014 and automated probe traffic is named, not blended in.<\/li>\n<li><strong>In Google's Index \/ Found by AI Search<\/strong> \u2014 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 \u2014 plus week-on-week trend, Google Discover, and the health of the sitemap you registered.<\/li>\n<\/ul>\n\n<p><strong>Content \u2014 clean, machine-readable output<\/strong><\/p>\n\n<ul>\n<li><strong>Markdown delivery<\/strong> \u2014 request any page as clean markdown by appending <code>.md<\/code> to its URL. (An <code>Accept: text\/markdown<\/code> mode also exists, off by default.)<\/li>\n<li><strong>\/llms.txt<\/strong> &amp; <strong>\/llms-full.txt<\/strong> \u2014 an <a href=\"https:\/\/llmstxt.org\">llmstxt.org<\/a> index of your pages, topics and recent posts, plus a full-text edition an agent can ingest in a single request.<\/li>\n<li><strong>JSON-LD<\/strong> \u2014 WebSite + Person\/Organization, plus BlogPosting and BreadcrumbList on posts. Automatically <strong>defers to Yoast, Rank Math, SEOPress, AIOSEO and The SEO Framework<\/strong> so you never ship duplicate schema.<\/li>\n<li><strong>Topics for AI<\/strong> \u2014 say what each post is about in plain words, right in the editor; those topics become the JSON-LD <code>keywords<\/code> and a line in the page's <code>.md<\/code>, 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.<\/li>\n<li><strong>AI description<\/strong> \u2014 write a one-line summary of each post in the editor; it becomes the JSON-LD <code>description<\/code>, the lead of the page's <code>.md<\/code>, and the page's <code>&lt;meta name=\"description\"&gt;<\/code> (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 <code>&lt;head&gt;<\/code>.<\/li>\n<li><strong>XML sitemap<\/strong> \u2014 with no SEO plugin, Agentimus serves your sitemap (index + paginated sub-sitemaps, with last-changed dates) at WordPress's standard <code>\/wp-sitemap.xml<\/code> address \u2014 old addresses redirect, so a search-console registration never goes stale \u2014 and advertises it in robots.txt and llms.txt; with one installed, it links theirs instead.<\/li>\n<li><strong>Change feed<\/strong> \u2014 a JSON feed at <code>\/agentimus-changes.json<\/code> lists recently added, updated and removed pages (with a <code>?since=<\/code> filter), so an assistant re-checks only what changed. On by default, advertised in discovery.<\/li>\n<\/ul>\n\n<p><strong>Identity &amp; contact<\/strong><\/p>\n\n<ul>\n<li><strong>Author \/ site identity<\/strong> \u2014 a profile sentence, expertise topics and linked profiles (<code>sameAs<\/code>) feed llms.txt and JSON-LD \u2014 the highest-signal lines for agent retrieval.<\/li>\n<li><strong>security.txt<\/strong> \u2014 optionally publish an RFC 9116 disclosure contact at <code>\/.well-known\/security.txt<\/code>.<\/li>\n<\/ul>\n\n<p><strong>Readiness report<\/strong><\/p>\n\n<ul>\n<li>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.<\/li>\n<li><strong>Agent preview<\/strong> \u2014 open it from the Readiness tab to see the exact JSON-LD <em>and<\/em> 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.<\/li>\n<li><strong>AI Readability tips<\/strong> \u2014 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 \u2014 nothing shows to visitors.<\/li>\n<\/ul>\n\n<p><strong>Machine discovery (forward-looking)<\/strong><\/p>\n\n<p>Agentimus also publishes a single, normalized discovery document \u2014 the conventions the agent ecosystem is converging on (<code>.well-known<\/code>, A2A agent cards, MCP-shaped tools) \u2014 putting identity, capabilities and APIs in one predictable place:<\/p>\n\n<ul>\n<li><strong>\/.well-known\/discovery.json<\/strong> \u2014 an owner-curated document describing the site's identity, capabilities, APIs and agent cards. Other plugins can declare themselves through one optional hook.<\/li>\n<li><strong>\/.well-known\/agent-card.json<\/strong> and <strong>\/.well-known\/mcp.json<\/strong> \u2014 an A2A agent card and an MCP manifest, generated automatically.<\/li>\n<li><strong>Standards-aligned <code>.well-known<\/code> endpoints<\/strong> \u2014 an RFC 9727 <code>api-catalog<\/code>, plus \u2014 <em>only when the capability actually exists<\/em> \u2014 an MCP server card and an Agent Skills index. Optional <strong>response signing<\/strong> (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.<\/li>\n<li><strong>WordPress Abilities API<\/strong> \u2014 Agentimus registers its own <strong>read-only abilities<\/strong> (readiness\/AEO-GEO score, AI traffic, request log, bot checks, and page \/ JSON-LD \/ Markdown previews), so WordPress's built-in AI \u2014 and, with the MCP adapter, external agents \u2014 can read them, each gated by the same capability as its screen. A separate, off-by-default switch adds the write abilities above.<\/li>\n<li><strong>Zero-config auto-discovery<\/strong> \u2014 reads your REST namespaces, public post types and the Abilities API, so a site is described even when no plugin declares itself; the <strong>Discovery Hub<\/strong> screen shows what an agent sees, and you decide what is published.<\/li>\n<\/ul>\n\n<p><strong>What's read today vs. what it readies you for<\/strong><\/p>\n\n<p>The content signals above are read by search engines and AI tools <strong>today<\/strong>; the discovery document is <strong>forward-looking<\/strong>, preparing your site for agents as they adopt these conventions.<\/p>\n\n<p><strong>Why it's useful<\/strong><\/p>\n\n<p>Most tools cover one slice \u2014 an llms.txt file, a bot blocker, or structured data. Agentimus brings the whole job together in one lightweight package \u2014 and tells you what's still missing.<\/p>\n\n<h3>External services<\/h3>\n\n<p>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 \u2014 see the FAQ.)<\/p>\n\n<p><strong>Two opt-in features go outbound; both are off by default.<\/strong><\/p>\n\n<p><strong>Verify bot identities<\/strong> 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 \u2014 or a URL you add yourself). Only those files are fetched; nothing about your site is sent.<\/p>\n\n<p>The same setting verifies <strong>Web Bot Auth<\/strong> signatures \u2014 the standard where an AI agent signs its request cryptographically. To check one, Agentimus fetches (and caches) the signing operator's <strong>public key directory<\/strong> at <code>\/.well-known\/http-message-signatures-directory<\/code>, only when a signed request arrives, and sends nothing about your site with it. Operators publishing one today:<\/p>\n\n<ul>\n<li><strong>OpenAI<\/strong> \u2014 https:\/\/chatgpt.com\/.well-known\/http-message-signatures-directory \u00b7 https:\/\/openai.com\/policies\/terms-of-use \u00b7 https:\/\/openai.com\/policies\/privacy-policy<\/li>\n<li><strong>Google<\/strong> \u2014 https:\/\/agent.bot.goog\/.well-known\/http-message-signatures-directory \u00b7 https:\/\/policies.google.com\/terms \u00b7 https:\/\/policies.google.com\/privacy<\/li>\n<\/ul>\n\n<p><strong>AI Visibility:<\/strong> 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 \u2014 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:<\/p>\n\n<ul>\n<li><strong>OpenAI (ChatGPT)<\/strong> \u2014 https:\/\/openai.com\/policies\/terms-of-use \u00b7 https:\/\/openai.com\/policies\/privacy-policy<\/li>\n<li><strong>Perplexity<\/strong> \u2014 https:\/\/www.perplexity.ai\/hub\/legal\/terms-of-service \u00b7 https:\/\/www.perplexity.ai\/hub\/legal\/privacy-policy<\/li>\n<li><strong>Google (Gemini)<\/strong> \u2014 https:\/\/ai.google.dev\/gemini-api\/terms \u00b7 https:\/\/policies.google.com\/privacy<\/li>\n<li><strong>Anthropic (Claude)<\/strong> \u2014 https:\/\/www.anthropic.com\/legal\/consumer-terms \u00b7 https:\/\/www.anthropic.com\/legal\/privacy<\/li>\n<\/ul>\n\n<p>URL-like strings in the plugin's output are labels, not requests \u2014 the discovery documents' <code>$schema<\/code> value names the format (never fetched), and the <code>example.com<\/code> URLs in <code>examples\/<\/code> are documentation placeholders.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>agentimus<\/code> folder to <code>\/wp-content\/plugins\/<\/code>, or install via Plugins \u2192 Add New.<\/li>\n<li>Activate the plugin.<\/li>\n<li>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 \u2014 open <strong>Agentimus<\/strong> any time to review the readiness report or adjust settings.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"where%20is%20the%20documentation%3F\"><h3>Where is the documentation?<\/h3><\/dt>\n<dd><p>The full documentation \u2014 a plain-English user manual and a developer reference \u2014 is at https:\/\/heera.github.io\/agentimus\/. It has step-by-step guides for every feature, plus the hooks, filters and endpoints for developers.<\/p><\/dd>\n<dt id=\"do%20i%20need%20to%20be%20technical%20to%20use%20this%3F\"><h3>Do I need to be technical to use this?<\/h3><\/dt>\n<dd><p>No. A setup wizard opens automatically the first time you visit the admin and walks you through everything in about a minute \u2014 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.<\/p><\/dd>\n<dt id=\"what%20does%20agentimus%20change%20on%20my%20site%3F%20will%20my%20visitors%20notice%3F\"><h3>What does Agentimus change on my site? Will my visitors notice?<\/h3><\/dt>\n<dd><p>Nothing your visitors see changes \u2014 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.<\/p><\/dd>\n<dt id=\"what%27s%20the%20quickest%20way%20to%20set%20this%20up%20for%20my%20site%3F\"><h3>What's the quickest way to set this up for my site?<\/h3><\/dt>\n<dd><p>Activate Agentimus and run the one-minute setup wizard \u2014 that covers most sites. Then, depending on what you do:<\/p>\n\n<ul>\n<li><strong>Consultant, freelancer or personal brand:<\/strong> fill in your Identity \u2014 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.<\/li>\n<li><strong>Business or agency:<\/strong> 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.<\/li>\n<li><strong>Blog or publisher:<\/strong> the defaults are already right \u2014 your posts and pages flow into llms.txt automatically. Just add a profile sentence so an assistant knows whose site it is.<\/li>\n<\/ul>\n\n<p>Whatever your case, the Readiness report always tells you the single next thing worth improving.<\/p><\/dd>\n<dt id=\"does%20agentimus%20make%20external%20requests%20or%20send%20my%20data%20anywhere%3F\"><h3>Does Agentimus make external requests or send my data anywhere?<\/h3><\/dt>\n<dd><p>By default, no \u2014 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, <em>Store IP addresses for flagged clients<\/em>, can store IPs locally for flagged crawlers only \u2014 off by default; see <em>External services<\/em>.) Two opt-in features go outbound. <strong>Verify bot identities<\/strong> makes DNS lookups and downloads, once a day, the crawler-IP lists that bot operators publish (Google, OpenAI, Perplexity, \u2026) 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. <strong>The other is the optional AI Visibility feature:<\/strong> 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 \u2014 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 <em>External services<\/em> for the full disclosure. The discovery document includes a <code>$schema<\/code> value that <em>identifies<\/em> 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 \u2014 and that runs in <em>your browser<\/em>, fetching your own public URLs only when you click it; the server itself still makes no request.<\/p><\/dd>\n<dt id=\"do%20i%20need%20an%20seo%20plugin%20alongside%20agentimus%3F\"><h3>Do I need an SEO plugin alongside Agentimus?<\/h3><\/dt>\n<dd><p>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 \u2192 Discovery \u2192 Search basics. If you install an SEO plugin later, Agentimus notices on the next page load and steps aside on everything the plugin owns \u2014 your per-page values are kept, and everything returns if that plugin leaves.<\/p><\/dd>\n<dt id=\"does%20this%20conflict%20with%20my%20seo%20plugin%3F\"><h3>Does this conflict with my SEO plugin?<\/h3><\/dt>\n<dd><p>No. When Yoast, Rank Math, SEOPress, AIOSEO or The SEO Framework is active, Agentimus stands down on every overlapping surface \u2014 JSON-LD, SEO titles, share cards, canonicals, meta descriptions and the sitemap \u2014 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.<\/p><\/dd>\n<dt id=\"my%20robots.txt%20rules%20aren%27t%20showing.\"><h3>My robots.txt rules aren't showing.<\/h3><\/dt>\n<dd><p>If a static <code>robots.txt<\/code> 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.<\/p><\/dd>\n<dt id=\"i%20turned%20something%20on%20but%20nothing%20seems%20to%20happen%20%E2%80%94%20is%20it%20broken%3F\"><h3>I turned something on but nothing seems to happen \u2014 is it broken?<\/h3><\/dt>\n<dd><p>Almost always it's working \u2014 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 <code>yoursite.com\/llms.txt<\/code>) and refresh. The Readiness report's <strong>Verify live<\/strong> button fetches your real URLs from your browser and shows exactly what an agent receives \u2014 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).<\/p><\/dd>\n<dt id=\"how%20do%20i%20tell%20ai%20not%20to%20train%20on%20my%20content%3F\"><h3>How do I tell AI not to train on my content?<\/h3><\/dt>\n<dd><p>Set <strong>Allow AI training<\/strong> to off under Settings \u2192 Crawler policy. That one switch publishes your choice in three places at once, so a crawler that ignores one still sees the others:<\/p>\n\n<ol>\n<li><strong>robots.txt<\/strong> \u2014 a <code>Content-Signal: \u2026 ai-train=no<\/code> line (advisory).<\/li>\n<li><strong>A response header<\/strong> on your pages \u2014 <code>tdm-reservation: 1<\/code> (the W3C TDM Reservation Protocol), which reaches bots that never read robots.txt.<\/li>\n<li><strong>An opt-out file<\/strong> at <code>\/.well-known\/tdmrep.json<\/code> \u2014 the recognized, machine-readable reservation, relevant under EU text-and-data-mining rules.<\/li>\n<\/ol>\n\n<p>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 <code>X-Robots-Tag: noai, noimageai<\/code> (off by default, honored by some platforms) and link an AI-usage policy URL.<\/p>\n\n<p><strong>Important \u2014 these are signals, not a wall.<\/strong> robots.txt, the header and tdmrep.json are standardized <em>requests<\/em> that compliant crawlers honor; they do not forcibly stop a bot. To actually refuse a crawler with a <code>403<\/code>, add it to the crawler list or use scanner blocking (Crawler policy \u2192 Block specific crawlers \/ Block scanners), which Agentimus enforces at its generated endpoints.<\/p><\/dd>\n<dt id=\"can%20i%20block%20only%20specific%20ai%20bots%3F\"><h3>Can I block only specific AI bots?<\/h3><\/dt>\n<dd><p>Yes \u2014 list them under <strong>Block specific crawlers<\/strong>. That writes a per-name <code>Disallow: \/<\/code> to robots.txt for each. The <code>\/.well-known\/tdmrep.json<\/code> opt-out file and the <code>tdm-reservation<\/code> header are <strong>site-wide<\/strong> \u2014 the standard has no per-bot dial \u2014 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.)<\/p><\/dd>\n<dt id=\"which%20ai%20agents%20are%20allowed%20by%20default%3F\"><h3>Which AI agents are allowed by default?<\/h3><\/dt>\n<dd><p>Out of the box Agentimus blocks nothing \u2014 it's a discovery layer, so every agent is served until you turn on the optional scanner blocking. Even then, an <strong>always-allowed<\/strong> list keeps trusted clients flowing: the major search engines (Googlebot, Bingbot, DuckDuckBot, Applebot, Yandex) are recognised automatically and never blocked or flagged, and the <em>AI access<\/em> 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, \u2026) with one click, or mark any client <strong>Allow<\/strong> from the activity review queue. Training crawlers (GPTBot, ClaudeBot, \u2026) are deliberately not on the trust list \u2014 those belong to your separate AI-training choice, so trusting them here wouldn't quietly undo an opt-out you may have set.<\/p><\/dd>\n<dt id=\"can%20i%20see%20if%20ai%20is%20sending%20me%20visitors%3F\"><h3>Can I see if AI is sending me visitors?<\/h3><\/dt>\n<dd><p>Yes \u2014 the dashboard's \"Traffic from AI\" card counts real people who landed on your site from an AI assistant (ChatGPT, Perplexity, Gemini, \u2026), detected from the visit's referrer and the <code>utm_source<\/code> tag some AI tools add to their links. It's the mirror of the activity log: that shows bots <em>reading<\/em> your content; this shows AI <em>bringing you readers<\/em>, with a by-source and top-landing-pages breakdown. Like the rest of the log it's first-party and aggregate-only \u2014 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.<\/p><\/dd>\n<dt id=\"will%20agentimus%20get%20my%20site%20mentioned%20by%20chatgpt%20or%20improve%20my%20ai%20rankings%3F\"><h3>Will Agentimus get my site mentioned by ChatGPT or improve my AI rankings?<\/h3><\/dt>\n<dd><p>Honestly: it helps with one half of that, not the other. Agentimus makes your site <strong>discoverable and correctly understood<\/strong> \u2014 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 <strong>spontaneously mentions you<\/strong> when someone asks a broad question (\"best resources for X\") is a matter of <strong>authority and reputation<\/strong> \u2014 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.<\/p><\/dd>\n<dt id=\"will%20it%20slow%20my%20site%20down%3F\"><h3>Will it slow my site down?<\/h3><\/dt>\n<dd><p>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.<\/p><\/dd>\n<dt id=\"does%20it%20expose%20anything%20private%2C%20or%20let%20agents%20change%20my%20site%3F\"><h3>Does it expose anything private, or let agents change my site?<\/h3><\/dt>\n<dd><p>No. Agentimus only describes what your site already makes public; it grants no new access. Removing or suppressing an item changes what is <em>advertised<\/em>, not what is reachable \u2014 the underlying endpoints behave exactly as before, behind their own authentication.<\/p><\/dd>\n<dt id=\"does%20agentimus%20run%20an%20mcp%20server%3F\"><h3>Does Agentimus run an MCP server?<\/h3><\/dt>\n<dd><p>Yes \u2014 as an opt-in, on WordPress 6.9 or newer. Turn on <strong>Settings \u2192 Discovery \u2192 MCP server<\/strong> 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 \u2014 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 \u2014 every request signs in, each tool keeps the same permission checks as the admin screens, and every call is recorded under <strong>More \u2192 Agent Access<\/strong>. Off by default, and everything needed ships with the plugin.<\/p><\/dd>\n<dt id=\"can%20an%20ai%20agent%20write%20to%20my%20site%3F\"><h3>Can an AI agent write to my site?<\/h3><\/dt>\n<dd><p>Only if you say so, twice. The MCP server starts read-only; a second switch \u2014 <strong>Let connected agents write<\/strong> \u2014 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\u2019s 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\u2019s AI-readability grade. Every write runs as the signed-in user \u2014 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 \u2014 and every call is recorded under <strong>More \u2192 Agent Access<\/strong>, attributed to the key that made it.<\/p><\/dd>\n<dt id=\"can%20ai%20help%20me%20write%20the%20description%2C%20topics%20and%20fixes%3F\"><h3>Can AI help me write the description, topics and fixes?<\/h3><\/dt>\n<dd><p>Yes, if you're on WordPress 7.0 and have set up an AI provider under Settings \u2192 AI. Then <strong>Draft with AI<\/strong> appears on the AI description field, <strong>Suggest with AI<\/strong> on the Topics field, and <strong>Fix with AI<\/strong> on any AI Readability row that needs work. Agentimus asks <em>your<\/em> AI through WordPress's shared connectors \u2014 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.<\/p><\/dd>\n<dt id=\"can%20ai%20write%20a%20whole%20post%20for%20me%3F\"><h3>Can AI write a whole post for me?<\/h3><\/dt>\n<dd><p>Yes \u2014 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. <strong>Create draft<\/strong> opens the post in the editor, where image placeholders arrive with their alt text ready \u2014 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 <strong>Let connected agents write<\/strong> switch on and an AI provider under Settings \u2192 AI, and it never publishes: drafts and pending review only.<\/p><\/dd>\n<dt id=\"does%20ai%20visibility%20use%20the%20ai%20provider%20i%20set%20up%20in%20wordpress%3F\"><h3>Does AI Visibility use the AI provider I set up in WordPress?<\/h3><\/dt>\n<dd><p>No \u2014 it needs its own API keys, and that's on purpose. A visibility check is graded on the <strong>sources each engine cited<\/strong>, 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 \u2192 AI Visibility). They stay on your server and are used for nothing else.<\/p><\/dd>\n<dt id=\"how%20do%20i%20make%20my%20plugin%20appear%20in%20the%20discovery%20document%3F\"><h3>How do I make my plugin appear in the discovery document?<\/h3><\/dt>\n<dd><p>Add a single optional action \u2014 no dependency, no library. If Agentimus isn't installed the hook simply never fires:<\/p>\n\n<pre><code>add_action( 'wpdiscovery_register', function ( $registry ) {\n    $registry-&gt;register( array( 'id' =&gt; 'acme', 'title' =&gt; 'Acme', 'type' =&gt; 'commerce' ) );\n} );\n<\/code><\/pre>\n\n<p>Agentimus also fires the product-aliased <code>agentimus_register<\/code>; you may hook either. See <code>examples\/integrate-your-plugin.php<\/code> for the full resource schema (capabilities, endpoints, auth, agent cards, MCP tools).<\/p><\/dd>\n<dt id=\"which%20hooks%20can%20my%20plugin%20use%3F\"><h3>Which hooks can my plugin use?<\/h3><\/dt>\n<dd><p>Registration is a single action, but Agentimus exposes more for deeper integrations, grouped by stability:<\/p>\n\n<ul>\n<li><strong>Stable<\/strong> \u2014 frozen at WP_Discovery spec 1.0; build on these: the <code>wpdiscovery_register<\/code> action with its <code>$registry-&gt;register()<\/code> \/ <code>add_well_known()<\/code> API, plus <code>agentimus_entity_types<\/code> and the <code>agentimus_cache_flushed<\/code> action.<\/li>\n<li><strong>Extension<\/strong> \u2014 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 \u2014 e.g. <code>agentimus_envelope<\/code>, <code>agentimus_documents<\/code>, <code>agentimus_mcp<\/code>, <code>agentimus_agent_skills<\/code>, <code>agentimus_well_known_routed<\/code>, <code>agentimus_post_types<\/code>, <code>agentimus_security_txt<\/code>.<\/li>\n<li><strong>Internal<\/strong> \u2014 advanced site-owner tuning (Guard, Classifier, Activity, Settings); not a third-party integration surface.<\/li>\n<\/ul>\n\n<p>Every hook, with its signature and tier, is catalogued in <code>examples\/all-hooks-reference.php<\/code>.<\/p><\/dd>\n<dt id=\"is%20the%20discovery%20format%20an%20open%20standard%20i%20can%20read%3F\"><h3>Is the discovery format an open standard I can read?<\/h3><\/dt>\n<dd><p>Yes. The discovery document implements the <strong>WP_Discovery Protocol<\/strong>, an openly-licensed (CC BY 4.0) specification \u2014 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.<\/p><\/dd>\n<dt id=\"does%20agentimus%20store%20ip%20addresses%3F\"><h3>Does Agentimus store IP addresses?<\/h3><\/dt>\n<dd><p>Not by default. The agent-activity log records who fetched your endpoints with no IP addresses at all. One opt-in setting \u2014 <em>Store IP addresses for flagged clients<\/em> \u2014 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 \u2192 Privacy).<\/p><\/dd>\n<dt id=\"is%20the%20admin%20interface%20built%20from%20source%20i%20can%20inspect%3F\"><h3>Is the admin interface built from source I can inspect?<\/h3><\/dt>\n<dd><p>Yes \u2014 there is no minified-only code. The admin interface is built from Vue 3 source in <code>resources\/<\/code> with Vite; the source and <code>vite.config.js<\/code> ship in this package and also live in the public repository at https:\/\/github.com\/heera\/agentimus . Run <code>npm install &amp;&amp; npm run build<\/code> to regenerate <code>assets\/admin\/<\/code> from source.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.33.0<\/h4>\n\n<ul>\n<li>New: Classic search, measured \u2014 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.<\/li>\n<li>New: In Google's Index \u2014 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 \u2014 plus week-on-week trend, Google Discover, and the health of the sitemap you registered.<\/li>\n<li>New: Found by AI Search \u2014 how much of your site Bing's index holds and how cleanly its crawler gets in; ChatGPT search and Copilot read this index today.<\/li>\n<li>New: Cloudflare edge panel (opt-in, your own token) \u2014 what the edge answered or blocked before your server ever saw the request, with a warning when the edge disagrees with your crawler policy.<\/li>\n<li>New: a setup wizard on first visit, and an agent-ready front door \u2014 SKILL.md, auth.md, and an MCP handshake that answers strangers politely.<\/li>\n<li>Fixed: the promoted XML sitemap now serves at WordPress's standard \/wp-sitemap.xml, and the old addresses redirect to it \u2014 a moved sitemap had been silently failing search-console registrations.<\/li>\n<li>Improved: every data screen names whose behavior it counts \u2014 people or machines \u2014 and every external data pull is chunked or budgeted, resumes after failure, and reports what happened in words.<\/li>\n<\/ul>\n\n<h4>1.32.0<\/h4>\n\n<ul>\n<li>New \u2014 <strong>Connect an assistant by approval, not by key.<\/strong> Give an AI assistant your MCP address and it asks <em>you<\/em> for permission: a consent page on your own site names what it calls itself, where it will return, and lets you choose <strong>Read only<\/strong> or <strong>Read and write<\/strong> \u2014 you can grant less than it asked for. Approving gives that one assistant its own key; every connection is listed under <strong>Connected assistants<\/strong> 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 \u2014 nothing is brokered by anyone else. Verified with Claude, Cursor and ChatGPT (ChatGPT connects behind its Developer-mode switch).<\/li>\n<li>New \u2014 <strong>A shared token for assistants that can't ask.<\/strong> 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 \u2014 Agentimus stores only a fingerprint, never the secret.<\/li>\n<li>New \u2014 <strong>A read-only key is shown read-only tools.<\/strong> 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 \u2014 and publishing stays off unless you allow it.<\/li>\n<li>Fixed \u2014 <strong>Discovery for clients that compute the address themselves.<\/strong> 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 \u2014 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.<\/li>\n<li>Improved \u2014 <strong>Agent Access grew a proper table.<\/strong> The events feed is a real table with column headings on wide screens \u2014 same discs, pills and stamps, without repeating \"First seen\" on every row \u2014 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.<\/li>\n<li>Improved \u2014 <strong>The roster says how each key got in.<\/strong> 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 \u2014 which ends every connection using the shared token \u2014 from rotating it for a fresh secret.<\/li>\n<li>Improved \u2014 <strong>The MCP card, rebuilt around the address.<\/strong> One status line (running, tool count, last call), your server address up front with a Copy button \u2014 that address <em>is<\/em> the setup now \u2014 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.<\/li>\n<li>New \u2014 <strong>Conflict honesty in Readiness.<\/strong> Agentimus checks its own <code>\/llms.txt<\/code> 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.<\/li>\n<li>New \u2014 <strong>Robots watch.<\/strong> If your robots.txt changes \u2014 by another plugin, a host setting, or your own hand \u2014 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.<\/li>\n<li>Fixed \u2014 <strong>The internal-link tool reaches agents at last.<\/strong> 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.<\/li>\n<li>Fixed \u2014 <strong>Assistants that use their own callback address can connect.<\/strong> Desktop clients register a private return address (<code>claude:\/\/\u2026<\/code>); these were being silently discarded, so registration failed with a misleading error. Executable and malformed addresses are still refused.<\/li>\n<li>Fixed \u2014 <strong>Screens stop waiting to be reloaded.<\/strong> 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.<\/li>\n<li>Improved \u2014 <strong>Agent Access names the door.<\/strong> A call made with the shared token reads \"via connection token\", and one made by an approved assistant reads \"via Claude's connection\" \u2014 the identity you approved, not a name the caller claimed for itself.<\/li>\n<\/ul>\n\n<h4>1.31.0<\/h4>\n\n<ul>\n<li>New \u2014 <strong>Share drafts, written from the post.<\/strong> The editor panel grows a <strong>Share<\/strong> 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 \u2014 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.<\/li>\n<li>New \u2014 <strong>Ask AI about this post.<\/strong> 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 \u2014 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.<\/li>\n<li>Improved \u2014 <strong>Screens load like screens.<\/strong> 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\u2026\" \u2014 or, on Agent Access, nothing at all.<\/li>\n<li>Fixed \u2014 <strong>The request-log tool answers MCP clients again.<\/strong> 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.<\/li>\n<li>New \u2014 <strong>Signed agents, verified mathematically.<\/strong> Some AI agents now cryptographically sign their requests \u2014 Google's agent and OpenAI's already do. With <strong>Verify bot identities<\/strong> on, Agentimus checks the signature right on your own server (Web Bot Auth, the emerging open standard): a genuine agent earns a <strong>signed<\/strong> mark in the Request Log, and a forged signature \u2014 someone pretending to be a signer \u2014 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 <em>External services<\/em>).<\/li>\n<li>New \u2014 <strong>Link to your own posts.<\/strong> A new editor box suggests which of your own posts the one you're writing should link to \u2014 found from your topics, categories and text, instantly, no AI needed \u2014 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.<\/li>\n<li>New \u2014 <strong>A refusal is never silent.<\/strong> Requests turned away at your AI endpoints \u2014 proven impostors, forged signatures \u2014 are now recorded: they show in the Request Log as <strong>refused<\/strong> 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.<\/li>\n<li>Improved \u2014 <strong>Agent Access reads as a feed.<\/strong> 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.<\/li>\n<li>Improved \u2014 <strong>The Request Log says more per row.<\/strong> A new Status column carries one honest mark per request \u2014 verified, signed, spoofed, forged, refused \u2014 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.<\/li>\n<li>Improved \u2014 <strong>The Optimize worklist works in bigger strokes.<\/strong> Each check's section gains a one-click <strong>Ignore All<\/strong> \u2014 every page that check flags, including the ones past the \"Showing 6 of 8\" preview \u2014 the aside list gains a matching <strong>Restore All<\/strong>, 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.<\/li>\n<li>Fixed \u2014 <strong>One broken discovery extension no longer silences the rest.<\/strong> If another plugin extending Agentimus's discovery documents fails, its entry is skipped and named in an admin notice \u2014 everyone else's still ships.<\/li>\n<\/ul>\n\n<p>Earlier releases \u2014 the full history, in the same words \u2014 live in <a href=\"https:\/\/github.com\/heera\/agentimus\/blob\/main\/CHANGELOG.md\">CHANGELOG.md<\/a> in the plugin's source repository.<\/p>","raw_excerpt":"Make your site agent-ready: AI SEO (AEO\/GEO), llms.txt &amp; bot control \u2014 be found, read &amp; cited by AI \u2014 and write, edit &amp; publish via MCP.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/328611","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=328611"}],"author":[{"embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/heera"}],"wp:attachment":[{"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=328611"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=328611"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=328611"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=328611"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=328611"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/bn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=328611"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}