by tommyoz12
0 (0 reviews)
AI-Only Pages
Mark any page as AI-only. Hidden from search engines, optimized for AI crawlers, listed in /llms-index.txt. Includes Token Diet and global settings.
Tested up to WP 6.7.5 (Current: 6.9.4)
v1.3.4
Current Version v1.3.4
Updated 3 days ago
Last Update on 16 Apr, 2026
Refreshed 11 hours ago
Last Refreshed on
Rank
#58,493
—
No change
Active Installs
0+
—
No change
KW Avg Position
140.7
—
No change
Downloads
275
+3 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
18,114
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
Need 10 more installs to reach 10+
Rank Changes
Current
#58,493
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 3 of 3| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| LLM | 106 | — | Tag | 1 month ago |
| noindex | 128 | — | Tag | 1 month ago |
| robots | 188 | — | Tag | 1 month ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.4
- Last Updated
- Apr 16, 2026
- Requires WP
- 5.5+
- Tested Up To
- 6.7.5
- PHP Version
- 7.4 or higher
- Author
- tommyoz12
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,718
Master Addons For Elementor – Widgets, Extensions, Theme Builder, Popup Builder & Template Kits
30K+ installs
#960
The SEO Framework – Fast, Automated, Effortless.
200K+ installs
#271
Smash Balloon Social Post Feed - Simple Social Feeds for WordPress
200K+ installs
#277
VK All in One Expansion Unit
100K+ installs
#299
Frequently Asked Questions
Common questions about AI-Only Pages
Google may have already crawled and cached the page before you activated the plugin. It can take days or weeks for Google to re-crawl and respect the new noindex directive. If you need faster removal, submit the URL to Google Search Console's URL Removal tool. Also verify that the noindex tag is actually appearing on the page: view source and search for <meta name="googlebot". The noindex tags are not appearing on my Pages (not Posts). This was a bug fixed in version 1.3.1. Both output_noindex_tags() and output_xrobots_headers() incorrectly checked publicly_queryable to decide whether to proceed. WordPress's built-in page post type has publicly_queryable = false, causing both methods to silently bail out without writing any tags. Update to 1.3.1 to resolve this.
Yes. The plugin overrides the global <meta name="robots"> tag that Yoast SEO and RankMath output on AI-only pages. Without this override, Yoast might output <meta name="robots" content="index, follow"> which would conflict with the per-bot tags. On AI-only pages, the global tag is suppressed entirely; only the per-bot tags remain.
First, check that LLM Index is enabled on the AI-Only Pages settings page. If it is enabled, go to Settings → Permalinks and click Save Changes without changing anything. This flushes WordPress's rewrite rules, which registers the /llms-index.txt URL pattern. This flush happens automatically on plugin activation, but some server configurations (particularly Nginx without try_files) may need a manual flush or a server config update. My caching plugin is serving the same page to both humans and AI bots. Full-page caching plugins (WP Rocket, LiteSpeed, W3 Total Cache, etc.) serve responses from a disk cache before WordPress runs. The plugin's output buffer never fires on cached pages. To fix this, configure your caching plugin to exclude AI-Only page URLs from its cache: WP Rocket: Settings → Cache → Never Cache URL(s). Add the slug of each AI-only page. LiteSpeed Cache: LiteSpeed Cache → Cache → Do not cache URIs. W3 Total Cache: Performance → Page Cache → Never cache the following pages. Alternatively, add a custom rule to exclude pages with the _aionly_active cookie, or contact your host's support team — managed WordPress hosts often expose this setting in their dashboard. My uptime monitor or API client is being treated as an AI bot. The plugin uses two-layer bot detection. Layer 1 matches known AI crawler signatures. Layer 2 (heuristic) flags requests with no browser engine string in the User-Agent AND no Accept-Language header — a combination that every real browser always sends, but that many CLI tools and monitoring services do not. The simplest fix is to configure your monitoring tool to send an Accept-Language header. Alternatively, disable heuristic detection entirely: add_filter( 'aionly_use_heuristic_bot_detection', '__return_false' );
Yes, if "Strip <form> elements" is enabled in the settings (it is by default). WooCommerce add-to-cart buttons are rendered inside <form> elements. AI crawlers cannot interact with forms anyway — they only read content. If you want AI crawlers to see your product CTAs, turn off "Strip forms" on the AI-Only Pages settings page, or add a developer filter: add_filter( 'aionly_strip_token_bloat_tags', function( $queries ) { return array_filter( $queries, function( $q ) { return $q !== '//form'; } ); } );
No. Disabling a toggle simply passes more of the original HTML through to the AI crawler. The page is never broken — it may just contain more noise that uses up the crawler's context window. The defaults are optimised for maximum signal-to-noise ratio.
No. Settings only affect the output buffer and filter callbacks — they have no impact on WordPress rewrite rules. Changes take effect on the very next AI crawler request.
All settings are stored in a single wp_options row with the key aionly_pages_settings as a serialised array. You can inspect or export it like any other WordPress option.
class-settings.php uses the same public add_filter() hooks that the core plugin exposes to developers. Specifically: aionly_should_clean_output — used to disable Token Diet when the master toggle is off. aionly_strip_token_bloat_tags — used to build a dynamic XPath query array from granular toggles. aionly_strip_selectors — used to empty the structural selector list when layout stripping is off. template_redirect at priority 0 — used to return a 404 for /llms-index.txt when the LLM Index is disabled. All these hooks run at priority 5, which means developer overrides at priority 10 (the WordPress default) always take precedence. Your custom filters always win.