Description

This plugin generates llms.txt and llms-full.txt from WordPress content and can also serve clean Markdown (.md) versions of posts, pages, and supported public post types, including WooCommerce products when the product post type is enabled.

It is intended for site owners who want to expose important content in formats that are easier for AI systems, search workflows, documentation pipelines, and content reuse tools to process than full HTML pages.

Why llms.txt matters

Web pages are made for browsers and human visitors. They often include menus, layout wrappers, scripts, widgets, and other interface elements around the main content.

llms.txt provides a simpler structured file that highlights important pages, sections, and resources in plain text. This helps website owners present a clearer map of their content.

That matters because tools such as ChatGPT, Claude, Gemini, Perplexity, and similar large language model systems may understand a website more easily when its important content is exposed in a cleaner and more direct format.

For websites, this can support:

AI discovery and GEO workflows
clearer identification of important pages and resources
better visibility for articles, service pages, documentation, and product content
easier retrieval, summarization, and citation-oriented use cases
a more structured content inventory for machine-readable access

Why Markdown matters

Markdown provides a cleaner text representation of published content without depending on the full HTML presentation layer.

This can help websites because Markdown:

removes much of the layout and theme markup around the main content
gives AI systems and text-based tools a more direct version of the page content
makes content easier to export, archive, review, and migrate
supports knowledge bases, documentation workflows, internal search, and retrieval pipelines
creates more portable copies of posts, pages, and WooCommerce product content

Why llms.txt and Markdown work together

llms.txt helps AI systems discover the important parts of a website.

Markdown helps them read and process the actual content in a cleaner format.

Together, they can help websites:

support GEO and LLM-driven discovery
make important content easier for AI assistants to find and understand
create cleaner text sources for retrieval-based systems
reduce reliance on raw HTML for content reuse
keep a more portable and organized content archive

The plugin does not write static files to your server. Output is generated on demand with caching, and no content is sent to external services.

Key Features

Virtual llms.txt and llms-full.txt endpoints.
Optional .md endpoints for individual posts, pages, and public custom post types, including WooCommerce products when the product post type is enabled.
Per-post controls: include or exclude content and add custom notes via the post editor metabox.
Respects noindex settings and can use meta descriptions from supported SEO plugins.
Bulk export of published content as a ZIP archive containing one .md file per item with YAML frontmatter.
Admin settings page with live preview, cache regeneration, and rewrite rule flushing.
WP-CLI commands for generation and export.

Configuration

The settings page offers four main areas:

LLMs.txt Config: Choose which public post types to include, including WooCommerce product when available, set max items per section, override the site description, and add preamble text or custom sections.
Markdown & Endpoints: Toggle public .md serving, control frontmatter fields.
Export Tool: Generate and download a ZIP archive of your content as clean .md files.
Advanced: Regenerate cache, flush rewrites, view current generated output live in the admin preview panel.

Per-post settings appear in a metabox on the edit screen for supported post types.

Usage

