odysseynewmedia

<p><strong>Odyssey LLMS</strong> is the definitive control panel for your website’s AI presence. It generates the critical files used by Large Language Models (like ChatGPT, Claude, and Gemini) to understand and cite your content.</p>
<p><strong>For Beginners:</strong> Just activate it. A comprehensive and optimised <code>llms.txt</code> file is instantly generated. No configuration is needed.</p>
<p><strong>For Power Users:</strong> Manage every aspect of your AI strategy. Track bot traffic with built-in analytics, generate JSONL datasets for fine-tuning, and clean up your content with CSS selectors.</p>
<h3>Concepts Explained: Why do you need this?</h3>
<h4>1. What is <code>llms.txt</code>?</h4>
<p>Think of <code>llms.txt</code> as a “Sitemap for AI”. While humans use HTML pages and Search Engines use XML sitemaps, AI agents look for an <code>llms.txt</code> file in your root directory. This file gives them a clean, prioritised list of links to crawl, ensuring they train on your <em>best</em> content and ignore the junk.</p>
<h4>2. What is <code>llms-full.txt</code> (Markdown)?</h4>
<p>This is an optional advanced feature (RAG-Ready). Instead of just providing links, <code>llms-full.txt</code> provides your <strong>actual website content</strong> converted into clean, lightweight Markdown format.<br />
*   <strong>Why it’s useful:</strong> It allows AI agents to ingest your website’s knowledge immediately without needing to visit and scrape every single HTML page. This reduces server load and ensures the AI gets accurate data for “Retrieval Augmented Generation” (RAG).<br />
*   <strong>⚠️ WARNING regarding Virtual Mode Limits:</strong> When using Virtual Mode to generate this file, the item limit for the llms-full.txt file is securely capped at 50 by default. <em>Manually increasing this limit beyond 50 in the ‘Tools’ settings will drastically increase server load and risks causing immediate 500/503 server crashes.</em> Use this feature at your own risk. If you require more than 50 items in your llms-full.txt file, we recommend using Physical Mode instead.</p>
<h4>3. What is <code>llms.jsonl</code> (Fine-Tuning)?</h4>
<p>This file formats your content into prompt-completion pairs (JSON Lines). This is the standard format used to <strong>fine-tune</strong> models like GPT-4 or Llama 3 on your specific data.</p>
<p><strong>New Features in 6.0:</strong></p>
<ul>
<li><strong>JSONL Generator:</strong> Create a dataset ready for fine-tuning custom AI models.</li>
<li><strong>Content Cleaning:</strong> Use CSS selectors (e.g., <code>.sidebar</code>, <code>.comments</code>) to strip unwanted elements from your Markdown and JSONL files.</li>
<li><strong>Visual Analytics:</strong> Visualise exactly which AI bots (ChatGPT, Claude, Google AI, etc.) are accessing your files with a built-in dashboard widget and charts.</li>
<li><strong>WooCommerce Integration:</strong> Automatically generates a structured “Products” section including Price, Stock, and SKU.</li>
</ul>
<p><strong>Key Features:</strong></p>
<ul>
<li><strong>Clean Tabbed Interface:</strong> Organised into General Rules, Content Sourcing, Analytics, Robots.txt, Security, and Tools.</li>
<li><strong>Granular Bot-Specific Rules:</strong> Set detailed <code>Allow</code> or <code>Disallow</code> rules for individual AI crawlers (<code>GPTBot</code>, <code>Google-Extended</code>, etc.).</li>
<li><strong>“Block All by Default” Mode:</strong> Create a secure “whitelist” by blocking all crawlers by default and only allowing the bots you explicitly enable.</li>
<li><strong>Settings Import & Export:</strong> Perfect for agencies. Easily back up, restore, and migrate your settings between sites with JSON import/export.</li>
<li><strong>Advanced Scheduling:</strong> Regenerate your file on save, manually, or on a recurring schedule (Hourly, Daily, Weekly, Monthly).</li>
<li><strong>Safety Validator:</strong> Prevents accidental blocking of all traffic in <code>robots.txt</code>.</li>
</ul>


