David Perez

closemarketing

Alex Brea

Knowledge Base Chatbot helps you curate the exact content you want to use as a “knowledge base” and generates a single Markdown file (<code>llm-knowledge-chatbot.md</code>) that can be consumed by an external chatbot or LLM pipeline.
From the WordPress admin, you can:
<ul>
<li>Select content from any public post type that is available in the admin (Pages, Posts, and most custom post types).</li>
<li>Add selected items to a curated list.</li>
<li>Reorder the list via drag & drop.</li>
<li>Regenerate the Markdown file at any time (it is also regenerated automatically after adding/removing items).</li>
</ul>
The generated file is saved in your WordPress root folder and can be accessed via a public URL such as: 
 https://example.com/llm-knowledge-chatbot.md

Knowledge Base Chatbot

Generate a Markdown knowledge base file from selected WordPress content (pages, posts, and CPTs) to power an external chatbot/LLM workflow.

Pavel Sherer

LLM Friendly adds two capabilities to your WordPress site:
1) /llms.txt 
An LLM-friendly index of the website with main links and a list of latest items per post type. You can exclude individual entries from the feed via Settings → LLM Friendly → llms.txt → “Excluded items”.
2) Markdown exports 
For selected post types, the plugin exposes .md endpoints under: 
{base}/{post_type}/{path}.md 
Entries can override their Markdown body via the “Markdown override” sidebar panel (or Classic Editor metabox) and can also be excluded from export through the same settings page.
This is useful for LLMs, indexing bots, and users who prefer plain text. 
You can opt in to excerpts in llms.txt via <code>llms_show_excerpt</code>, and you can send <code>X-Robots-Tag: noindex, nofollow</code> for Markdown exports via <code>md_send_noindex</code> if you want Markdown-only consumers without search engine indexing. 
If the automatic Markdown conversion does not fit a post, use the “Markdown override” sidebar panel (Gutenberg) or the Classic Editor metabox to provide a custom Markdown or block-based replacement.
<h4>Key features</h4>
<ul>
<li>llms.txt endpoint with cached generation, optional excerpts, a configurable custom Markdown block, and a per-post exclusion list.</li>
<li>Markdown exports for selected post types with Gutenberg-to-Markdown conversion, per-post Markdown overrides (sidebar panel/metabox), and a per-post exclusion list shared with llms.txt.</li>
<li>Configurable base path for exports (e.g. “llm”) and per-post-type enable/disable toggles; changing the base path requires flushing rewrites.</li>
<li>Manual or automatic regeneration of the cached llms.txt with ETag/Last-Modified headers.</li>
<li>Optional X-Robots-Tag: noindex, nofollow for both /llms.txt and Markdown exports; the Markdown header is controlled by <code>md_send_noindex</code>.</li>
<li>Toggle excerpts in llms.txt via <code>llms_show_excerpt</code> to add one-line summaries under each item.</li>
<li>Optional site title/description overrides plus a sitemap URL field for the generated llms.txt.</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 6.0+</li>
<li>PHP 7.4+</li>
</ul>
If requirements are not met, the plugin displays an admin notice and does not run.

LLM Friendly

Expose llms.txt and Markdown versions of posts/pages to make your site easier for LLMs to navigate and consume.

Knowledge Base Chatbot vs LLM Friendly