Linux 软件免费装
Banner图

Odyssey LLMS

开发者 odysseynewmedia
更新时间 2026年6月18日 16:35
PHP版本: 5.8 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

seo sitemap ai llms llms.txt

下载

6.2.0 6.2.1 6.2.2 6.3.0 6.1.13 6.1.11 6.1.12 6.1.14

详情介绍:

Odyssey LLMS 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. For Beginners: Just activate it. A comprehensive and optimised llms.txt file is instantly generated. No configuration is needed. For Power Users: 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. Concepts Explained: Why do you need this? 1. What is llms.txt? Think of llms.txt as a "Sitemap for AI". While humans use HTML pages and Search Engines use XML sitemaps, AI agents look for an llms.txt file in your root directory. This file gives them a clean, prioritised list of links to crawl, ensuring they train on your best content and ignore the junk. 2. What is llms-full.txt (Markdown)? This is an optional advanced feature (RAG-Ready). Instead of just providing links, llms-full.txt provides your actual website content converted into clean, lightweight Markdown format. * Why it's useful: 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). * ⚠️ WARNING regarding Virtual Mode Limits: When using Virtual Mode to generate this file, the item limit for the llms-full.txt file is securely capped at 50 by default. Manually increasing this limit beyond 50 in the 'Tools' settings will drastically increase server load and risks causing immediate 500/503 server crashes. 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. 3. What is llms.jsonl (Fine-Tuning)? This file formats your content into prompt-completion pairs (JSON Lines). This is the standard format used to fine-tune models like GPT-4 or Llama 3 on your specific data. New Features in 6.0: Key Features:

安装:

  1. Upload the odyssey-llms folder to the /wp-content/plugins/ directory.
  2. Activate the plugin through the 'Plugins' menu in your WordPress dashboard.
  3. That's it! A llms.txt file has been generated. A new "Odyssey LLMS" menu item will appear in your admin sidebar.
  4. (Optional) Navigate to the Odyssey LLMS page to view Analytics or configure advanced settings.

常见问题:

Where do I find the settings page?

The settings page is located in its own top-level menu in your WordPress admin sidebar, labelled Odyssey LLMS.

How do I clean up the Markdown content?

In the "Content Intelligence" tab, look for the "Content Cleaning (CSS)" field. Enter CSS selectors for elements you want to remove, separated by commas (e.g., .footer, .nav, #sidebar).

How do I enable Analytics?

Go to the main settings tab and select "Virtual File" as your serving method. This allows WordPress to intercept bot requests and log them to your dashboard.

Does this conflict with Yoast SEO or RankMath?

No. The Robots.txt editor includes intelligent conflict detection. It will automatically fetch and import any virtual rules created by other SEO plugins so you don't lose them.

Can I increase the limit of pages in llms-full.txt?

⚠️ WARNING: While you can manually increase the post/page limit for the llms-full.txt file in the settings, we strongly warn against setting it too high (especially in Virtual Mode). Doing so will drastically increase server load and risks causing immediate 500/503 server crashes due to the heavy processing required. If you require a large number of items, we recommend using Physical Mode.

What is the JSONL Prompt Template and how does I use it?

The JSONL Prompt Template controls the "question" side of each entry in your llms.jsonl fine-tuning dataset. When you want to train a custom AI model (such as GPT-4, Llama 3, or any fine-tuneable LLM) on your website's content, that process requires structured "Question and Answer" pairs - known as prompt and completion. How it works: The plugin generates llms.jsonl where every line is a JSON object in this format: {"prompt": "What is My Post Title?", "completion": "The full text of that post..."} The template field lets you define the prompt structure for every post on your site. Use {{title}} as a dynamic placeholder. The plugin will automatically replace it with each post's actual title at generation time. Examples by use case:

  • Default / General: What is {{title}}?
  • Service business: Tell me about the {{title}} service provided by our company.
  • E-commerce / Products: What are the features and specifications of {{title}}?
  • Knowledge base / Support: How do I {{title}}?
By customising this template, you are priming your fine-tuning dataset so the resulting model learns to respond to the exact style of queries your users will ask.

What is the difference between Physical File and Virtual File mode?

Physical File (Recommended for most sites): The plugin writes a real static llms.txt file to your server's root directory. This is served directly by your web server (Apache/Nginx) with maximum speed, and does not require WordPress to load for every bot request. The downside is that bot visits cannot be tracked for Analytics. Virtual File (Enable Analytics): The file is served dynamically by WordPress via a rewrite rule. This allows the plugin to intercept every request and log it to the Analytics dashboard. It also enables Rate Limiting to throttle abusive bots. The trade-off is a small performance overhead since WordPress must load for each request. Both modes support llms.txt, llms-full.txt (Markdown), and llms.jsonl generation.

What does "Include Taxonomy Archives" do?

When you select specific taxonomies (e.g. Categories, Tags, WooCommerce Product Categories) in the Content Source tab, the plugin will fetch all non-empty terms for those taxonomies and include their archive page URLs in the generated llms.txt. This is useful for giving AI crawlers a complete picture of your site's topic structure, not just individual posts.

What does "Include Author Archives" do?

When this option is enabled, the plugin fetches all WordPress users who have at least one published post and appends their author archive URLs (e.g. yoursite.com/author/name/) to the generated llms.txt. This is useful for sites where author credibility and profiles are part of the content strategy.

How does the WooCommerce integration work?

When WooCommerce Products is enabled in the Content Source settings and WooCommerce is active, the plugin automatically enriches product entries with structured metadata pulled directly from WooCommerce:

  • Price - the product's formatted sale/regular price.
  • SKU - the product's stock-keeping unit identifier (if set).
  • Stock Status - whether the product is In Stock or Out of Stock.
This data is prepended to the product content in both llms-full.txt (Markdown) and llms.jsonl, giving AI models accurate, up-to-date product information without needing to scrape individual product pages.

What is the Content Order setting?

The Content Order setting in the Content Source tab controls the order in which posts appear across all generated files (llms.txt, llms-full.txt, llms.jsonl). Since AI agents typically give more weight to content they encounter earlier in a file, ordering by your most recent or most engaged-with content ensures they train on your best material first. Available options:

  • Date: Newest First (Default) - Most recently published content appears first.
  • Date: Oldest First - Chronological order from the beginning.
  • Title A → Z - Alphabetical by post title.
  • Most Commented First - Prioritises your most engaged content.
  • Menu/Page Order - Uses the WordPress page order field, ideal for structured sites.

How does rate limiting work?

When Virtual File mode is active, the plugin tracks the number of requests made by each IP address within a rolling time window. If a bot or visitor exceeds the configured request limit, they are temporarily blocked and receive a 429 Too Many Requests response with a Retry-After header. The block duration is configurable in the Security tab and enforces a minimum of 1 hour to prevent configuration errors from causing permanent lockouts.

更新日志:

6.3.0 6.2.2 6.2.1 6.2.0 6.1.14 6.1.13 6.1.12 6.1.11 6.1.8 6.1.7 6.0.8 6.0.0 5.8.3 5.8.2 5.8.0 5.7.1 5.4.6 5.3.3 5.2.1 5.0.0 6.1.14 4.0.0 3.0.0 2.2.1 2.2.0 2.1.0 2.0.0 1.0.0