tommyoz12

<p>AI-Only Pages gives you granular control over which search engine bots can index each page on your WordPress site — while simultaneously making those pages more discoverable and useful for AI crawlers like ChatGPT, Claude, and Perplexity.</p>
<p><strong>The core idea:</strong> you have content that is perfect for AI training pipelines and retrieval-augmented generation (RAG) systems, but you do not want that content competing for rankings in Google, Bing, or Yahoo.</p>
<p>AI-Only Pages lets you mark those pages as AI-only: they disappear from traditional search engine indexes while becoming first-class citizens in the AI ecosystem.</p>
<h4>What it does</h4>
<ul>
<li><strong>Per-bot noindex</strong> — Block individual bots (Googlebot, Bingbot, Yandexbot, etc.) with a checkbox per bot per page. Checking one bot blocks it; the others still index normally.</li>
<li><strong>“Block All” master toggle</strong> — One click blocks all 10 supported search engine bots simultaneously.</li>
<li><strong><code><meta></code> tags and HTTP headers</strong> — Both <code><meta name="googlebot" content="noindex, nofollow"></code> HTML meta tags and <code>X-Robots-Tag</code> HTTP headers are emitted, covering all crawling contexts. Works correctly on all public post types including Pages and custom post types.</li>
<li><strong>SEO plugin integration</strong> — Suppresses Yoast SEO, WP Core, and RankMath’s global <code><meta name="robots"></code> tag on AI-only pages so there is no conflict between the global tag and your per-bot tags.</li>
<li><strong>Sitemap exclusion</strong> — AI-Only pages are automatically removed from all XML sitemaps (Yoast SEO and WP Core sitemaps are both supported).</li>
<li><strong><code>/llms-index.txt</code></strong> — A plain-text AI discovery file served at <code>yoursite.com/llms-index.txt</code> listing all AI-only pages with their titles and last-modified dates. AI crawlers can use this file to find your AI-optimised content directly. Can be toggled on/off from the settings page.</li>
<li><strong>Token Diet — clean AI output</strong> — When an AI crawler visits an AI-only page, the plugin serves a cleaned version of the HTML with navigation, sidebars, footers, cookie banners, inline styles, SVGs, and iframes stripped out. AI models receive pure content with minimal noise.</li>
<li><strong>Global Settings Page</strong> — A top-level “AI-Only Pages” menu in the WordPress admin sidebar lets you configure Token Diet and LLM Index behaviour globally, without touching code.</li>
<li><strong>Caching plugin notice</strong> — If WP Rocket, LiteSpeed Cache, or another full-page caching plugin is detected, an admin notice explains how to configure it to work alongside this plugin.</li>
</ul>
<h4>The Settings Page</h4>
<p>A full settings page is available under <strong>AI-Only Pages</strong> in the WordPress admin sidebar. It provides:</p>
<p><strong>Section 1 — Instructions & Status:</strong> A “How It Works” guide covering the meta box, Token Diet, and LLM Index. A live, clickable URL to your <code>/llms-index.txt</code> file with a green/red status indicator showing whether the index is active.</p>
<p><strong>Section 2 — LLM Index Settings:</strong> A toggle to enable or disable <code>/llms-index.txt</code> globally. When disabled, the endpoint returns a 404.</p>
<p><strong>Section 3 — Token Diet Master Control:</strong> A master toggle to enable or disable Token Diet entirely. When off, AI bots receive raw, full HTML — identical to what human visitors see.</p>
<p><strong>Section 4 — Granular Token Diet Stripping:</strong> Individual toggles for each category of content stripped:</p>
<ul>
<li>Strip structural layout (headers, footers, sidebars, navigation, cookie banners)</li>
<li>Strip <code><style></code> tags and embedded CSS</li>
<li>Strip <code><svg></code> elements (major token bloaters)</li>
<li>Strip <code><iframe></code> elements (maps, embeds, social widgets)</li>
<li>Strip <code><form></code> elements <em>(Warning: removes WooCommerce Add to Cart buttons)</em></li>
<li>Strip <code><script></code> tags <em>(Note: <code>application/ld+json</code> schema is always preserved)</em></li>
</ul>
<h4>Supported Search Engine Bots</h4>
<p>Googlebot (Web), Googlebot-Image, Googlebot-News, Googlebot-Video, AdsBot-Google, Bingbot, Slurp (Yahoo), DuckDuckBot, Baiduspider, YandexBot.</p>
<h4>AI Bots Welcomed</h4>
<p>GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, YouBot, Meta-ExternalAgent, Amazonbot, Bytespider, Diffbot, cohere-ai, anthropic-ai, AI2Bot, OAI-SearchBot, and more. These bots are detected automatically and served cleaned content when they visit an AI-only page.</p>
<h4>Developer-Friendly</h4>
<p>Every major behaviour is extensible via WordPress filters. See the <strong>Developer Reference</strong> section below. The Settings class hooks into filters at priority 5, leaving priorities 10 and above free for developer overrides — so your custom <code>add_filter()</code> calls always win.</p>
<h3>Using the Plugin</h3>
<h4>Per-page control</h4>
<ol>
<li>Open any post or page in the WordPress editor.</li>
<li>Find the <strong>AI-Only Pages</strong> meta box in the right sidebar.</li>
<li>Check individual bots to block them, or use <strong>Block from ALL search engine bots</strong> to check all at once.</li>
<li>Click <strong>Publish</strong> or <strong>Update</strong> to save. The noindex tags take effect immediately.</li>
<li>Visit <code>yoursite.com/llms-index.txt</code> to confirm your page appears in the AI content index.</li>
</ol>
<p><strong>Note:</strong> The master toggle requires JavaScript. The individual checkboxes always work regardless of JS state.</p>
<h4>Global settings</h4>
<ol>
<li>Go to <strong>AI-Only Pages</strong> in the WordPress admin sidebar.</li>
<li>Review the “How It Works” section and confirm your <code>/llms-index.txt</code> URL is live.</li>
<li>Use the <strong>LLM Index Settings</strong> card to enable or disable the discovery file.</li>
<li>Use the <strong>Token Diet — Master Control</strong> card to enable or disable all output cleaning.</li>
<li>Use the <strong>Token Diet — Granular Stripping</strong> card to select exactly which HTML elements are stripped from AI output.</li>
<li>Click <strong>Save Settings</strong>.</li>
</ol>
<h3>Developer Reference</h3>
<p>All filters are applied inside <code>AIOnly\Pages\Plugin</code>. The Settings class hooks at priority 5; standard developer priority is 10+.</p>
<p><strong><code>aionly_ai_crawler_signatures</code></strong><br />
Array of User-Agent substrings used for Layer 1 bot detection.<br />
    @param string[] $signatures<br />
    @return string[]</p>
