Sean Mullins

LLMs.txt Curator helps site owners generate and curate a high-quality <code>llms.txt</code> file for AI assistants and retrieval systems, ensuring only relevant, well-described content is exposed to large language models.
It generates and maintains <code>llms.txt</code> and <code>llms-full.txt</code> — the emerging standard for telling AI systems (ChatGPT, Claude, Perplexity, Gemini, and others) which pages on your site matter most and what they contain.
Unlike auto-generators that dump every URL into a flat file, LLMs.txt Curator takes a curation-first approach. You choose the pages, organise them into sections, fill descriptions, override titles for AI, validate quality, and see exactly which AI bots are reading your file — all from a single interface.
<h4>What makes this different</h4>
Most llms.txt plugins treat the file as a static output. LLMs.txt Curator treats it as a living asset:
<ul>
<li>Quality Score — every generated file shows your coverage percentage, which pages have descriptions, and which still need attention.</li>
<li>Description Suggestions — one click fills all missing descriptions from a five-step fallback chain (SEO meta → excerpt → Open Graph → page content). Never overwrites what you’ve set manually.</li>
<li>Change Detection — a banner appears in your admin when curated pages have been updated since the last generation, with a Regenerate Now button. Your llms.txt stays current without manual checking.</li>
<li>Per-Page Title Override — set a different title for each page specifically for AI consumption, without touching your on-site SEO.</li>
<li>Safety Mode — blocks generation if validation errors exist, preventing a broken file from going live. Includes an on-demand validator with plain-English results.</li>
<li>AI Crawler Analytics — see which bots visited in the last 7 days, with a visual bar chart. OpenAI, Anthropic, Perplexity, Google — know who is actually reading your file.</li>
</ul>
<h4>Core features</h4>
<ul>
<li>Drag-and-drop curation — reorder sections and pages visually; each section becomes an <code>##</code> heading per the spec</li>
<li>llms-full.txt generation — the companion file with full Markdown content for each curated page</li>
<li>Five SEO plugin integrations — Rank Math, Yoast SEO, All in One SEO, SEOPress, The SEO Framework</li>
<li>Schema-aware descriptions — uses structured data before falling back through the description chain</li>
<li>Scheduled regeneration — choose Instant (on publish), Daily, Weekly, or Manual</li>
<li>WooCommerce support — SKU, price, stock, categories, dimensions; respects product visibility</li>
<li>WordPress Multisite — network-activate across all sites; each site manages its own independent llms.txt; Network Admin overview with per-site and bulk regenerate</li>
<li>Pre-built templates — Business, E-commerce, SaaS, Blog, Local Business</li>
<li>Live preview — see your exact llms.txt output before saving</li>
<li>Import / export — move your configuration between sites as JSON</li>
<li>WP-CLI — <code>wp llms-txt regenerate</code>, <code>wp llms-txt status</code>, <code>wp llms-txt crawler-log</code></li>
<li>REST API — <code>POST /wp-json/llms-txt/v1/regenerate</code>, <code>GET /wp-json/llms-txt/v1/status</code></li>
<li>Atomic file writes — temp file → rename; no half-written files served to bots</li>
<li>ETag/304 caching — proper HTTP headers for CDN revalidation</li>
<li>Subdirectory / Bedrock support — correctly finds the site root on non-standard installs</li>
<li>Robots.txt reference — automatically adds a spec-compliant comment</li>
</ul>
<h4>Description Suggestions in detail</h4>
When pages lack descriptions, AI systems get less context. The suggestion engine fills the gap automatically:
<ol>
<li>Schema markup (Rank Math, custom <code>_schema_json</code>)</li>
<li>SEO plugin meta description</li>
<li>WordPress excerpt</li>
<li>Open Graph description (<code>_og_description</code> / <code>og_description</code>)</li>
<li>First 160 characters of post content</li>
</ol>
Already-set descriptions are never touched. Pages that can’t be filled automatically are listed for manual review.
<h4>Quality Score</h4>
Every generated <code>llms.txt</code> ends with a coverage report:
<pre><code>Quality Score: 94%
Pages included: 48
Pages with descriptions: 45
Pages missing descriptions: 3
</code></pre>
This is visible to the AI systems reading your file, and to you in the Preview tab.
<h4>AI Crawler Analytics</h4>
Track 12 known bots: GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, Bytespider, CCBot, Cohere, DeepSeek, Amazonbot.
The 7-day analytics card shows a visual bar chart of recent activity. All-time totals are kept separately. IP addresses are anonymised before storage — last octet zeroed for IPv4, last 80 bits for IPv6. No data leaves your server.
<h4>Safety Mode</h4>
Before generation, the validator checks:
<ul>
<li>Pages missing or unpublished</li>
<li>Duplicate URLs across sections</li>
<li>Noindex conflicts</li>
<li>Canonical mismatches</li>
<li>Password-protected pages</li>
<li>Thin content (< 100 words, no meta, no excerpt)</li>
<li>File size > 50 KB</li>
<li>Too many pages (> 80)</li>
</ul>
When Safety Mode is on, errors block generation and the results are shown immediately. Warnings are surfaced but don’t block. Everything is explained in plain English.
<h4>Scheduled regeneration</h4>
<ul>
<li>Instant — regenerates ~30 seconds after any page is published or trashed (default)</li>
<li>Daily — once per day, via WP-Cron recurring event</li>
<li>Weekly — once per week</li>
<li>Manual — only when you click Save & Generate</li>
</ul>
<h4>How to get started</h4>
<ol>
<li>Install and activate. The plugin auto-scans your content and creates initial sections.</li>
<li>Curate: drag, drop, add, remove. Aim for 20-60 pages that best represent your site.</li>
<li>Click Generate Missing Descriptions to fill gaps automatically.</li>
<li>Fix any warnings shown in the Safety Mode card.</li>
<li>Set the update mode that suits your workflow.</li>
<li>Save & Generate. Your files are live at <code>/llms.txt</code> and <code>/llms-full.txt</code>.</li>
<li>Enable the AI Crawler Log to see which bots start visiting.</li>
</ol>
<h4>WooCommerce integration</h4>
When WooCommerce is active, the plugin automatically includes SKU, price, and stock status in <code>llms.txt</code> descriptions, and full product details in <code>llms-full.txt</code>. Products with “hidden” visibility are excluded, and you can optionally exclude out-of-stock products.
<h4>Developer hooks</h4>
<ul>
<li><code>llmscu_capability</code> filter — override the required capability (default: <code>manage_options</code>)</li>
<li><code>llmscu_post_limit</code> filter — scanner post limit per type (default: 500)</li>
<li><code>llmscu_full_word_limit</code> filter — per-page word cap in <code>llms-full.txt</code> (default: unlimited)</li>
<li><code>llmscu_regenerated</code> action — fires after each successful regeneration with the content string</li>
</ul>