llms.txt and llms-full.txt:
– The plugin serves the files at the root of your site (e.g. https://yoursite.com/llms.txt).
– These files can help AI tools and LLM-driven systems identify important website content more clearly.
– The structure follows the format described at https://llmstxt.org/.

.md endpoints:
– Append .md to a public post, page, or supported custom post type URL to receive a Markdown version.
– WooCommerce product URLs can also return Markdown output, for example /product/your-product.md, when product support is enabled.
– The output includes YAML frontmatter (title, date, modified, taxonomies, custom notes when present).

Bulk export:
– Use the Export Tool in the plugin settings or the WP-CLI command to download a ZIP containing .md files for selected post types.

WP-CLI (when available):
wp clustova llms generate wp clustova export markdown --zip

See the plugin settings page for live preview and one-click actions.

Installation

Upload the clustova-llms-txt-markdown-generator folder to the /wp-content/plugins/ directory, or install via the WordPress Plugins screen.
Activate the plugin through the ‘Plugins’ menu in WordPress.
Go to Settings > Clustova LLMs.txt to configure included post types, limits, custom text, and more.
Visit https://yoursite.com/llms.txt and https://yoursite.com/llms-full.txt to see the results.
(Optional) Enable Markdown endpoints and test https://yoursite.com/your-post-slug.md.

After activation, visit Settings > Permalinks and click Save Changes (this is required for the rewrite rules to take effect, especially on subdirectory installs like /wordpress/). You can also use the „Flush Rewrite Rules“ button in the plugin’s Advanced tab.

FAQ

What is llms.txt?: llms.txt is a proposed plain-text standard described at https://llmstxt.org/. It gives websites a structured way to list important pages, resources, and summaries for AI systems and other machine-readable workflows.
How to add llms.txt to WordPress?: Install Clustova LLMs.txt & Markdown Generator, activate it, and go to Settings > Clustova LLMs.txt. The file is served automatically at yourdomain.com/llms.txt. No manual file uploads required.
Why is llms.txt useful for websites?: It helps websites present important content in a simpler format than full HTML pages. This can make it easier for systems such as ChatGPT, Claude, Gemini, Perplexity, and similar tools to find and understand what the site contains.
How can llms.txt help with GEO?: GEO often depends on whether AI systems can identify what a website is about, which pages matter, and where useful source content lives. llms.txt helps by giving those systems a structured map of important pages and content sections.
How do I generate Markdown from WordPress posts?: When .md endpoints are enabled, appending .md to a public post URL returns a Markdown version of that post. The admin area also provides a bulk ZIP export and per-post download links.
Does it work with WooCommerce?: Yes. If your site uses WooCommerce, you can include the product post type in the plugin settings. This allows product pages to be included in llms.txt, Markdown endpoints, and bulk Markdown exports, which can help make catalog content easier to organize, export, and present in cleaner formats.
Why would a website need Markdown versions of posts or pages?: Markdown versions are easier to export, archive, reuse, and process in text-based systems. They can be useful for content review, knowledge bases, internal search, retrieval workflows, documentation systems, and AI processing.
How do llms.txt and Markdown work together?: llms.txt helps external systems discover the important URLs and sections of a site. Markdown helps those systems read the content in a cleaner text format. Together they support both discovery and understanding.
Does it work with Yoast SEO, Rank Math, or SEOPress?: The plugin checks for noindex directives from supported SEO plugins and can use their meta description fields when available. You can disable this behavior in the settings.
Can I customize the content that appears in my llms.txt file?: Yes. Choose which post types to include, set limits per section, add custom preamble text or extra sections, and override descriptions on individual posts via the metabox.
What is the difference between llms.txt and llms-full.txt?: llms.txt is the shorter, primary file. llms-full.txt includes longer excerpts from the selected content. You can enable or disable either file independently in the settings.
Is any of my content sent to external services?: No. Everything is generated locally on your WordPress server. Your data never leaves your site.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Clustova LLMs.txt – Markdown Generator” is open source software. The following people have contributed to this plugin.

Translate “Clustova LLMs.txt – Markdown Generator” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.17

Rewrote readme.txt to explain why llms.txt and Markdown matter for GEO, AI discovery, and LLM understanding in more practical terms.
Added clearer documentation about how systems such as ChatGPT, Claude, Gemini, and Perplexity can benefit from cleaner structured content.
Expanded WooCommerce mentions across the description, usage, and FAQ so product support is easier to understand.

1.0.15

Removed specific domain references (e.g. or97.com) from readme.txt changelog and upgrade notices. Documentation should remain generic and not reference any particular site.

1.0.14

llms.txt audit-driven improvements:
- Fixed homepage URL bug (clean root URL instead of broken .md version) with extra safeguards for front page.
- Added aggressive filtering to exclude theme builder pages (porto_builder, elementor_library, etc.), system pages (cart, checkout, my-account, 404), placeholder/lorem content, and UI template pages.
- Improved product handling: high-level category summaries in main llms.txt (for AI readability), detailed in llms-full.txt. Product descriptions normalized (cleaner notes, no raw shortcodes/entities).
- Added explicit „Company“ / „About“ section and reinforced educational preamble for GEO/LLM benefits.
- Better prioritization and noise reduction so important content (products, tutorials) stands out over CMS noise.
Updated default llms.txt preamble (educational section on why llms.txt + Markdown matter for LLMs, GEO, RAG, etc.) is preserved and now complemented by the new structural sections.
Rebuild ZIP and bump per project rules. Update your site and regenerate cache to see improved llms.txt.

1.0.10

Improved Markdown output for WooCommerce products: added price, SKU, stock status, proper product categories (product_cat), and featured image to YAML frontmatter. Products now get much cleaner, AI-friendly .md files.
Significantly improved cleaning of page builder content (Visual Composer / WPBakery shortcodes common on Porto-style themes). The Home page and product pages should no longer be full of raw [vc_row] etc.
Better LLM descriptions in llms.txt / llms-full.txt for products (includes price + short description).
General robustness improvements in the Markdown converter and llms generator for shortcode-heavy sites.

1.0.9

Added mention of WooCommerce product support (.md endpoints and bulk export work for the ‘product’ post type when enabled in Included Post Types settings).
Updated relevant sections in Description, Key Features, Usage, and Configuration for clarity.

1.0.8

Major UI/UX refactor to match the parent Clustova AI Writer plugin’s card-based layout and component styles for consistent branding.
Converted settings forms to use .aiw-card, .aiw-field, and related components (matching parent’s flat design).
Added dashicons to tabs, improved headers, and applied full violet color scheme, fonts, borders, and spacing throughout the admin pages.
Version 1.0.7 changes included initial violet palette application.

1.0.6

Revised readme.txt and plugin header description to remove promotional language, comparative claims („best“, „AI prefers“, „LLMs love“, „actually read“, etc.), and marketing-style wording per WordPress.org plugin review feedback.
Focused description, FAQ, and usage sections on factual functionality, configuration steps, and how to use the features.
Bumped version per mandatory project rule.

1.0.5

Refined $_POST['post_types'] handling in the admin export form (handle_export_form) to inline sanitize_key sanitization. This resolves the final WordPress.Security.ValidatedSanitizedInput.InputNotSanitized warning reported by Plugin Check.
Bumped version per mandatory project rule (use official version.sh script + update Changelog on every change).

1.0.4

Fixed Plugin Check (WP.org) errors: corrected Text Domain to exactly match the plugin slug (clustova-llms-txt-markdown-generator) in the main plugin header, CLST_TEXT_DOMAIN constant, and every translation function call across admin and exporter classes.
Updated internal admin settings page slug and related links for full consistency with the plugin slug.
Fixed multiple WordPress.Security.ValidatedSanitizedInput.InputNotSanitized warnings (properly sanitize $_POST nonces and post_types, and $_SERVER['HTTP_X_WP_NONCE'] before use in verify_nonce).
Replaced discouraged unlink() calls with wp_delete_file() in the Markdown ZIP exporter. Added compliant handling + phpcs ignore for the controlled readfile() streaming of the generated temporary ZIP before deletion.
Prefixed all top-level variables in uninstall.php ($clst_*) and added matching phpcs:disable comments for the direct database queries used only during plugin uninstall cleanup.
Shortened the plugin „Short Description“ in readme.txt to comply with the 150 character limit.
Fixed outdated folder name reference in Installation instructions.
Bumped version per mandatory project rule (use official version.sh script + update Changelog on every change).

1.0.3

SEO-optimized readme.txt for better visibility in WordPress.org search and plugin directory (stronger keywords around llms.txt, llms txt generator, markdown for wordpress, ai content optimization, etc.).
Improved short description, description section, and FAQ with high-intent search terms while staying 100% compliant with WP.org rules.
Updated screenshots captions for better SEO.

1.0.2

Added comprehensive PHPDoc comments to all classes, methods, and files for professional code quality (required for wp.org uploads from this account).
Reinforced in skill that directory name + main .php file must exactly match the plugin slug derived from Plugin Name.
Bumped version per the mandatory „update version on every change + add PHPDocs“ rule now saved in the wordpress-plugin-dev skill.

1.0.1

Fixed Plugin Check errors (updated „Tested up to“ to current WP version, added proper ABSPATH guard in class-cli.php)
Improved rewrite flushing with flush_rewrite_rules( true ) (hard flush) in activation and admin button for better reliability, especially on subdirectory installs (e.g. /wordpress/)
Updated installation instructions to emphasize visiting Settings > Permalinks > Save Changes after activation
Always increment version on any code changes going forward (per project rule)

1.0.0

Initial release
Virtual /llms.txt and /llms-full.txt serving with spec-compliant formatting and caching
Public .md endpoints for posts, pages and public CPTs
Professional pure-PHP Markdown converter with YAML frontmatter
Full site Markdown ZIP export
Per-post metabox + list table integration
Live admin preview, regenerate, and settings with full security (nonces, capabilities, sanitization, escaping)
WP-CLI commands
Follows WordPress Plugin Directory guidelines and coding standards

Description

Why llms.txt matters

Why Markdown matters

Why llms.txt and Markdown work together

Key Features

Configuration

Usage

Installation

FAQ

What is llms.txt?

How to add llms.txt to WordPress?

Why is llms.txt useful for websites?

How can llms.txt help with GEO?

How do I generate Markdown from WordPress posts?

Does it work with WooCommerce?

Why would a website need Markdown versions of posts or pages?

How do llms.txt and Markdown work together?

Does it work with Yoast SEO, Rank Math, or SEOPress?

Can I customize the content that appears in my llms.txt file?

What is the difference between llms.txt and llms-full.txt?

Is any of my content sent to external services?