<p><strong><code>aionly_strip_selectors</code></strong><br />
CSS-style selector strings passed to Pass 1 of Token Diet (structural removal). Supports element tag, #id, and .class (one class, no combinators).<br />
    @param string[] $selectors<br />
    @return string[]</p>
<p><strong><code>aionly_strip_token_bloat_tags</code></strong><br />
XPath query strings passed to Pass 2 of Token Diet (tag removal).<br />
    @param string[] $queries<br />
    @return string[]</p>
<p><strong><code>aionly_allowed_attributes</code></strong><br />
HTML attribute names kept on every element by Pass 3 of Token Diet. Everything else is stripped.<br />
    @param string[] $attributes<br />
    @return string[]</p>
<p><strong><code>aionly_should_clean_output</code></strong><br />
Boolean. Return false to disable Token Diet entirely for a specific post.<br />
    @param bool     $enabled  Default: true.<br />
    @param \WP_Post $post<br />
    @return bool</p>
<p><strong><code>aionly_enable_xrobots_headers</code></strong><br />
Boolean. Return false to suppress X-Robots-Tag HTTP headers.<br />
    @param bool     $enabled  Default: true.<br />
    @param \WP_Post $post<br />
    @return bool</p>
<p><strong><code>aionly_cache_ttl</code></strong><br />
Filter the transient TTL in seconds.<br />
    @param int $ttl  Default: 600 (10 minutes).<br />
    @return int</p>