LLMs.txt Curator

Curate, score, and maintain your llms.txt with quality scoring, description suggestions, change detection, and AI crawler analytics.

sourcewatchai

AI SEO and AI visibility analytics for WordPress. See your AI search visibility — which AI tools crawl, cite, and send visitors to your site — and whether ChatGPT, Perplexity, Google AI Overviews, Gemini, and Claude actually surface your content. It is the AI-era answer to “how do I show up in AI search?”
This plugin sends two things to your SourceWatch dashboard:
<ul>
<li>AI bot crawls — when ChatGPT, Perplexity, Google AI, Claude and others fetch your pages.</li>
<li>AI referrals — when a real person clicks through to your site from an AI tool.</li>
</ul>
It uses two complementary beacons so it works even when your site is cached:
<ul>
<li>An in-page script (your Public Key) captures human visitors from AI tools right in 
the browser — so it keeps working even when pages are served from a cache/CDN (where 
server-side code never runs).</li>
<li>A server-side beacon (your Site Key) captures AI bot crawls, which can’t be seen in 
the browser because bots don’t run JavaScript.</li>
</ul>
Neither adds page-load delay, and if SourceWatch is ever unreachable your site loads exactly 
as before. The destination endpoint is fixed inside the plugin, so it can never be 
repointed to send your data elsewhere.
<h3>External service</h3>
This plugin connects your site to SourceWatch (https://sourcewatch.ai), a third-party 
service that turns the data below into your AI-visibility analytics dashboard. The plugin 
does nothing until you install it and add your keys, and you can pause it at any time.
What is sent, and when:
<ul>
<li>On front-end page views: the page URL, the referring URL, the visitor’s IP address and 
user agent, and the HTTP status — sent to https://sourcewatch.ai/api/track/ai.</li>
<li>From Settings → SourceWatch when you click “Check capture”: your keys and this site’s 
domain — sent to https://sourcewatch.ai/api/track/ai/status to confirm setup.</li>
</ul>
Your use of the SourceWatch service is governed by its policies:
<ul>
<li>Terms of Use: https://sourcewatch.ai/terms</li>
<li>Privacy Policy: https://sourcewatch.ai/privacy</li>
</ul>

SourceWatch – AI SEO Analytics

AI SEO & AI visibility analytics — track which AI tools (ChatGPT, Perplexity, Google AI) crawl your WordPress site and send visitors.

LLMs.txt Curator vs SourceWatch – AI SEO Analytics