AJ Agent Crawl Optimizer – AI Readiness Scanner & llms.txt for WordPress
by Ajay Maurya 5 (3 reviews)

AJ Agent Crawl Optimizer – AI Readiness Scanner & llms.txt for WordPress

llms.txt + AI-readiness scanner for WordPress: get found by ChatGPT & Claude, manage AI crawlers in robots.txt, fix failures in one click.

AJ Agent Crawl Optimizer ranks #28,287 among WordPress.org plugins with 10+ active installations, a 5/5 rating from 3 reviews, and was last updated Jul 13, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.6 (Current: 7.1.2)
v2.0.0 Current Version v2.0.0
Updated 2 months ago Last Update on 13 Jul, 2026
Refreshed 10 hours ago Last Refreshed on
Top 50% by installs Downloads -16.5% this week
View on WordPress.org
Rank
#28,287
No change
Active Installs
10+
No change
KW Avg Position
64.7
0.7 worse
Downloads
1K
+3 today
Support Resolved
0%
No change
Rating
100%
Review 5 out of 5
5 (3 reviews)

Next Milestone 20

Total Progress 50%
10+ 20+
15,025
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 5 more installs to reach 20+

Rank Changes

27,890 28,878 29,866 30,854 31,842 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
27,890 28,878 29,866 30,854 31,842 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Current #28,287
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
0 10 20 30 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0
3 reviews
Overall 100%
5
3 (100%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version
2.0.0
Last Updated
Jul 13, 2026
Requires WP
5.6+
Tested Up To
7.0.6
PHP Version
7.4 or higher
Author
Ajay Maurya

Support & Rating

Rating
★ ★ ★ ★ ★ 5
Reviews
3
Support Threads
0
Resolved
0%

Keywords

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Frequently Asked Questions

Common questions about AJ Agent Crawl Optimizer – AI Readiness Scanner & llms.txt for WordPress

No. JSON-LD output 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. The settings page shows a clear notice when this happens. Our robots_txt filter runs at PHP_INT_MAX priority, so any rules your SEO plugin adds (sitemap URLs, custom Disallow, etc.) are preserved — our Content-Signal line is appended last.
No. Browsers send Accept: text/html and get the normal HTML response. The .well-known/..., /llms.txt, and ?format=openapi endpoints are paths a normal user never visits. The only thing added to the page HTML is a single JSON-LD <script> block (when no SEO plugin is active) and a small WebMCP script tag (which no-ops in browsers without the experimental flag).
Yes. Every endpoint resolves at both the root and per-subsite paths automatically — /llms.txt, /blog/llms.txt, /.well-known/api-catalog, /blog/.well-known/api-catalog, etc. Each subsite has its own settings.
Use the ajaco_required_capability filter. The plugin defaults to manage_options (admin-only); change it to any capability of your choice, e.g. edit_pages for editors: add_filter( 'ajaco_required_capability', function () { return 'edit_pages'; } ); I enabled IndexNow but I'm not seeing pings to Bing or Yandex. Check three things: (1) the IndexNow API Key field is filled in, (2) you're publishing a post of a public post type — revisions and autosaves are skipped, (3) you're on production. Pings are non-blocking, so failures are silent. Tail your server log for outbound requests to api.indexnow.org.
Yes. Use the relevant filter: ajaco_skill_definitions — register custom Agent Skills. ajaco_json_ld_graph — add custom Schema.org entries (Product, Recipe, Event, etc.). ajaco_llms_txt_content — append sections to or replace the llms.txt body. ajaco_openapi_spec — add securitySchemes, custom tags, additional servers. ajaco_api_catalog_linkset — add anchors or rels (e.g. for a GraphQL endpoint). ajaco_mcp_server_card — override transport / capabilities for a real MCP implementation. The Help tab's "For Developers" section on the settings page lists every hook.
Use the Reset to Defaults button under the Save Changes button on the settings page. It clears every plugin option, wipes cached endpoint outputs, and shows a confirmation dialog before wiping anything.
Minimal. The OpenAPI document is cached for a day in a transient and only regenerates on plugin activation/deactivation or theme switch. The llms.txt body is cached for an hour and invalidates on post edits, site name/description changes, and setting toggles. Endpoint handlers run on init only when the request path matches; on every other request they early-return after one regex check. The Markdown handler runs at PHP_INT_MAX priority on shutdown so it never breaks object-cache writes or other shutdown hooks.
The plugin doesn't include a built-in access log. To verify activity, check your server access log for User-Agents like GPTBot, ClaudeBot, OAI-SearchBot, Google-Extended, PerplexityBot, CCBot, Bytespider, etc. hitting any of the plugin endpoints.
Yes. Every feature is an independent toggle. Uncheck what you don't want and Save Changes. The corresponding behavior reverts immediately on the next request — no rewrite flush, no cache flush needed (the plugin handles cache invalidation itself).

Sign In / Register

You need to sign in or register to use this feature.