<p><strong><code>aionly_llms_index_lines</code></strong><br />
Filter the array of text lines that make up llms-index.txt before output.<br />
    @param string[] $lines       Array of lines (including comment lines).<br />
    @param int[]    $active_ids  Post IDs included in the index.<br />
    @return string[]</p>
<p><strong><code>aionly_supported_post_types</code></strong><br />
Array of public post type slugs the plugin should support.<br />
    @param string[] $post_types<br />
    @return string[]</p>
<p><strong><code>aionly_use_heuristic_bot_detection</code></strong><br />
Boolean. Return false to disable Layer 2 heuristic bot detection.<br />
    @param bool $enabled  Default: true.<br />
    @return bool</p>
<h4>Code Examples</h4>
<p><strong>Disable heuristic bot detection (uptime monitors):</strong></p>
<pre><code>add_filter( 'aionly_use_heuristic_bot_detection', '__return_false' );
</code></pre>
<p><strong>Preserve WooCommerce forms (developer override — wins over settings page):</strong></p>
<pre><code>add_filter( 'aionly_strip_token_bloat_tags', function( $queries ) {
    return array_filter( $queries, function( $q ) {
        return $q !== '//form';
    } );
} );
</code></pre>
<p><strong>Add a custom strip selector:</strong></p>
<pre><code>add_filter( 'aionly_strip_selectors', function( $selectors ) {
    $selectors[] = '.advertisement';
    $selectors[] = '#newsletter-popup';
    return $selectors;
} );
</code></pre>
<p><strong>Keep <code>class</code> attributes in AI output:</strong></p>
<pre><code>add_filter( 'aionly_allowed_attributes', function( $attrs ) {
    $attrs[] = 'class';
    return $attrs;
} );
</code></pre>
<p><strong>Add a custom AI crawler signature:</strong></p>
<pre><code>add_filter( 'aionly_ai_crawler_signatures', function( $sigs ) {
    $sigs[] = 'FutureBot';
    return $sigs;
} );
</code></pre>
<p><strong>Restrict to specific post types:</strong></p>
<pre><code>add_filter( 'aionly_supported_post_types', function( $types ) {
    return [ 'post', 'page' ]; // Only posts and pages.
} );
</code></pre>
<p><strong>Disable Token Diet on a specific post (always wins, priority 10 > settings priority 5):</strong></p>
<pre><code>add_filter( 'aionly_should_clean_output', function( $enabled, $post ) {
    if ( 42 === $post->ID ) {
        return false; // Post 42 serves full HTML to AI bots.
    }
    return $enabled;
}, 10, 2 );
</code></pre>
<p><strong>Read a single setting value in custom code:</strong></p>
<pre><code>$token_diet_on = '1' === \AIOnly\Pages\Settings::get( 'token_diet_enabled' );
$all_settings  = \AIOnly\Pages\Settings::get_settings(); // Full array.
</code></pre>


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.

VaultDevLabs

