Ajay Maurya

AJ Agent Crawl Optimizer 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 — all without changing anything for human visitors.
Each capability is a separate toggle under Settings → AJ Agent Crawl Optimizer and ships opt-in (everything starts off). On first activation, a one-time Quick Setup wizard 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).
<h4>Discovery — help agents find what your site offers</h4>
<ul>
<li>API Catalog (RFC 9727) — <code>/.well-known/api-catalog</code> linkset advertising your REST API, plus a <code>Link: rel="api-catalog"</code> header on every response so agents discover it from any URL.</li>
<li>MCP Server Card (SEP-1649 draft) — <code>/.well-known/mcp/server-card.json</code> describing the site to MCP-aware agents.</li>
<li>Agent Skills Index (RFC v0.2.0) — <code>/.well-known/agent-skills/index.json</code> listing six skills (search, posts, pages, media, categories, tags) plus per-skill <code>SKILL.md</code> artifacts with verifiable sha256 digests.</li>
<li>llms.txt (per llmstxt.org) — <code>/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>
<li>IndexNow — non-blocking ping to Bing and Yandex on every post publish so search engines re-crawl within minutes.</li>
</ul>
<h4>Presentation — format content for agents</h4>
<ul>
<li>Markdown Negotiation — when a request includes <code>Accept: text/markdown</code>, the page is served as clean Markdown with <code>X-Markdown-Tokens</code> for context budgeting. Browsers (which send <code>text/html</code>) are completely unaffected.</li>
<li>JSON-LD Schema — Schema.org structured data: WebSite, Organization, Article, BreadcrumbList, and auto-detected FAQPage. Logo resolved from your theme’s custom logo or site icon.</li>
<li>OpenAPI 3.0.3 — <code>/?format=openapi</code> returns a complete spec generated dynamically from <code>rest_get_server()</code>, including plugin-registered REST routes.</li>
<li>WebMCP Tools — registers four tools (search, posts, pages, site info) via <code>navigator.modelContext.provideContext()</code> for browsers that support the W3C WebMCP draft.</li>
</ul>
<h4>Declarations</h4>
<ul>
<li>Content-Signals — appends a <code>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 — their additions are preserved, our line lands at the very end.</li>
</ul>
<h4>Why use it</h4>
<ul>
<li>No conflicts with your SEO plugin. 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>
<li>Multisite-aware. Every endpoint also resolves at <code>/{subsite}/...</code> paths automatically.</li>
<li>Cached. 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>
<li>Performance-conscious. Markdown handler runs at <code>PHP_INT_MAX</code> priority so it doesn’t break object-cache flushes or Query Monitor. IndexNow pings are non-blocking.</li>
<li>Extensible. Nine filter hooks let you customize skills, schemas, capabilities, and content. See “For Developers” below.</li>
<li>Accessible. Score-card SVG has dynamic <code>aria-label</code>, copy buttons announce success via <code>aria-live</code>, decorative arrows hidden from screen readers via CSS pseudo-elements.</li>
</ul>
<h4>For developers</h4>
The plugin exposes nine filter hooks for extension. Examples:
<pre><code>add_filter( 'ajaco_required_capability', function () { return 'edit_posts'; } );
</code></pre>
Delegate plugin access to a non-admin role.
<pre><code>add_filter( 'ajaco_skill_definitions', function ( $skills ) { return $skills + [ 'products' => [ 'type' => 'information-retrieval', 'description' => 'WooCommerce products', 'endpoint' => rest_url( 'wc/v3/products' ) ] ]; } );
</code></pre>
Register custom skills that ship in the Agent Skills Index and are served as SKILL.md artifacts with verifiable sha256 digests.
<pre><code>add_filter( 'ajaco_content_signal', function () { return 'ai-train=yes, search=yes, ai-input=yes'; } );
</code></pre>
Customize the Content-Signal directive (e.g. permit AI training).
Other hooks: <code>ajaco_api_catalog_linkset</code>, <code>ajaco_mcp_server_card</code>, <code>ajaco_json_ld_graph</code>, <code>ajaco_openapi_spec</code>, <code>ajaco_llms_txt_content</code>, <code>ajaco_active_seo_plugin</code>. The settings page’s Help tab → For Developers lists all of them with descriptions.
<h3>External services</h3>
This plugin connects to one external service, and only when the corresponding feature is explicitly enabled by the site administrator.
<h4>IndexNow (api.indexnow.org)</h4>
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.
When data is sent: only when the IndexNow 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 <code>publish</code> status, the plugin fires a single non-blocking HTTPS POST to <code>https://api.indexnow.org/indexnow</code>.
What data is sent: the request body is a JSON document containing exactly three fields — your site’s host (e.g. <code>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.
If the IndexNow feature toggle is off (the default), the plugin makes no outbound network requests of any kind.
This service is provided by Microsoft (Bing) and the IndexNow project. Their terms and privacy policies apply:
<ul>
<li>IndexNow protocol documentation: https://www.indexnow.org/documentation</li>
<li>IndexNow FAQ and terms: https://www.indexnow.org/faq</li>
<li>Microsoft Bing Webmaster Guidelines : https://www.bing.com/webmasters/help/webmaster-guidelines-30fba23a</li>
<li>Microsoft Privacy Statement: https://www.microsoft.com/en-us/privacy/privacystatement</li>
</ul>
<h3>Privacy</h3>
AJ Agent Crawl Optimizer stores data only on your own server — there is no telemetry, no analytics, and no third-party logging. Specifically:
<h4>Local data</h4>
<ul>
<li>Plugin option rows in the WordPress options table store toggle states and the IndexNow API Key (stored as plain text — keep your database secure).</li>
<li>Transients cache the OpenAPI document and llms.txt body. These are deleted on plugin uninstall.</li>
<li>No request data, IP addresses, User-Agents, or visitor information is recorded by the plugin.</li>
</ul>
<h4>Outbound network calls</h4>
The plugin makes exactly one outbound HTTP request, and only when explicitly enabled:
<ul>
<li>IndexNow — when the IndexNow toggle is on and a key is configured, the plugin sends a non-blocking POST to <code>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>
</ul>
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.
<h4>Cookies</h4>
The plugin does not set any cookies.
<h4>Uninstall</h4>
When the plugin is deleted (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.

AJ Agent Crawl Optimizer


Helpful plugin to bridge the gap between standard WordPress SEO website and AI Crawler tools. Good Job Ajay!


Quick and Easy way of making your website AI crawler reach

Make your WordPress site legible to AI agents — Markdown negotiation, JSON-LD, OpenAPI, MCP server card, llms.txt, IndexNow, and more.

MksDdn Collection for Postman helps developers quickly generate a Postman Collection (v2.1.0) or OpenAPI 3.0 documentation for WordPress REST API endpoints. The plugin automatically discovers and includes standard WordPress entities, custom post types, options pages, and individual pages. Generated collections include pre-configured requests with sample data and can be downloaded as JSON files for import into Postman. OpenAPI spec can be used with Swagger UI, Redoc, or frontend code generators.
The plugin provides comprehensive API testing capabilities with automatic generation of test data for form submissions, support for file uploads via multipart/form-data, and seamless integration with Advanced Custom Fields (ACF). Special handling is included for the mksddn-forms-handler plugin when active.
Features: 
– Basic REST endpoints: pages, posts, categories, tags, taxonomies, comments, users, settings 
– WooCommerce REST API (wc/v3): products, product categories, orders with full CRUD when WooCommerce is active 
– Search functionality: Posts, Pages, and All content types with customizable queries 
– Custom Post Types with full CRUD operations (List, Get by Slug/ID, Create, Update, Delete) 
– ACF/SCF fields: auto-included for all post types when ACF or Smart Custom Fields plugin is active 
– Special handling for Forms (mksddn-forms-handler integration) 
– Options endpoints: <code>/wp-json/custom/v1/options/...</code> 
– Individual pages by slug with ACF field support 
– Automatic test data generation for form submissions 
– Support for multipart/form-data for file uploads 
– Yoast SEO integration (automatic yoast_head_json inclusion) 
– Multilingual support with Accept-Language headers (Polylang priority) 
– OpenAPI 3.0 export for API documentation (Swagger UI, Redoc) 
– Extensible via WordPress filters 
– WP-CLI integration for command-line usage
<h3>External services</h3>
This plugin references external services for Postman Collection schema validation:
Postman Collection Schema Service 
– Service: Postman Collection Schema (schema.getpostman.com) 
– Purpose: Used to validate and structure the generated Postman Collection JSON according to the official Postman Collection v2.1.0 specification 
– Data sent: No data is sent to this service. The plugin only references the schema URL for validation purposes 
– When: The schema URL is included in the generated collection metadata for Postman to validate the collection structure 
– Terms of service: https://www.postman.com/legal/terms-of-use/ 
– Privacy policy: https://www.postman.com/legal/privacy-policy/
Note: This plugin does not send any user data to external services. The schema reference is purely for collection structure validation within the Postman application.

MksDdn Collection for Postman

Generate Postman Collection (v2.1.0) or OpenAPI 3.0 documentation for the WordPress REST API from the admin UI.

AJ Agent Crawl Optimizer vs MksDdn Collection for Postman