{"id":10566,"date":"2026-05-16T18:32:07","date_gmt":"2026-05-16T10:32:07","guid":{"rendered":"https:\/\/aeosub.com\/aj-agent-crawl-optimizer\/"},"modified":"2026-05-16T18:32:07","modified_gmt":"2026-05-16T10:32:07","slug":"aj-agent-crawl-optimizer","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/aj-agent-crawl-optimizer\/","title":{"rendered":"AJ Agent Crawl Optimizer"},"content":{"rendered":"
\n\n\n\n\n\n\n\n
Developer<\/th>\nAjay Maurya<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv1.0.0<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n5.5 \/ 6.9.4<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-05-16 10:00am GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details \u2192<\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Make your WordPress site legible to AI agents \u2014 Markdown negotiation, JSON-LD, OpenAPI, MCP server card, llms.txt, IndexNow, and more.<\/div>\n

AJ Agent Crawl Optimizer<\/strong> is a thin compatibility layer that teaches your site to speak the languages AI agents already use to discover and consume web content. It publishes machine-readable manifests at well-known URLs, serves clean Markdown when an AI requests it, and declares your AI-usage preferences \u2014 all without changing anything for human visitors.<\/p>\n

Each capability is a separate toggle under Settings \u2192<\/span> AJ Agent Crawl Optimizer<\/strong> and ships opt-in<\/strong> (everything starts off). On first activation, a one-time Quick Setup wizard<\/strong> suggests sensible defaults based on your environment (for example, it skips JSON-LD when an SEO plugin is detected so you don’t get duplicate structured data).<\/p>\n

Discovery \u2014 help agents find what your site offers<\/h4>\n
    \n
  • API Catalog<\/strong> (RFC 9727) \u2014 \/.well-known\/api-catalog<\/code> linkset advertising your REST API, plus a Link: rel=\"api-catalog\"<\/code> header on every response so agents discover it from any URL.<\/li>\n
  • MCP Server Card<\/strong> (SEP-1649 draft) \u2014 \/.well-known\/mcp\/server-card.json<\/code> describing the site to MCP-aware agents.<\/li>\n
  • Agent Skills Index<\/strong> (RFC v0.2.0) \u2014 \/.well-known\/agent-skills\/index.json<\/code> listing six skills (search, posts, pages, media, categories, tags) plus per-skill SKILL.md<\/code> artifacts with verifiable sha256 digests.<\/li>\n
  • llms.txt<\/strong> (per llmstxt.org) \u2014 \/llms.txt<\/code> curated, LLM-readable index of your top pages and recent posts, with a Discovery section auto-linking every other plugin endpoint.<\/li>\n
  • IndexNow<\/strong> \u2014 non-blocking ping to Bing and Yandex on every post publish so search engines re-crawl within minutes.<\/li>\n<\/ul>\n

    Presentation \u2014 format content for agents<\/h4>\n
      \n
    • Markdown Negotiation<\/strong> \u2014 when a request includes Accept: text\/markdown<\/code>, the page is served as clean Markdown with X-Markdown-Tokens<\/code> for context budgeting. Browsers (which send text\/html<\/code>) are completely unaffected.<\/li>\n
    • JSON-LD Schema<\/strong> \u2014 Schema.org structured data: WebSite, Organization, Article, BreadcrumbList, and auto-detected FAQPage. Logo resolved from your theme’s custom logo or site icon.<\/li>\n
    • OpenAPI 3.0.3<\/strong> \u2014 \/?format=openapi<\/code> returns a complete spec generated dynamically from rest_get_server()<\/code>, including plugin-registered REST routes.<\/li>\n
    • WebMCP Tools<\/strong> \u2014 registers four tools (search, posts, pages, site info) via navigator.modelContext.provideContext()<\/code> for browsers that support the W3C WebMCP draft.<\/li>\n<\/ul>\n

      Declarations<\/h4>\n
        \n
      • Content-Signals<\/strong> \u2014 appends a Content-Signal: ai-train=no, search=yes, ai-input=no<\/code> directive to robots.txt declaring your AI-usage preferences (per contentsignals.org). Composes with Yoast\/Rank Math\/AIOSEO \u2014 their additions are preserved, our line lands at the very end.<\/li>\n<\/ul>\n

        Why use it<\/h4>\n
          \n
        • No conflicts with your SEO plugin.<\/strong> JSON-LD auto-suppresses when Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO, Squirrly SEO, Schema Pro, or SASWP is active.<\/li>\n
        • Multisite-aware.<\/strong> Every endpoint also resolves at \/{subsite}\/...<\/code> paths automatically.<\/li>\n
        • Cached.<\/strong> OpenAPI is cached for a day, llms.txt for an hour, with proper invalidation on plugin activation, theme switch, post changes, and setting toggles.<\/li>\n
        • Performance-conscious.<\/strong> Markdown handler runs at PHP_INT_MAX<\/code> priority so it doesn’t break object-cache flushes or Query Monitor. IndexNow pings are non-blocking.<\/li>\n
        • Extensible.<\/strong> Nine filter hooks let you customize skills, schemas, capabilities, and content. See “For Developers” below.<\/li>\n
        • Accessible.<\/strong> Score-card SVG has dynamic aria-label<\/code>, copy buttons announce success via aria-live<\/code>, decorative arrows hidden from screen readers via CSS pseudo-elements.<\/li>\n<\/ul>\n

          For developers<\/h4>\n

          The plugin exposes nine filter hooks for extension. Examples:<\/p>\n

          add_filter( 'ajaco_required_capability', function () { return 'edit_posts'; } );\n<\/code><\/pre>\n
          Delegate plugin access to a non-admin role.<\/p>\n
          add_filter( 'ajaco_skill_definitions', function ( $skills ) { return $skills + [ 'products' => [ 'type' => 'information-retrieval', 'description' => 'WooCommerce products', 'endpoint' => rest_url( 'wc\/v3\/products' ) ] ]; } );\n<\/code><\/pre>\n
          Register custom skills that ship in the Agent Skills Index and are served as SKILL.md artifacts with verifiable sha256 digests.<\/p>\n
          add_filter( 'ajaco_content_signal', function () { return 'ai-train=yes, search=yes, ai-input=yes'; } );\n<\/code><\/pre>\n
          Customize the Content-Signal directive (e.g. permit AI training).<\/p>\n
          Other hooks: ajaco_api_catalog_linkset<\/code>, ajaco_mcp_server_card<\/code>, ajaco_json_ld_graph<\/code>, ajaco_openapi_spec<\/code>, ajaco_llms_txt_content<\/code>, ajaco_active_seo_plugin<\/code>. The settings page’s Help tab \u2192<\/span> For Developers lists all of them with descriptions.<\/p>\n
          External services<\/h3>\n
          This plugin connects to one external service, and only when the corresponding feature is explicitly enabled by the site administrator.<\/p>\n
          IndexNow (api.indexnow.org)<\/h4>\n
          What it is and what it’s used for: IndexNow is an open protocol (originally from Microsoft Bing and Yandex) that lets sites notify search engines the moment a URL is published or updated, so search engines can re-crawl within minutes instead of days.<\/p>\n
          When data is sent: only when the IndexNow<\/strong> feature toggle is turned on AND an IndexNow API Key is configured on the settings page. In that case, every time a post of a public post type transitions to the publish<\/code> status, the plugin fires a single non-blocking HTTPS POST to https:\/\/api.indexnow.org\/indexnow<\/code>.<\/p>\n
          What data is sent: the request body is a JSON document containing exactly three fields \u2014 your site’s host (e.g. example.com<\/code>), your IndexNow API key (which you generated yourself at Bing Webmaster Tools), and the permalink URL of the post that was just published. No visitor information, IP addresses, user-agents, or post content is sent.<\/p>\n
          If the IndexNow feature toggle is off (the default), the plugin makes no outbound network requests of any kind.<\/p>\n
          This service is provided by Microsoft (Bing) and the IndexNow project. Their terms and privacy policies apply:<\/p>\n
            \n
          • IndexNow protocol documentation: https:\/\/www.indexnow.org\/documentation<\/li>\n
          • IndexNow FAQ and terms: https:\/\/www.indexnow.org\/faq<\/li>\n
          • Microsoft Bing Webmaster Guidelines : https:\/\/www.bing.com\/webmasters\/help\/webmaster-guidelines-30fba23a<\/li>\n
          • Microsoft Privacy Statement: https:\/\/www.microsoft.com\/en-us\/privacy\/privacystatement<\/li>\n<\/ul>\n
            Privacy<\/h3>\n
            AJ Agent Crawl Optimizer stores data only on your own server<\/strong> \u2014 there is no telemetry, no analytics, and no third-party logging. Specifically:<\/p>\n
            Local data<\/h4>\n
              \n
            • Plugin option rows<\/strong> in the WordPress options table store toggle states and the IndexNow API Key (stored as plain text \u2014 keep your database secure).<\/li>\n
            • Transients<\/strong> cache the OpenAPI document and llms.txt body. These are deleted on plugin uninstall.<\/li>\n
            • No request data, IP addresses, User-Agents, or visitor information is recorded by the plugin.<\/li>\n<\/ul>\n
              Outbound network calls<\/h4>\n
              The plugin makes exactly one<\/strong> outbound HTTP request, and only when explicitly enabled:<\/p>\n
                \n
              • IndexNow<\/strong> \u2014 when the IndexNow toggle is on and a key is configured, the plugin sends a non-blocking POST to https:\/\/api.indexnow.org\/indexnow<\/code> on every post publish. The payload contains the site host, the IndexNow key, and the URL of the published post (no visitor data).<\/li>\n<\/ul>\n
                If the IndexNow toggle is off (the default), the plugin makes zero outbound network requests. All other features (manifests, JSON-LD, robots.txt) only respond to incoming HTTP requests; they never call out.<\/p>\n
                Cookies<\/h4>\n
                The plugin does not set any cookies.<\/p>\n
                Uninstall<\/h4>\n
                When the plugin is deleted<\/strong> (not just deactivated), all plugin options, the IndexNow key, and all transients are removed from the database. Multisite networks have every site cleaned in turn.<\/p>\n","protected":false},"excerpt":{"rendered":"
                Make your WordPress site legible to AI agents \u2014 Markdown negotiation, JSON-LD, OpenAPI, MCP server card, llms.txt, IndexNow, and more.<\/p>","protected":false},"author":1,"featured_media":9317,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[550,608,930,931,894,555],"class_list":["post-10566","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-ai","tag-llms-txt","tag-mcp","tag-openapi","tag-structured-data","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/10566","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=10566"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/10566\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/9317"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=10566"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=10566"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=10566"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}