WordPress llms.txt Plugin Guide: Clustova LLMs.txt, llms-full.txt, Markdown Endpoints and Bulk Export

Why WordPress sites need AI-friendly content surfaces

Most WordPress sites still publish content only in traditional HTML page form. That works for browsers and standard search crawlers, but it is not always the best format for AI systems, internal retrieval workflows, or downstream Markdown-based content pipelines.

AI tools often perform better when they can read a clean site summary, access lightweight text representations of content, or ingest structured Markdown files instead of parsing theme-heavy frontend markup filled with navigation, widgets, and page-builder noise.

That is the problem Clustova LLMs.txt solves. It gives WordPress site owners a way to generate llms.txt, llms-full.txt, public Markdown endpoints, and full-site Markdown exports directly from the WordPress database.

What the Clustova LLMs.txt plugin does

The plugin is intentionally lightweight in architecture. It does not depend on an external API and it does not write static files into your server by default. Instead, it generates outputs on demand and uses internal caching for efficiency.

• Serves a virtual /llms.txt file
• Serves a virtual /llms-full.txt file with broader context
• Supports public .md endpoints for posts, pages, and selected custom post types
• Includes a ZIP export tool for bulk Markdown downloads
• Adds per-post controls so editors can include, exclude, or annotate content
• Provides WP-CLI commands for generation and export workflows

That makes it useful for publishers, agencies, product teams, documentation sites, and anyone building retrieval pipelines from WordPress content.

What llms.txt and llms-full.txt are for

The plugin follows the llmstxt.org concept of a structured, root-level summary file for LLMs. The shorter llms.txt acts as the main discovery layer, while llms-full.txt provides a richer representation with longer excerpts and more context from the included content.

That distinction is useful in practice. Some AI systems only need a concise map of the site and its important sections. Others benefit from a fuller site snapshot that includes more detail about what each piece of content covers.

With Clustova LLMs.txt, both outputs can be generated dynamically from your content model rather than being hand-maintained text files that quickly drift out of date.

Why Markdown endpoints are one of the most valuable features

For many teams, the Markdown endpoints are even more useful than the top-level llms.txt files. When enabled, you can append .md to a supported content URL and receive a Markdown version of that page or post.

That matters because Markdown is a much better interchange format for many AI workflows. It is lightweight, human-readable, easy to store in versioned systems, and much easier to ingest into RAG pipelines or knowledge-base transformations than heavily styled HTML.

The plugin also includes YAML frontmatter in those outputs. That means the Markdown is not just plain text. It carries structured metadata such as title, dates, taxonomies, and notes so the content remains useful after export or ingestion.

WooCommerce and custom post type support

The plugin is not limited to standard WordPress posts. It can also work with public custom post types, including WooCommerce products when the product post type is enabled in settings.

That makes it a practical fit for sites that are part content hub, part commerce catalog, or part documentation library. Instead of building separate export systems for every post type, you can use one plugin to create a more unified Markdown and llms.txt layer across the site.

How to set up the plugin correctly

Installation is straightforward, but there are a few details worth getting right early so the routes and outputs behave properly.

1. Install and activate the plugin
2. Open Settings -> Clustova LLMs.txt
3. Choose which post types should be included in llms.txt generation
4. Enable Markdown endpoints if you want public .md versions of content URLs
5. Review frontmatter settings and export options
6. Visit /llms.txt and /llms-full.txt to verify output
7. Test a real endpoint such as /your-post-slug.md

One important operational note: after activation, WordPress rewrite rules may need refreshing. Saving permalinks again or using the plugin’s rewrite flush action is the safest way to make sure the routes resolve immediately.

The four settings areas that matter most

The plugin groups its configuration into four practical areas, which makes it easier to manage without turning the admin into a cluttered export dashboard.

1. LLMs.txt Config

This is where you choose which public post types are included, define limits per section, and override or expand the site-level summary using custom preamble text or extra sections.

2. Markdown and Endpoints

This controls public .md output, including whether endpoints are available and what frontmatter fields appear in the generated Markdown.

3. Export Tool

This generates a ZIP archive containing one Markdown file per selected content item. It is ideal for migrations, archives, audits, and ingestion pipelines.

4. Advanced

Advanced settings handle cache regeneration, rewrite flushing, and live preview of generated output. That is especially useful when you are troubleshooting route behavior or checking the shape of the generated files after a content model change.

Why the export tool matters for AI and content ops

The ZIP export feature is more than a convenience button. It turns WordPress into a usable Markdown source for teams that want a portable, structured snapshot of site content.

That has obvious use cases:

• Building a RAG knowledge base from WordPress content
• Archiving content for internal documentation teams
• Cleaning content before moving it into a different CMS
• Creating AI-friendly source files for downstream agents and tooling

Because the files include frontmatter, the result is much more useful than dumping raw text or scraping HTML into ad hoc scripts.

Per-post controls are important for real editorial workflows

One reason many export and summary plugins break down in real use is that editorial teams need exceptions. Some content should be excluded. Some needs custom notes. Some should not appear in AI-facing outputs because it is outdated, thin, or context-dependent.

Clustova LLMs.txt handles this with per-post controls in the editor metabox. That gives editors direct control over inclusion and notes at the content level instead of forcing everything to be managed globally.

Best practices for better outputs

The plugin can transform and expose content cleanly, but the quality of the source content still matters. A better llms.txt layer starts with better content hygiene.

• Include only public post types that make sense for AI consumption
• Exclude low-value pages such as placeholders or utility templates
• Use custom notes where a page needs extra machine-readable context
• Regenerate outputs after major imports, taxonomy changes, or content cleanup
• Use the ZIP export to audit what your site looks like outside the frontend theme layer

That last point is underrated. Seeing your site as Markdown often reveals how much noise, thin copy, or structural inconsistency exists in the content model.

Final takeaway

Clustova LLMs.txt is useful because it solves a real operational problem instead of chasing a trend keyword. It gives WordPress sites a practical AI-readable output layer: site summaries, richer full summaries, per-page Markdown endpoints, and exportable Markdown archives.

If your team is thinking about GEO, AI search visibility, documentation reuse, or WordPress-to- knowledge-base workflows, this is one of the simplest ways to get cleaner structured outputs without custom development.

Frequently Asked Questions

What does the Clustova LLMs.txt plugin do?

It generates virtual llms.txt and llms-full.txt outputs, public Markdown endpoints for supported content, and ZIP exports of Markdown files with frontmatter.

Does the plugin create static files on the server?

No. It generates output dynamically and uses internal caching instead of writing permanent static files to disk.

Can it generate Markdown for WooCommerce products?

Yes. WooCommerce products are supported when the product post type is enabled in the included post types settings.

Are there WP-CLI commands?

Yes. The plugin includes WP-CLI commands for generation and ZIP export workflows.

Is any site content sent to external services?

No. The plugin works locally inside WordPress and does not send your content to external APIs in order to generate these outputs.