<p>Find noindex tags, robots.txt blocks, canonical issues, redirects, sitemap gaps, and other SEO visibility problems before important pages disappear from search.</p>
<p>VDL Search Visibility Scanner checks sitemap coverage, robots.txt, noindex tags, canonical URLs, redirects, HTTP status, title tags, and meta descriptions so site owners can see which pages are discoverable, risky, invisible, or expected. It also includes a single-page checker for important URLs and exportable fix-first reports for developers, SEOs, or site owners.</p>
<p>This is not a ranking tracker, SEO content generator, backlink tool, or generic SEO suite. It focuses on technical discoverability signals.</p>
<p>This plugin does not force Google indexing, submit normal pages to Google’s Indexing API, or guarantee rankings.</p>
<h4>Common problems it helps catch</h4>
<ul>
<li>Important pages missing from your sitemap</li>
<li>Pages accidentally marked noindex</li>
<li>Canonical tags pointing somewhere unexpected</li>
<li>Redirect chains that confuse discovery</li>
<li>robots.txt or sitemap problems</li>
<li>Public pages with weak title or meta description signals</li>
<li>Utility pages correctly excluded from search</li>
</ul>
<h4>Built for</h4>
<ul>
<li>Site owners checking why pages may be hard for search engines to discover</li>
<li>SEOs doing a quick WordPress technical visibility audit</li>
<li>WooCommerce stores checking product/category discoverability</li>
<li>Agencies preparing fix-first reports for clients</li>
<li>Developers reviewing sitemap, canonical, robots, and noindex issues</li>
</ul>
<h4>What it checks</h4>
<ul>
<li>single important URL visibility checks</li>
<li>WordPress discourage search engines setting</li>
<li>robots.txt reachability</li>
<li>sitemap reachability</li>
<li>sitemap reference in robots.txt</li>
<li>homepage status</li>
<li>selected public pages and recent posts</li>
<li>noindex robots meta</li>
<li>canonical tag status</li>
<li>title tag presence</li>
<li>meta description presence</li>
<li>sitemap coverage gaps</li>
<li>basic redirect chains</li>
</ul>
<h4>Visibility Map</h4>
<p>Results are grouped into:</p>
<ul>
<li>Homepage</li>
<li>Pages</li>
<li>Posts</li>
<li>Sitemap</li>
<li>Robots</li>
</ul>
<p>Each result is classified as Discoverable, Risky, Invisible, or Expected with a priority label. The priority engine separates true visibility blockers from mild metadata cleanup.</p>
<p>Results also include a visibility impact label and classification reason so site owners can see why an item is urgent, moderate, low-impact, or expected.</p>
<h4>What to fix first</h4>
<p>The dashboard groups findings into:</p>
<ul>
<li>Fix now: true visibility blockers</li>
<li>Fix soon: discovery and coverage risks</li>
<li>Optional cleanup: metadata and content polish</li>
<li>Expected: utility, legal, search, and system exclusions</li>
</ul>
<p>Expected results are common utility-page signals, such as noindex on checkout or account pages, that should not be treated like broken public-page visibility.</p>
<h4>Single page checker</h4>
<p>Paste an important URL from the current site to quickly see whether it appears search-ready, blocked, missing from the sitemap, canonicalised elsewhere, redirected, or in need of review.</p>
<h4>Best first use</h4>
<p>Paste the page you care about most first. The single page checker shows whether that URL looks search-ready, blocked by noindex, missing from the sitemap, canonicalised elsewhere, redirected, or only needs metadata cleanup. Then run a full scan to build the fix-first report.</p>
<h4>Fix-first report</h4>
<p>Run a full scan to create a local report grouped into Fix now, Fix soon, Optional cleanup, and Expected exclusions. Export CSV or HTML to share with a developer, SEO, or site owner.</p>
<h4>Likely important pages</h4>
<p>The scanner highlights pages commonly important for search visibility, such as the homepage, shop pages, product pages, top-level pages, and posts. Utility pages such as cart, checkout, and account pages are kept calm when noindex is expected.</p>
<h4>External services</h4>
<p>The scanner runs locally against the current site and does not require an external API.</p>
<p>The “Get Help Fixing This” button is a normal external link to VaultDevLabs. No scan data is sent automatically. The link may include summary counts and the current site URL in the URL query so you can request a manual review.</p>
<h4>Optional manual review</h4>
<p>The plugin can show a local visibility report in wp-admin. If you want help interpreting the results, the “Get Help Fixing This” link opens VaultDevLabs in your browser. No scan data is sent automatically.</p>


VDL Search Visibility Scanner – Noindex, Sitemap & SEO Audit

Check whether WordPress pages are technically discoverable with noindex, robots.txt, canonical, sitemap, redirect, and status-code checks.

AI-Only Pages vs VDL Search Visibility Scanner – Noindex, Sitemap & SEO Audit