[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqrCaRqjyn2jsfs3QfcVGzlkw6QXRdae0s4r9KO6Xc5U":3,"$f4hb8TZhLbeO45KvlqywOZ3Hb-ZSSPO-Q7KhGD5nvInQ":129,"$fBNaPqmwZnpO-2c1502ZEhkJ7OIUmECPY1KZN2jotxpc":134},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":26,"fingerprints":26},"llmaffiliate-ai-traffic-monetizer","LLMAffiliate AI Traffic Monetizer","1.0.8","llmaffiliate01","https:\u002F\u002Fprofiles.wordpress.org\u002Fllmaffiliate01\u002F","\u003Cp>\u003Cstrong>LLMAffiliate AI Traffic Monetizer\u003C\u002Fstrong> is a WordPress plugin that detects Large Language Model (LLM) traffic and dynamically serves enhanced content while ensuring compliance with search engine parity requirements.\u003C\u002Fp>\n\u003Cp>It mirrors the behavior of an interception layer (e.g., Cloudflare Worker) directly inside WordPress, enabling controlled content delivery for AI crawlers and agents.\u003C\u002Fp>\n\u003Ch4>CORE FEATURES\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Detects major LLM user agents including ChatGPT, Claude, Gemini, Copilot, Perplexity, Pi, LLaMA, Grok, Cohere, Mistral, Anthropic, and OpenAI.\u003C\u002Fli>\n\u003Cli>Ensures Googlebot and search engine crawlers always receive original content (configurable parity enforcement).\u003C\u002Fli>\n\u003Cli>Serves enhanced HTML responses via a remote content service.\u003C\u002Fli>\n\u003Cli>Automatically falls back to native WordPress rendering if the external service fails.\u003C\u002Fli>\n\u003Cli>Adds cache-control, licensing, and optional Text and Data Mining headers.\u003C\u002Fli>\n\u003Cli>Supports secure QA overrides using HMAC-signed query parameters.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>HOW IT WORKS\u003C\u002Fh4>\n\u003Cp>The plugin intercepts incoming HTTP requests and:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Identifies whether the request originates from an LLM or standard browser.\u003C\u002Fli>\n\u003Cli>If LLM traffic is detected:\n\u003Cul>\n\u003Cli>Fetches enhanced content from a configured external service.\u003C\u002Fli>\n\u003Cli>Applies headers and response transformations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>If the service fails:\n\u003Cul>\n\u003Cli>Falls back to WordPress rendering safely.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Ensures search engines always receive unmodified content.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>USE CASES\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>AI traffic handling and request analysis\u003C\u002Fli>\n\u003Cli>Controlled content delivery for LLM vs. human visitors\u003C\u002Fli>\n\u003Cli>Response parity handling (search engines receive origin content)\u003C\u002Fli>\n\u003Cli>Experimentation with LLM-specific rendering in compliant deployments\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>OPERATIONAL LOGGING & PRIVACY\u003C\u002Fh4>\n\u003Cp>An in-plugin setting (\u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> LLMAffiliate AI Traffic \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Advanced Detection Settings\u003C\u002Fstrong>) allows you to disable request and suspicious-event logging. When disabled, no logs are stored. When enabled (default), the plugin may store operational or security logs. These may include:\u003Cbr \u002F>\n* IP address\u003Cbr \u002F>\n* User agent\u003Cbr \u002F>\n* Requested URL\u003Cbr \u002F>\n* Referer\u003Cbr \u002F>\n* Selected HTTP headers\u003Cbr \u002F>\n* Detection and decision metadata\u003Cbr \u002F>\n* Suspicious-event or request logs\u003C\u002Fp>\n\u003Cp>This logging is used for debugging, security analysis, and request classification. Data is stored within your WordPress database. Configure and retain logs in accordance with your privacy policy and applicable regulations.\u003C\u002Fp>\n\u003Ch4>AI TERMS PAGE\u003C\u002Fh4>\n\u003Cp>The plugin can serve a public \u003Ccode>\u002Fai-terms\u003C\u002Fcode> page (or equivalent) that displays your site’s AI usage and content terms. It functions as a site-published policy page that visitors—including AI systems and human readers—can view. Site owners are responsible for the contents and legal suitability of the terms. The plugin includes a default template; you may customize it to match your needs.\u003C\u002Fp>\n\u003Ch4>GOOGLE SEARCH CONSOLE (OPTIONAL)\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>LLMAffiliate\u003C\u002Fstrong> service can provide a \u003Cstrong>Google Search Console HTML tag verification token\u003C\u002Fstrong> on \u003Ca href=\"https:\u002F\u002Fllmaffiliate.com\u002F\" rel=\"nofollow ugc\">llmaffiliate.com\u003C\u002Fa> for connected sites (see your dashboard or integration docs). If you choose to use it, open \u003Cstrong>Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> LLMAffiliate AI Traffic\u003C\u002Fstrong> in WordPress and paste the token into the prominent \u003Cstrong>Use LLMAffiliate’s Search Console verification\u003C\u002Fstrong> field, then save. The token is \u003Cstrong>stored only in your site’s database\u003C\u002Fstrong> and outputs the standard \u003Ccode>\u003Cmeta name=\"google-site-verification\" …>\u003C\u002Fcode> tag on your \u003Cstrong>public\u003C\u002Fstrong> frontend. You can clear the field at any time to remove the tag.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why this helps:\u003C\u002Fstrong> With your consent, LLMAffiliate can verify the site in Search Console tied to that token, which helps the service \u003Cstrong>monitor indexing coverage and page performance\u003C\u002Fstrong> for your integration and support you more effectively. This is \u003Cstrong>fully optional\u003C\u002Fstrong>; if you leave the field empty, nothing is added to your HTML.\u003C\u002Fp>\n\u003Cp>No extra HTTP request is made to Google from the plugin for this feature—the meta tag is for Google’s crawler when it visits your site.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the \u003Cstrong>LLM Affiliate\u003C\u002Fstrong> cloud service to detect visiting AI crawlers (ChatGPT, Perplexity, Claude, Gemini, Copilot, etc.) and return an LLM-optimized, monetizable version of the requested article. Without this external service the plugin still performs local LLM detection, search-engine parity, and renders the \u003Ccode>\u002Fai-terms\u003C\u002Fcode> page, but the enhanced-content feature is not available.\u003C\u002Fp>\n\u003Cp>This service is provided by \u003Cstrong>LLM Affiliate\u003C\u002Fstrong> (llmaffiliate.com).\u003C\u002Fp>\n\u003Cp>Service endpoints used:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Site Onboarding\u003C\u002Fstrong> — \u003Ccode>POST https:\u002F\u002Fapi.llmaffiliate.com\u002Fapi\u002Fv1\u002Fenhanced-content\u002Fonboarding\u002F\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purpose:\u003C\u002Fstrong> Registers your WordPress site with the LLM Affiliate backend so the site can receive enhanced content. Think of it as a one-time (idempotent) handshake.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When it is sent:\u003C\u002Fstrong> Only when you click \u003Cstrong>Generate Token\u003C\u002Fstrong> in the plugin admin screen (Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> LLMAffiliate AI Traffic). It is also re-sent if you regenerate\u002Frotate the token. It is \u003Cstrong>not\u003C\u002Fstrong> sent on every page load.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data sent (JSON body):\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>\u003Ccode>token\u003C\u002Fcode> – the authentication token generated by the plugin\u003C\u002Fli>\n\u003Cli>\u003Ccode>site_id\u003C\u002Fcode> – an internal site identifier (e.g., \u003Ccode>site_xxxxxxxx\u003C\u002Fcode>) generated by the plugin\u003C\u002Fli>\n\u003Cli>\u003Ccode>host\u003C\u002Fcode> – your site’s public URL (WordPress \u003Ccode>home_url()\u003C\u002Fcode>)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No post content, no user data, no visitor IP, and no visitor PII is transmitted by this endpoint.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Enhanced Content Render\u003C\u002Fstrong> — \u003Ccode>GET https:\u002F\u002Fapi.llmaffiliate.com\u002Fapi\u002Fv1\u002Fenhanced-content\u002Frender\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purpose:\u003C\u002Fstrong> Fetches the LLM-optimized HTML version of a single article URL to serve back to the detected AI crawler.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When it is sent:\u003C\u002Fstrong> Only when the plugin’s LLM detector classifies an incoming request as an AI\u002FLLM user-agent (ChatGPT, Perplexity, Claude, Gemini, Copilot, LLaMA, Grok, Cohere, Mistral, DeepSeek, Pi, and similar). It is \u003Cstrong>not\u003C\u002Fstrong> sent for human visitors, for search-engine crawlers (Googlebot, Bingbot), or for admin\u002FREST\u002Fstatic-asset requests.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data sent (query string + pass-through headers):\u003C\u002Fstrong>\n\u003Cul>\n\u003Cli>\u003Ccode>url\u003C\u002Fcode> – the public URL of the article being requested (query string + path)\u003C\u002Fli>\n\u003Cli>\u003Ccode>llm_profile\u003C\u002Fcode> – the detected LLM profile name (e.g., \u003Ccode>chatgpt\u003C\u002Fcode>, \u003Ccode>claude\u003C\u002Fcode>, \u003Ccode>gemini\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>\u003Ccode>User-Agent\u003C\u002Fcode> header – forwarded from the visiting LLM client\u003C\u002Fli>\n\u003Cli>\u003Ccode>Accept-Language\u003C\u002Fcode> header – forwarded from the visiting LLM client\u003C\u002Fli>\n\u003Cli>\u003Ccode>X-LLM-Profile\u003C\u002Fcode> header – the plugin’s detected profile\u003C\u002Fli>\n\u003Cli>\u003Ccode>X-LLM-Confidence\u003C\u002Fcode> header – a numeric confidence score (0–1) from the local detector\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No cookies, session IDs, logged-in-user identifiers, or page body content are sent.\u003C\u002Fstrong> Only the public URL and the minimum context needed to produce and attribute enhanced content is transmitted.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>User sitemaps (for the plugin sitemap endpoint only)\u003C\u002Fstrong> — \u003Ccode>GET https:\u002F\u002Fapi.llmaffiliate.com\u002Fapi\u002Fv1\u002Fenhanced-content\u002Fpublic\u002Fuser-sitemaps?host=\u003Chostname>\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Purpose:\u003C\u002Fstrong> Returns JSON listing LLM-optimized sitemap URLs for the given site hostname so this plugin can serve \u003Ccode>\u002Fsitemap.xml\u003C\u002Fcode> (or the configured sitemap path) as a simple URL index for search engines.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When it is sent:\u003C\u002Fstrong> Only on GET requests that match the plugin’s dedicated sitemap path (not on normal page views). The \u003Ccode>host\u003C\u002Fcode> query parameter is your site’s hostname from WordPress \u003Ccode>home_url()\u003C\u002Fcode> (no path, no user input from forms).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data sent:\u003C\u002Fstrong> \u003Ccode>host\u003C\u002Fcode> only, in the query string. Each item in the JSON \u003Ccode>sitemaps\u003C\u002Fcode> array includes \u003Ccode>site_url\u003C\u002Fcode> and \u003Ccode>last_modified\u003C\u002Fcode>. Non-200 responses result in an empty \u003Ccode>\u003Curlset>\u003C\u002Fcode> (no URLs listed).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>All requests are made over HTTPS. If the service is unavailable or returns a non-200 response, the plugin adds an \u003Ccode>X-LLMAFFTM-Interceptor: fallback\u003C\u002Fcode> header and allows WordPress to render the normal (origin) page — humans and LLMs always receive \u003Cem>something\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Use of the LLM Affiliate service is governed by the provider’s terms. Please review them before generating a token:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Terms of Service:\u003C\u002Fstrong> https:\u002F\u002Fllmaffiliate.com\u002Fterms\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy Policy:\u003C\u002Fstrong> https:\u002F\u002Fllmaffiliate.com\u002Fprivacy\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Service provider homepage:\u003C\u002Fstrong> https:\u002F\u002Fllmaffiliate.com\u002F\u003C\u002Fli>\n\u003C\u002Ful>\n","Detect LLM user agents, enforce Google parity, and serve enhanced content through a configurable content service.",0,240,"2026-06-19T15:41:00.000Z","7.0.2","6.0","7.4",[18,19,20,21,22],"ai","chatbot","content-delivery","crawler","llm","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fllmaffiliate-ai-traffic-monetizer.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-08-29T15:03:02.300Z",[36,60,78,96,114],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":14,"requires_at_least":49,"requires_php":16,"tags":50,"homepage":23,"download_link":56,"security_score":57,"vuln_count":58,"unpatched_count":11,"last_vuln_date":59,"fetched_at":27},"better-robots-txt","Better Robots.txt – AI-Ready Crawl Control & Bot Governance","3.1.2","Pagup","https:\u002F\u002Fprofiles.wordpress.org\u002Fpagup\u002F","\u003Cp>Better Robots.txt replaces the default WordPress robots.txt workflow with a smarter, structured version you can configure and preview before publishing.\u003C\u002Fp>\n\u003Cp>Instead of a blank textarea, you get a guided wizard with presets, plain-language explanations, and a final Review & Save step so you can inspect the generated robots.txt before it goes live.\u003C\u002Fp>\n\u003Cp>Built for beginners and advanced users alike, Better Robots.txt helps you control how search engines, AI crawlers, SEO tools, archive bots, bad bots, social preview bots, and other automated agents interact with your site.\u003C\u002Fp>\n\u003Cp>Trusted by thousands of WordPress sites, Better Robots.txt is designed for the AI era without resorting to hype, vague promises, or hidden rules.\u003C\u002Fp>\n\u003Cp>Better Robots.txt is available in Free, Pro, and Premium editions. The free plugin covers the guided workflow and essential crawl control features, while Pro and Premium unlock additional governance, protection, and AI-ready modules. Some screenshots on the plugin page show features from all three editions.\u003C\u002Fp>\n\u003Ch3>A quick overview\u003C\u002Fh3>\n\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Better robots.txt Video — AI-Ready Crawl Control for WordPress\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F1169756981?dnt=1&app_id=122963\" width=\"750\" height=\"372\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Why Better Robots.txt is different\u003C\u002Fh3>\n\u003Cp>Most robots.txt plugins fall into one of three categories:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Simple text editor\u003C\u002Fli>\n\u003Cli>Virtual robots.txt manager\u003C\u002Fli>\n\u003Cli>Single-purpose AI or policy add-on\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Better Robots.txt goes further.\u003C\u002Fp>\n\u003Cp>It gives you a complete, guided crawl control workflow so you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Choose a preset that matches your goals\u003C\u002Fli>\n\u003Cli>Control major crawler categories without writing everything by hand\u003C\u002Fli>\n\u003Cli>Keep core WordPress protection rules visible and editable\u003C\u002Fli>\n\u003Cli>Clean up low-value crawl paths that waste crawl budget\u003C\u002Fli>\n\u003Cli>Generate a cleaner robots.txt output\u003C\u002Fli>\n\u003Cli>Preview the final result before saving\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What you can control\u003C\u002Fh3>\n\u003Cp>Better Robots.txt helps you manage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Search engine visibility\u003C\u002Fli>\n\u003Cli>AI and LLM crawler behavior\u003C\u002Fli>\n\u003Cli>AI usage signals such as search, ai-input, and ai-train preferences\u003C\u002Fli>\n\u003Cli>SEO tool crawlers\u003C\u002Fli>\n\u003Cli>Bad bots and abusive crawlers\u003C\u002Fli>\n\u003Cli>Archive and Wayback access\u003C\u002Fli>\n\u003Cli>Feed crawlers and crawl traps\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawlers\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>llms.txt generation\u003C\u002Fli>\n\u003Cli>Advanced directives such as crawl-delay and custom rules\u003C\u002Fli>\n\u003Cli>Final review before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Editions\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is available in three editions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Free – Includes the guided setup, the Essential preset, core crawl control features, and the final Review & Save workflow.\u003C\u002Fli>\n\u003Cli>Pro – Adds more advanced governance and protection modules, including additional AI, crawler, and cleanup controls.\u003C\u002Fli>\n\u003Cli>Premium – Unlocks the most restrictive and advanced protection options, including the Fortress preset and additional high-control modules.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Some options shown in the interface are marked Free, Pro, or Premium so users can immediately understand which modules belong to each edition.\u003C\u002Fp>\n\u003Ch3>AI crawler controls by edition\u003C\u002Fh3>\n\u003Cp>The Free edition lets site owners choose a basic global policy for AI search and discovery crawlers: allow or block. AI training crawlers remain separated from AI search crawlers, so a site can block training use while still allowing AI-powered search and answer discovery.\u003C\u002Fp>\n\u003Cp>The Pro and Premium editions add advanced controls, including per-bot AI crawler rules, custom user agents, AI usage signals, llms.txt, and additional machine-readable governance files.\u003C\u002Fp>\n\u003Cp>Better Robots.txt separates AI-related agents into three practical families:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI training crawlers, such as GPTBot, Google-Extended, and ClaudeBot.\u003C\u002Fli>\n\u003Cli>AI search and discovery crawlers, such as OAI-SearchBot, PerplexityBot, and Claude-SearchBot.\u003C\u002Fli>\n\u003Cli>User-action fetchers, such as ChatGPT-User, Perplexity-User, and Claude-User.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>User-action fetchers are triggered by user requests. Depending on the provider, robots.txt may not apply to those fetches in the same way as it applies to automated crawlers. For stronger enforcement, combine robots.txt with server logs, WAF rules, provider verification, or IP-based controls where available.\u003C\u002Fp>\n\u003Ch3>Presets\u003C\u002Fh3>\n\u003Cp>Setup starts with four modes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Essential – A clean, practical configuration for most websites that want a better robots.txt without complexity.\u003C\u002Fli>\n\u003Cli>AI-First – For publishers and content sites that want AI-ready governance without shutting down discovery.\u003C\u002Fli>\n\u003Cli>Fortress – For websites that want stronger protection against scraping, archive capture, and unnecessary crawl activity.\u003C\u002Fli>\n\u003Cli>Custom – For users who prefer to configure each module manually.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For many sites, one preset plus a quick review is enough.\u003C\u002Fp>\n\u003Ch3>Built for beginners and experts\u003C\u002Fh3>\n\u003Cp>Beginners get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A guided setup instead of a raw robots.txt box\u003C\u002Fli>\n\u003Cli>Preset-based configuration\u003C\u002Fli>\n\u003Cli>Plain-language explanations for important choices\u003C\u002Fli>\n\u003Cli>A safer workflow with a final preview step\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Advanced users get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Editable core WordPress protection rules\u003C\u002Fli>\n\u003Cli>Fine-grained crawler controls by category\u003C\u002Fli>\n\u003Cli>WooCommerce-oriented cleanup options\u003C\u002Fli>\n\u003Cli>Consolidated output options\u003C\u002Fli>\n\u003Cli>Advanced directives and custom rules\u003C\u002Fli>\n\u003Cli>A final output they can inspect before publishing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AI-ready, without hype\u003C\u002Fh3>\n\u003Cp>Better Robots.txt includes features for modern AI-related crawl governance, including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI crawler handling\u003C\u002Fli>\n\u003Cli>Optional llms.txt support\u003C\u002Fli>\n\u003Cli>AI usage signals for compliant systems\u003C\u002Fli>\n\u003Cli>Optional machine-readable governance signals for advanced use cases\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These features help you express how you want automated systems to use your content.\u003C\u002Fp>\n\u003Cp>However, Better Robots.txt does not claim to control AI by force. Like robots.txt itself, these signals are most useful with compliant systems and good-faith crawlers.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A robots.txt governance plugin for WordPress\u003C\u002Fli>\n\u003Cli>A guided configuration workflow instead of a raw text editor\u003C\u002Fli>\n\u003Cli>A crawl control layer to reduce wasteful crawling\u003C\u002Fli>\n\u003Cli>A practical bridge between SEO, crawl hygiene, and AI-era policy signaling\u003C\u002Fli>\n\u003Cli>A way to keep your crawl policy clearer for humans and machines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Technical reference for advanced users: Better Robots.txt also maintains a public \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FGautierDorval\u002Fbetter-robots-txt\" rel=\"nofollow noopener noreferrer ugc\">GitHub repository\u003C\u002Fa> with product definition, governance notes, and machine-readable artefacts.\u003C\u002Fp>\n\u003Ch3>What Better Robots.txt is not\u003C\u002Fh3>\n\u003Cp>Better Robots.txt is not:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A firewall or Web Application Firewall (WAF)\u003C\u002Fli>\n\u003Cli>An anti-scraping enforcement engine\u003C\u002Fli>\n\u003Cli>A legal compliance engine\u003C\u002Fli>\n\u003Cli>A guarantee that every bot will obey your rules\u003C\u002Fli>\n\u003Cli>A replacement for server-level security or access control\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It helps you publish a clearer crawl policy.\u003C\u002Fp>\n\u003Cp>It does not replace infrastructure-level protection.\u003C\u002Fp>\n\u003Ch3>Typical use cases\u003C\u002Fh3>\n\u003Cp>Use Better Robots.txt if you want to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Clean up a weak or noisy default robots.txt\u003C\u002Fli>\n\u003Cli>Reduce crawl waste on WordPress or WooCommerce\u003C\u002Fli>\n\u003Cli>Keep major search engines allowed while restricting other bots\u003C\u002Fli>\n\u003Cli>Control whether archive bots can snapshot your site\u003C\u002Fli>\n\u003Cli>Publish AI usage preferences more clearly\u003C\u002Fli>\n\u003Cli>Keep social preview bots allowed while limiting scrapers\u003C\u002Fli>\n\u003Cli>Review the final file before making it live\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Key Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Guided step-by-step wizard\u003C\u002Fli>\n\u003Cli>Preset-based setup: Essential, AI-First, Fortress, Custom\u003C\u002Fli>\n\u003Cli>Search engine visibility controls\u003C\u002Fli>\n\u003Cli>AI and LLM crawler governance\u003C\u002Fli>\n\u003Cli>AI usage signals support\u003C\u002Fli>\n\u003Cli>SEO tool crawler controls\u003C\u002Fli>\n\u003Cli>Bad bot and abusive crawler options\u003C\u002Fli>\n\u003Cli>Archive and Wayback access controls\u003C\u002Fli>\n\u003Cli>Spam, feed, and crawl trap cleanup\u003C\u002Fli>\n\u003Cli>WooCommerce crawl cleanup options\u003C\u002Fli>\n\u003Cli>CSS, JavaScript, and image crawling rules\u003C\u002Fli>\n\u003Cli>Social media preview crawler controls\u003C\u002Fli>\n\u003Cli>ads.txt and app-ads.txt allowance\u003C\u002Fli>\n\u003Cli>Optional llms.txt generation\u003C\u002Fli>\n\u003Cli>Consolidated output option\u003C\u002Fli>\n\u003Cli>Core WordPress protection rules remain visible and editable\u003C\u002Fli>\n\u003Cli>Final Review & Save preview screen\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>About the publisher\u003C\u002Fh4>\n\u003Cp>Better Robots.txt is developed and maintained by \u003Ca href=\"https:\u002F\u002Fpagup.com\u002F\" rel=\"nofollow ugc\">Pagup\u003C\u002Fa>, a digital readability firm based in Quebec, Canada. Pagup helps organizations become correctly understood by search engines, generative AI systems, and autonomous agents.\u003C\u002Fp>\n\u003Cp>The robots.txt file is the first surface that AI crawlers read when they discover a site. A well-structured robots.txt that references governance files such as llms.txt, ai-manifest.json, and interpretation policies helps AI systems understand your site faster and more accurately.\u003C\u002Fp>\n\u003Cp>Better Robots.txt is one component of a broader digital readability practice that includes \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fservices\u002Fsemantic-content-architecture\u002F\" rel=\"nofollow ugc\">semantic content architecture\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fservices\u002Fai-governance-and-machine-readability\u002F\" rel=\"nofollow ugc\">AI governance and machine readability\u003C\u002Fa>, and \u003Ca href=\"https:\u002F\u002Fpagup.com\u002Fen\u002Fglossary\u002Finterpretive-seo\u002F\" rel=\"nofollow ugc\">interpretive SEO\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Part of the Pagup ecosystem\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fpagup.com\u002F\" rel=\"nofollow ugc\">pagup.com\u003C\u002Fa> — Digital readability firm. Diagnostic, semantic architecture, AI governance.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgautierdorval.com\u002F\" rel=\"nofollow ugc\">gautierdorval.com\u003C\u002Fa> — Doctrine, canonical definitions, interpretive governance research.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Finterpretive-governance.org\u002F\" rel=\"nofollow ugc\">interpretive-governance.org\u003C\u002Fa> — Formal versioned standard for interpretive governance.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbetter-robots.com\u002F\" rel=\"nofollow ugc\">better-robots.com\u003C\u002Fa> — Documentation and resources for Better Robots.txt.\u003C\u002Fli>\n\u003C\u002Ful>\n","Replace the default WordPress robots.txt workflow with a smarter, structured version you can preview before publishing, with Free, Pro, and Premium ed …",5000,321566,90,102,"2026-07-04T14:07:00.000Z","5.0",[51,52,53,54,55],"ai-crawlers","bot-blocker","llms-txt","robots-txt","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbetter-robots-txt.3.1.2.zip",99,2,"2023-02-14 00:00:00",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":25,"downloaded":68,"rating":25,"num_ratings":31,"last_updated":69,"tested_up_to":70,"requires_at_least":15,"requires_php":71,"tags":72,"homepage":76,"download_link":77,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"coding-bunny-llms-generator","CodingBunny LLMs.txt Generator","1.2.2","CodingBunny","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodingbunny\u002F","\u003Cp>CodingBunny LLMs.txt Generator creates an advanced llms.txt file to help AI systems discover and understand your content with rich semantic metadata.\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>AI Metadata\u003C\u002Fstrong>: Schema.org types, canonical URLs, related content, differentiated licenses\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Filtering\u003C\u002Fstrong>: Decorative image detection, featured-only option, configurable limits\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Crawler Control\u003C\u002Fstrong>: Allow\u002FDisallow directives, AI bot allowlist, SEO noindex integration\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rich YAML\u003C\u002Fstrong>: Title, category, type, date, summary, author, language, tags, priority\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automation\u003C\u002Fstrong>: Daily\u002Fweekly scheduling, immediate on-publish, generation history\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Developer-Friendly\u003C\u002Fstrong>: 20+ hooks\u002Ffilters, WooCommerce support, multilingual ready\u003C\u002Fli>\n\u003Cli>Schema.org auto-detection (Article, Product, ContactPage, FAQPage, etc.)\u003C\u002Fli>\n\u003Cli>Canonical URLs (Yoast\u002FRankMath compatible)\u003C\u002Fli>\n\u003Cli>Related URLs (parent\u002Fchild pages, related posts\u002Fproducts)\u003C\u002Fli>\n\u003Cli>Differentiated licenses (content vs. media)\u003C\u002Fli>\n\u003Cli>HTML entity fixes and improved text normalization\u003C\u002Fli>\n\u003C\u002Ful>\n","Advanced llms.txt generator with AI metadata, Schema.org types, canonical URLs, and differentiated licenses for optimal LLM indexing.",1328,"2026-02-26T11:40:00.000Z","6.9.5","8.0",[18,73,74,55,75],"crawlers","llms","sitemap","https:\u002F\u002Fcoding-bunny.com\u002Fllms-generator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcoding-bunny-llms-generator.1.2.2.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":11,"num_ratings":11,"last_updated":88,"tested_up_to":14,"requires_at_least":89,"requires_php":90,"tags":91,"homepage":94,"download_link":95,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"parseless","ParseLess","0.6.0","phalkmin","https:\u002F\u002Fprofiles.wordpress.org\u002Fphalkmin\u002F","\u003Cp>ParseLess serves your WordPress content as clean Markdown to AI crawlers (via User-Agent detection) and on manual \u003Ccode>?format=md\u003C\u002Fcode> requests. Same URL, same content, none of the theme chrome, navigation, widgets, or page-builder scaffolding that AI bots and CLI tools don’t need.\u003C\u002Fp>\n\u003Cp>It also exposes \u003Ccode>\u002Fllms.txt\u003C\u002Fcode> for the emerging AI-indexing standard, so models know where to find your content.\u003C\u002Fp>\n\u003Ch4>Who is this for?\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>1. Developers using Claude Code, Cursor, Aider, or any CLI that feeds your own site content into an LLM.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you’ve ever piped a blog post into Claude or ChatGPT for analysis, rewriting, or summarization, you’ve watched it burn through tokens parsing nav menus, footer markup, and CSS classes that have nothing to do with your content. A typical WordPress page measured live: \u003Cstrong>~19,800 tokens of HTML for ~975 tokens of actual content\u003C\u002Fstrong> — a 20x reduction just by stripping the theme. Heavy page-builder sites (Elementor, Divi) routinely hit 100x or more.\u003C\u002Fp>\n\u003Cp>That’s the difference between fitting a handful of pages in a context window and fitting dozens.\u003C\u002Fp>\n\u003Cp>Just append \u003Ccode>?format=md\u003C\u002Fcode> to any post URL and pipe it straight into your tool of choice:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>curl https:\u002F\u002Fyoursite.com\u002Fmy-post\u002F?format=md | claude \"summarize this\"\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>2. Site owners getting “high resource usage” warnings from their host because AI bots are hammering the site.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and a dozen others crawl WordPress sites constantly. Each request renders your full theme, runs widget queries, loads page-builder assets, and ships hundreds of KB of HTML per page — most of which the bot discards before extracting the actual text.\u003C\u002Fp>\n\u003Cp>ParseLess intercepts these crawls and serves a tiny Markdown payload instead. You keep the AEO\u002FSEO benefit of being indexed by AI search, without paying the server cost of rendering your full theme for every bot hit.\u003C\u002Fp>\n\u003Cp>Typical impact on AI bot traffic (measured on real WordPress pages):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>95%+ less bandwidth\u003C\u002Fstrong> per crawled page (typically 15–30x smaller; e.g. a 79 KB page \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> 4 KB. Heavy page-builder sites see 100x+)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>~60–80% fewer database queries\u003C\u002Fstrong> per request\u003C\u002Fli>\n\u003Cli>\u003Cstrong>~60% lower peak PHP memory\u003C\u002Fstrong> per request\u003C\u002Fli>\n\u003Cli>\u003Cstrong>~50–80% faster Time To First Byte\u003C\u002Fstrong> (measured 54% on a content-heavy page, 67% on a short one)\u003C\u002Fli>\n\u003Cli>On a site with 500 posts crawled monthly by major AI bots, that’s roughly \u003Cstrong>gigabytes \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> tens of megabytes\u003C\u002Fstrong> of monthly bandwidth and a fraction of the cumulative PHP execution time\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Numbers vary by theme and content. Heavier setups (Elementor, Divi, Avada) see the biggest savings; lightweight themes see less dramatic but still meaningful gains. The conversion is cached as a transient, so repeated bot hits cost almost nothing.\u003C\u002Fp>\n\u003Ch4>How it works\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>AI crawlers are detected by User-Agent and served Markdown automatically — no configuration required.\u003C\u002Fli>\n\u003Cli>Humans, search engines, and unknown bots receive your normal HTML output. ParseLess never affects what real visitors see.\u003C\u002Fli>\n\u003Cli>The \u003Ccode>?format=md\u003C\u002Fcode> query parameter works on any post URL for manual preview or CLI piping.\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fllms.txt\u003C\u002Fcode> is published at your site root with a list of available content for AI indexers.\u003C\u002Fli>\n\u003Cli>Conversion happens once per post and is cached. Subsequent requests serve a single transient read.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatic Markdown for known AI bots (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, CCBot, Google-Extended, Applebot-Extended, Bytespider, Meta-ExternalAgent, cohere-ai, and more)\u003C\u002Fli>\n\u003Cli>Manual preview and CLI access via \u003Ccode>?format=md\u003C\u002Fcode> on any post URL\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fllms.txt\u003C\u002Fcode> endpoint for AI-indexing standards\u003C\u002Fli>\n\u003Cli>Respects noindex flags from Yoast SEO, Rank Math, and Genesis\u003C\u002Fli>\n\u003Cli>Skips private, draft, password-protected, and trashed posts\u003C\u002Fli>\n\u003Cli>Works with all public post types (configurable)\u003C\u002Fli>\n\u003Cli>Optional YAML frontmatter (title, URL, author, date, categories, tags, excerpt)\u003C\u002Fli>\n\u003Cli>Transient-based caching with configurable TTL\u003C\u002Fli>\n\u003Cli>Settings page at \u003Cstrong>Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> ParseLess\u003C\u002Fstrong> for detection mode, bot list, cache TTL, post types, and llms.txt control\u003C\u002Fli>\n\u003Cli>Per-post meta box with Markdown preview and copy-to-clipboard\u003C\u002Fli>\n\u003Cli>Extensible via filters: \u003Ccode>md4ai_bot_list\u003C\u002Fcode>, \u003Ccode>md4ai_supported_post_types\u003C\u002Fcode>, \u003Ccode>md4ai_markdown_output\u003C\u002Fcode>, \u003Ccode>md4ai_cache_ttl\u003C\u002Fcode>, \u003Ccode>md4ai_should_serve_markdown\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy and data collection\u003C\u002Fh3>\n\u003Cp>When logging is enabled (off by default), ParseLess records the following for\u003Cbr \u002F>\neach Markdown request:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Post ID, URL, and request timestamp\u003C\u002Fli>\n\u003Cli>The full User-Agent header\u003C\u002Fli>\n\u003Cli>A salted SHA-256 hash of the requester’s IP address (the raw IP is never stored)\u003C\u002Fli>\n\u003Cli>Matched bot identifier, bytes served, and whether the response came from cache\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>IP hashes cannot be reversed from an email address, so the WordPress privacy\u003Cbr \u002F>\nexporter\u002Feraser tools will report no personal data on demand.\u003C\u002Fp>\n\u003Cp>Logs are pruned daily according to the configured retention window\u003Cbr \u002F>\n(7\u002F30\u002F90\u002F365 days, default 30). Site owners can disable logging or click\u003Cbr \u002F>\n“Delete all logged requests” at any time from Tools \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> ParseLess.\u003C\u002Fp>\n","Serve your posts as Markdown to AI crawlers and CLI tools — typically 95%+ less bandwidth, ~60–80% fewer DB queries, no theme bloat.",50,417,"2026-06-16T17:58:00.000Z","6.8","8.2",[18,92,73,74,93],"bots","markdown","https:\u002F\u002Fgithub.com\u002Fphalkmin\u002Fparseless","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fparseless.0.6.0.zip",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":32,"downloaded":104,"rating":11,"num_ratings":11,"last_updated":105,"tested_up_to":106,"requires_at_least":107,"requires_php":16,"tags":108,"homepage":111,"download_link":112,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":113},"chatolia","Chatolia","1.1.3","senols","https:\u002F\u002Fprofiles.wordpress.org\u002Fsenols\u002F","\u003Cp>Chatolia lets you embed and manage cloud-hosted AI assistants on your site. Connect with a token, auto-create an agent, preview it in the admin, and embed via shortcode. The UI is hosted by Chatolia so you don’t have to rebuild the chat experience in WordPress.\u003C\u002Fp>\n\u003Cp>Features\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Connect with an access token\u003C\u002Fli>\n\u003Cli>One-click agent creation and storage\u003C\u002Fli>\n\u003Cli>Live admin preview\u003C\u002Fli>\n\u003Cli>Shortcode embeds the widget\u003C\u002Fli>\n\u003Cli>Basic appearance controls (theme, position)\u003C\u002Fli>\n\u003Cli>Translation-ready (i18n)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Homepage: https:\u002F\u002Fwww.chatolia.com\u002F\u003Cbr \u002F>\nDocumentation: https:\u002F\u002Fdocs.chatolia.com\u002F\u003C\u002Fp>\n\u003Cp>Privacy\u003C\u002Fp>\n\u003Cp>By connecting the plugin to your Chatolia account, you agree to Chatolia’s Privacy Policy and Terms of Service. When the shortcode is present on a page, the embedded client loads from chatolia.com and sends conversation data directly to Chatolia; the plugin itself only stores your token and agent ID.\u003C\u002Fp>\n","Embed and manage your Chatolia AI chatbots on WordPress.",464,"2025-12-07T11:49:00.000Z","6.9.4","5.8",[18,109,110,19,22],"assistant","chat","https:\u002F\u002Fchatolia.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fchatolia.1.1.3.zip","2026-04-16T10:56:18.058Z",{"slug":115,"name":116,"version":117,"author":118,"author_profile":119,"description":120,"short_description":121,"active_installs":32,"downloaded":122,"rating":11,"num_ratings":11,"last_updated":123,"tested_up_to":70,"requires_at_least":15,"requires_php":16,"tags":124,"homepage":127,"download_link":128,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"kennedy-site-scout","Kennedy Site Scout","3.0.1","Anthony Acosta","https:\u002F\u002Fprofiles.wordpress.org\u002Fanthon1\u002F","\u003Cp>Kennedy Site Scout prepares your WordPress site to be read, indexed, and cited by AI systems — including ChatGPT, Claude, Perplexity, Gemini, and 20+ other crawlers.\u003C\u002Fp>\n\u003Ch4>What it does\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Generates \u003Ccode>\u002Fllms.txt\u003C\u002Fcode>, \u003Ccode>\u002Fllms-full.txt\u003C\u002Fcode>, and \u003Ccode>\u002Fllms-sitemap.xml\u003C\u002Fcode> dynamically from your published content — no physical files written to disk\u003C\u002Fli>\n\u003Cli>Adds a configurable \u003Cstrong>Site Authority\u003C\u002Fstrong> section to your LLM files with publisher name, credentials, location, areas of expertise, and biography — giving AI systems the E-E-A-T context they need to cite your content accurately\u003C\u002Fli>\n\u003Cli>Includes rich \u003Cstrong>E-E-A-T metadata\u003C\u002Fstrong> per content item: author name, credentials (via Yoast SEO job title or user meta), and bio pulled from WordPress, Yoast SEO, and Rank Math\u003C\u002Fli>\n\u003Cli>Configurable \u003Cstrong>Custom Instructions\u003C\u002Fstrong> textarea — add guidance for AI systems directly into your llms.txt header\u003C\u002Fli>\n\u003Cli>Smart \u003Cstrong>\u003C!--more-->-aware content truncation\u003C\u002Fstrong> so excerpt boundaries are respected\u003C\u002Fli>\n\u003Cli>Logs AI crawler visits across every page of your site, not just the LLM files\u003C\u002Fli>\n\u003Cli>Detects 25+ known AI bots including GPTBot, ClaudeBot, Anthropic-AI, PerplexityBot, Meta ExternalAgent, Cohere AI, ByteSpider, AmazonBot, and more\u003C\u002Fli>\n\u003Cli>Respects Yoast SEO and Rank Math noindex settings — excluded content stays excluded\u003C\u002Fli>\n\u003Cli>Dashboard widget with bot visit stats, summary pills, settings, and one-click regeneration\u003C\u002Fli>\n\u003Cli>Auto-regenerates on publish and on a configurable cron schedule\u003C\u002Fli>\n\u003Cli>One-time admin notice with suggested robots.txt AI-bot directives (dismissible)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Free tier\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Up to 5 pages indexed\u003C\u002Fli>\n\u003Cli>200 log entries stored\u003C\u002Fli>\n\u003Cli>80-word content excerpts in llms-full.txt\u003C\u002Fli>\n\u003Cli>Site Authority section\u003C\u002Fli>\n\u003Cli>Custom llms.txt instructions\u003C\u002Fli>\n\u003Cli>All core features\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Pro tier\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Unlimited pages indexed\u003C\u002Fli>\n\u003Cli>5,000 log entries\u003C\u002Fli>\n\u003Cli>CSV export of crawler logs\u003C\u002Fli>\n\u003Cli>300-word content excerpts (respects \u003C!–more–>)\u003C\u002Fli>\n\u003Cli>Image tags in llms-sitemap.xml\u003C\u002Fli>\n\u003Cli>Tag data included in LLM files\u003C\u002Fli>\n\u003Cli>Rich E-E-A-T author metadata: bio + credentials per item\u003C\u002Fli>\n\u003Cli>Word count and reading time per item\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Featured Content\u003C\u002Fstrong> — pin posts with \u003Ccode>_kss_featured\u003C\u002Fcode> meta to the top of LLM files and sitemap\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Top Crawled Pages\u003C\u002Fstrong> — see which of your pages AI bots visit most\u003C\u002Fli>\n\u003Cli>Shortcode \u003Ccode>featured=\"only\"\u003C\u002Fcode> attribute to display only featured items\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why llms.txt?\u003C\u002Fh4>\n\u003Cp>The emerging llms.txt standard gives AI systems a clean, structured entry point to your site’s content — similar to what robots.txt did for search engines. This plugin automates generating and maintaining that file, with the E-E-A-T signals that help AI systems understand and trust your content.\u003C\u002Fp>\n\u003Ch4>GEO \u002F AIO Optimization\u003C\u002Fh4>\n\u003Cp>Generative Engine Optimization (GEO) and AI Overview (AIO) visibility starts with structured, trustworthy content signals. Kennedy Site Scout v3 adds a Site Authority section and per-item E-E-A-T metadata so AI models can accurately attribute and cite your expertise.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to an external license verification service operated by Kennedy Media Group. This service is used solely to validate Pro license keys entered by users who have purchased a Pro upgrade.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What data is sent and when:\u003C\u002Fstrong>\u003Cbr \u002F>\nThe license verification endpoint is only contacted when a site administrator manually enters a license key in the plugin’s dashboard widget and clicks “Activate”. At that point, the plugin sends:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The license key entered by the administrator\u003C\u002Fli>\n\u003Cli>The home URL of the WordPress installation (e.g. https:\u002F\u002Fexample.com)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No personal data, user data, post content, or any other site information is transmitted. The free version of the plugin never contacts this service.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Service details:\u003C\u002Fstrong>\u003Cbr \u002F>\n* Provider: Kennedy Media Group\u003Cbr \u002F>\n* Endpoint: https:\u002F\u002Fkennedymedia.com\u002Fwp-json\u002Fkssr-license\u002Fv1\u002Fverify\u003Cbr \u002F>\n* Terms of Service: https:\u002F\u002Fkennedymedia.com\u002Fterms\u002F\u003Cbr \u002F>\n* Privacy Policy: https:\u002F\u002Fkennedymedia.com\u002Fprivacy-2\u002F\u003C\u002Fp>\n\u003Cp>This plugin does not connect to any other external services. All LLM file generation and AI crawler logging happens entirely on your own server.\u003C\u002Fp>\n","Prepare your WordPress site for AI. Auto-generates E-E-A-T-rich llms.txt, llms-full.txt, and llms-sitemap.xml. Logs all AI crawler visits site-wide.",330,"2026-05-18T15:37:00.000Z",[125,126,53,55,75],"ai-crawler","gptbot","https:\u002F\u002Fkennedymedia.com\u002Fai-site-scout-2\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkennedy-site-scout.3.0.1.zip",{"error":130,"url":131,"statusCode":132,"statusMessage":133,"message":133},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fllmaffiliate-ai-traffic-monetizer\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":31,"versions":135},[136],{"version":137,"download_url":138,"svn_tag_url":139,"released_at":26,"has_diff":140,"diff_files_changed":141,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":142,"is_current":140},"1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fllmaffiliate-ai-traffic-monetizer.1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fllmaffiliate-ai-traffic-monetizer\u002Ftags\u002F1.0.1\u002F",false,[],[]]