Odyssey LLMS

The complete AI control panel for WordPress. Generate llms.txt, Markdown, and JSONL. Includes AI Analytics and Content Cleaning.

Kang Chen

<p>KCITService – AI Site Beacon generates the four standard AI-readable files (<code>llms.txt</code>, <code>llms-full.txt</code>, <code>llms-index.json</code>, <code>llms-sitemap.xml</code>) plus an optional <code>/ai.txt</code> for training permissions, and integrates with your <code>/robots.txt</code>. Where it differs from other plugins in this category:</p>
<h4>How this plugin is different</h4>
<ul>
<li><strong>Multilingual UI out of the box</strong> — 8 bundled language packs (English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish, French, German). No separate language pack downloads, no machine-translated strings — every UI label, button, help text, and FAQ entry was hand-translated.</li>
<li><strong>CJK-aware processing</strong> — the word counter and summary builder correctly handle Chinese, Japanese, and Korean characters. Most llms.txt generators undercount CJK content (counting an entire 1,000-character Chinese article as “1 word”) or produce mangled URL-encoded TOC anchors. We don’t.</li>
<li><strong>All three signal files in one plugin</strong> — <code>llms.txt</code> for content discovery, <code>robots.txt</code> integration for crawl signals, and <code>ai.txt</code> (Spawning.ai format) for training permissions. One admin area, consistent UX, single generation pipeline.</li>
<li><strong>Per-bot training controls</strong> — the ai.txt tab ships with a curated list of 13 known AI user-agents (OpenAI’s GPTBot/ChatGPT-User/OAI-SearchBot, Anthropic’s ClaudeBot, Google-Extended, Common Crawl’s CCBot, PerplexityBot, ByteDance’s Bytespider, Applebot-Extended, Amazonbot, Meta-ExternalAgent, cohere-ai) with default/allow/disallow radios for each.</li>
<li><strong>Settings version history with rollback</strong> — every settings change is snapshotted (last 20 versions kept), and one click rolls back to any prior state. The rollback itself is reversible.</li>
<li><strong>Privacy-first</strong> — the free version makes zero external API calls. Everything is processed locally inside WordPress. Customer/order/account data from WooCommerce is never read.</li>
</ul>
<h4>Generated files</h4>
<ul>
<li><code>/llms.txt</code> — concise Markdown guide and index</li>
<li><code>/llms-full.txt</code> — fuller Markdown content package</li>
<li><code>/llms-index.json</code> — structured machine-readable index</li>
<li><code>/llms-sitemap.xml</code> — XML list of AI-readable resources</li>
<li><code>/ai.txt</code> — optional Spawning.ai-style training permissions file</li>
<li><code>/robots.txt</code> — integrated via WordPress’s <code>robots_txt</code> filter (does not write a physical file, plays well with SEO plugins)</li>
</ul>
<h4>Standard features</h4>
<ul>
<li>Clean Markdown conversion of your public WordPress content</li>
<li>Two deployment modes: static files written to your site root, or virtual endpoints if root is not writable</li>
<li>Per-post include / exclude control via a sidebar meta box</li>
<li>Category, tag, and URL pattern exclusions</li>
<li>Manual or scheduled regeneration via WP-Cron (daily, weekly, monthly)</li>
<li>Live preview of the generated files before publishing</li>
</ul>
<h4>What this plugin does NOT claim</h4>
<p>This plugin does not claim that ChatGPT, Claude, Gemini, Perplexity, or any specific AI system will automatically crawl, index, train on, or use the generated files. The <code>llms.txt</code> and <code>ai.txt</code> conventions are emerging standards and adoption by individual AI providers is voluntary. Treat this plugin as making your signals available, not as a guarantee of how any specific AI service will behave.</p>


KCITService – AI Site Beacon

AI-readable file suite for multilingual sites: llms.txt + ai.txt + robots.txt integration, 8 bundled UI languages, CJK-aware.

Odyssey LLMS vs KCITService – AI Site Beacon