Title: MSG LLMs TXT Manager Author: cropllm Published: 8 september 2025 Last modified: 28 september 2026 --- Plugins zoeken ![](https://ps.w.org/msg-llms-txt-manager/assets/banner-772x250.png?rev=3368722) ![](https://ps.w.org/msg-llms-txt-manager/assets/icon-256x256.png?rev=3368722) # MSG LLMs TXT Manager Door [cropllm](https://profiles.wordpress.org/cropllm/) [Download](https://downloads.wordpress.org/plugin/msg-llms-txt-manager.2.2.1.zip) * [Details](https://nl.wordpress.org/plugins/msg-llms-txt-manager/#description) * [Beoordelingen](https://nl.wordpress.org/plugins/msg-llms-txt-manager/#reviews) * [Installatie](https://nl.wordpress.org/plugins/msg-llms-txt-manager/#installation) * [Ontwikkeling](https://nl.wordpress.org/plugins/msg-llms-txt-manager/#developers) [Ondersteuning](https://wordpress.org/support/plugin/msg-llms-txt-manager/) ## Beschrijving Most llms.txt plugins publish one file and stop. Measured server logs show that file is fetched mainly by SEO bots rather than by AI assistants, while the technique that does deliver content to agents is ordinary HTTP content negotiation. This plugin does both, and then shows you which one is working on your site. **Content negotiation.** When a client requests a page with `Accept: text/markdown`, it gets a clean Markdown version instead of HTML. Coding agents use this. Browsers, search crawlers and everything else are unaffected and still receive HTML. **Markdown mirrors.** Any page is available as Markdown by appending `.md` to its URL. Mirrors are served with a noindex header so they never compete with your pages in search. **llms.txt.** A spec-compliant index: one H1, a blockquote summary, H2 sections of links with descriptions, and an `Optional` section. Built from your published content, or written by hand. **llms-full.txt.** Every listed page as Markdown in a single file, so an agent can read the whole site in one request. Size-capped so it stays inside a model’s context window. **Agent activity log.** These clients do not run JavaScript, so they never appear in your analytics. The plugin records which agents request which paths and in which format, including requests for pages that do not exist, which tells you the titles agents expect you to have. **Crawler rules.** Optional Allow and Disallow rules for AI user agents, written into robots.txt where crawlers actually read them. Everything is virtual. No files are written to disk. #### What this will and will not do It will make your content cheap and accurate for an agent to read, and it will tell you who is reading it. It will not lift your Google rankings. Google has stated that llms.txt has no effect on Search or AI Overviews, and no major AI provider has committed to consuming the file. Treat this as infrastructure for agents, not as an SEO tactic. If your logs show your main AI reader is fetching HTML, the highest-value work is still keeping your rendered HTML clean. #### For developers Filters: `msgltm_index_document`, `msgltm_full_document`, `msgltm_post_document`,` msgltm_posts_for_type`, `msgltm_is_excluded`. ## Schermafbeeldingen [⌊Settings tab: surfaces, index file and crawler rules.⌉⌊Settings tab: surfaces, index file and crawler rules.⌉[ Settings tab: surfaces, index file and crawler rules. [⌊Content tab: post type selection and a live preview.⌉⌊Content tab: post type selection and a live preview.⌉[ Content tab: post type selection and a live preview. [⌊Agent activity: which agents read your site, and in which format.⌉⌊Agent activity: which agents read your site, and in which format.⌉[ Agent activity: which agents read your site, and in which format. ## Installatie 1. Upload and activate the plugin. 2. Go to **Settings LLMs TXT Manager**. 3. On the Content tab, choose which post types to include and check the preview. 4. On the Settings tab, write a summary, then run the diagnostics to confirm every endpoint responds correctly. ## FAQ ### What is llms.txt? A Markdown file at the root of a site giving AI models a curated map of the content. It was proposed by Jeremy Howard of Answer.AI in September 2024. It is a community convention, not a standard from any recognised body. ### Do AI crawlers actually read it? Rarely. Log studies consistently show the file is fetched mostly by SEO tools and generic bots rather than by AI assistants. Markdown delivered through content negotiation sees far more real agent use. Both are enabled here, and the Agent activity tab will tell you which is true for your site rather than leaving you to guess. ### Will the .md mirrors cause duplicate content problems? No. Every mirror is sent with an `X-Robots-Tag: noindex, nofollow` header, so search engines will not index them. ### Why does the negotiation check say “blocked by” my cache? Page caches such as Breeze, WP Super Cache and Varnish store the HTML of a URL and serve it to every later request for that URL before WordPress loads. They key on the URL alone, so an agent asking for Markdown gets the stored HTML and the plugin never sees the request. This is a property of how those caches work, not a bug. Agents still get Markdown through the `.md` mirror and through the `rel="alternate"` link on every page, both of which work behind any cache. Negotiation works fully on hosts whose cache honours `Vary: Accept` or where pages are not cached. ### Why was my llms.txt slow before 2.2.0? Versions up to 2.1.0 sent `Cache-Control: max-age=0, must-revalidate`, so every request went to WordPress. That was a deliberate choice to keep the file current, and it was the wrong trade: on a host where an uncached request takes three or four seconds, every agent and every audit paid that cost. From 2.2.0 the file is cacheable for an hour by default, and you can change that under Surfaces. ### Does content negotiation break my caching? It should not, and the plugin works hard to make sure. Negotiated responses carry` Vary: Accept`, `Cache-Control: no-store`, the `DONOTCACHEPAGE` constant that WordPress cache plugins honour, and the LiteSpeed and CDN equivalents. Even so, some caches ignore all of that. The diagnostics test for exactly this: they request the page as a browser, then as an agent, then as a browser again. If the second browser request comes back as Markdown, negotiation is switched off automatically and the cache is purged. Run the diagnostics after enabling negotiation and after changing cache plugins. ### Is llms.txt the same as robots.txt? No. robots.txt controls crawler access. llms.txt recommends content and cannot block anything. Allow and Disallow lines inside an llms.txt file are ignored by every crawler, which is why this plugin writes those rules to robots.txt instead. ### Will this slow my site down? No. Files are built in the background and stored, so a request is only ever answered from what is already built — a visitor is never made to wait for a rebuild. Markdown conversion happens once per post and is cached until that post changes. Nothing calls out to the network. ### PageSpeed Insights says my llms.txt failed with a timeout. What do I do? Switch on **Static files** under Surfaces. The file is then written to your WordPress directory and served by the web server directly, with no PHP and no page cache involved, which removes the timeout entirely. This matters on hosts where an uncached WordPress request takes several seconds: every other page on such a site is fast only because a page cache serves it, and llms.txt cannot be page-cached without a cache mangling its content type. ### PageSpeed Insights says my llms.txt failed. Why? Run the diagnostics on the Settings tab first; they now report how long the file takes to serve. Lighthouse fails the audit if fetching the file errors or times out, so a slow response looks identical to a broken file. If the content itself is in question, the audit checks three things: an H1 heading, a length over 50 characters, and at least one Markdown-style `[text](url)` link. Files this plugin generates satisfy all three. Note also that there is an open Lighthouse bug where the audit fails valid files on PageSpeed’s current Chrome build. ## Beoordelingen Er zijn geen beoordelingen voor deze plugin. ## Bijdragers & ontwikkelaars “MSG LLMs TXT Manager” is open source software. De volgende personen hebben bijgedragen aan deze plugin. Bijdragers * [ Hugo ](https://profiles.wordpress.org/cropllm/) [Vertaal “MSG LLMs TXT Manager” in je eigen taal.](https://translate.wordpress.org/projects/wp-plugins/msg-llms-txt-manager) ### Interesse in ontwikkeling? [Bekijk de code](https://plugins.trac.wordpress.org/browser/msg-llms-txt-manager/), haal de [SVN repository](https://plugins.svn.wordpress.org/msg-llms-txt-manager/) op, of abonneer je op het [ontwikkellog](https://plugins.trac.wordpress.org/log/msg-llms-txt-manager/) via [RSS](https://plugins.trac.wordpress.org/log/msg-llms-txt-manager/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 2.2.1 * Fixed: on sites with a static front page, the Markdown link in the page head pointed at an invalid address. Appending .md to the front page permalink produced a hostname rather than a URL, so the link in every homepage was broken. The front page now correctly points at /index.md. * Fixed: the diagnostics tested the front page, which produced the same invalid mirror URL. They now test an inner page instead, which is both a valid test and a faster one. * Changed: a diagnostic that times out fetching one of your own pages is reported as a warning explaining that the page could not be generated in time, rather than as a plugin failure. #### 2.2.0 * Added: a cache lifetime setting, defaulting to one hour. Previous versions sent` max-age=0, must-revalidate`, which forced every single request back to WordPress. On hosts where an uncached request takes several seconds, that alone was enough to make agents and PageSpeed Insights time out. A CDN or reverse proxy can now answer most requests without waking WordPress. * Added: a daily check that measures how long your own llms.txt takes to serve. If it is slow enough that agents will give up, the plugin says so in the admin with a one-click fix, rather than leaving you to discover it from a failed audit. * Added: the diagnostics report the exact Cache-Control header in use. #### 2.1.0 * Added: optional static file output. llms.txt and llms-full.txt are written to the WordPress directory, so the web server serves them directly without loading WordPress. On sites where an uncached request is slow, this is the difference between a file agents can fetch and one they time out on. Off by default; switch it on under Surfaces. * Added: the diagnostics recommend static output when the index is slow to serve, and confirm the file is on disk once it is enabled. * Safety: an existing llms.txt that the plugin did not create is never overwritten, and only files the plugin wrote are removed on deactivation or uninstall. #### 2.0.7 * Fixed: on sites with many pages, the first request after the 12-hour cache expired had to rebuild the whole file, which could be slow enough to time out. A timed- out fetch is reported by Lighthouse and PageSpeed Insights as a failed llms.txt. Requests are now never made to wait for a build: the stored file is served immediately even when stale, and refreshed in the background. * Changed: built files are kept in an option rather than a transient, so an object cache cannot evict them and leave a visitor to rebuild. * Changed: publishing queues a background refresh instead of emptying the cache. Saving on the settings screens still rebuilds immediately. * Added: `stale-while-revalidate` and `stale-if-error` cache directives so a CDN can always answer instantly. * Added: a response-time check in the diagnostics, which warns if the index takes more than three seconds to serve. #### 2.0.6 * Fixed: a fatal error on /llms.txt when WordPress core sitemaps are enabled (sites without an SEO plugin). The sitemap URL was read from the wrong object. * Fixed: root-relative links in converted Markdown dropped a non-standard port from the site URL. * Verified end to end inside WordPress 7.1: every endpoint, header, negotiation path, admin screen, form handler, nonce check, the meta box, activation, upgrade migration, and uninstall. #### 2.0.5 * Changed: diagnostics now recognise when a page cache answered a request before WordPress ran. Content negotiation blocked in this way is reported as a limitation of the cache, with an explanation, rather than as a failure. * Changed: the content negotiation setting explains which caching setups it can and cannot work behind. #### 2.0.4 * Changed: responses are now sent with `Cache-Control: public, max-age=0, must- revalidate` instead of a five-minute lifetime. Browsers and CDNs revalidate on every request and receive a 304 when nothing has changed, so edits appear immediately. #### 2.0.3 * Fixed: caches that capture output through PHP’s output buffer (Breeze, WP Super Cache, WP Rocket, W3 Total Cache, Cache Enabler and others) could store every plugin response and re-serve it labelled text/html, regardless of headers or DONOTCACHEPAGE. The plugin now closes all output buffers before writing any response, so such caches capture nothing. Verified against Breeze’s own cache handler. * Fixed: purging Breeze now uses its full purge, which also clears Cloudways Varnish. * Added: diagnostics name the active page cache and give cache-specific exclusion advice when needed. #### 2.0.2 * Fixed: page caches that ignore the Vary header could store a negotiated Markdown response under the HTML URL and serve it to browsers. Negotiated responses are now marked uncacheable at every layer (DONOTCACHEPAGE, LiteSpeed API, Cache-Control no-store, CDN and surrogate headers). * Fixed: the “browsers get HTML” diagnostic trusted the Content-Type header, which a cache can fake. It now inspects the body, runs before and after the Markdown request, and if it finds Markdown being served to browsers it switches negotiation off and purges the cache. * Added: a purge button that clears the plugin’s caches and asks WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed, WP Fastest Cache, SiteGround Optimizer, Cache Enabler, Breeze, Hummingbird, WP Engine or Kinsta to purge. * Changed: upgrading from 2.0.0 or 2.0.1 switches content negotiation off and purges caches, with a notice asking you to run the diagnostics before re-enabling it. #### 2.0.1 * Fixed: Manual mode was saved and shown in the admin but never served. /llms.txt always returned the generated index. Manual content is now served correctly. * Changed: the endpoint cache header dropped from one hour to five minutes, so edits appear quickly. ETags still keep repeat requests cheap. * Added: the Settings tab states which document is currently being served, and the Content tab warns when its preview is not what visitors receive. #### 2.0.0 * Added: content negotiation. A request with `Accept: text/markdown` receives Markdown, with a `Vary: Accept` header for caches. * Added: Markdown mirrors at any URL plus `.md`, served noindex. * Added: `llms-full.txt`, a single size-capped file containing every listed page as Markdown. * Added: an HTML to Markdown converter handling headings, lists, nested lists, tables, code blocks, blockquotes, links and images. * Added: agent activity logging, showing per-agent HTML and Markdown counts and requests for pages that do not exist. * Added: per-post controls to pin, exclude, or override the description. * Added: descriptions are taken from Yoast, Rank Math, SEOPress or AIOSEO when present, and pages those plugins mark noindex are excluded. * Added: diagnostics that request every endpoint and report what came back. * Added: `rel="alternate"` Markdown link in the page head, ETag and conditional request support, and developer filters. * Security: text and titles are escaped so page content can never become live markup or forge a link in a generated file. #### 1.6.0 * Fixed: the served file was HTML-escaped, which corrupted Markdown characters such as `>` and `&`. * Changed: the index now follows the llms.txt specification instead of robots.txt- style directives. * Changed: per-bot rules write to robots.txt, where crawlers read them. * Changed: the generator reads local posts instead of making an HTTP request per URL. * Fixed: works with plain permalinks and on subdirectory installs. #### 1.5.5 * Readme alignment and metadata updates. ## Meta * Versie **2.2.1** * Laatst geüpdatet **2 weken geleden** * Actieve installaties **10+** * WordPress versie ** 6.0 of nieuwer ** * Getest t/m **7.1.3** * PHP versie ** 7.4 of nieuwer ** * Taal * [English (US)](https://wordpress.org/plugins/msg-llms-txt-manager/) * Tags * [Agents](https://nl.wordpress.org/plugins/tags/agents/)[AI](https://nl.wordpress.org/plugins/tags/ai/) [crawlers](https://nl.wordpress.org/plugins/tags/crawlers/)[llms.txt](https://nl.wordpress.org/plugins/tags/llms-txt/) [markdown](https://nl.wordpress.org/plugins/tags/markdown/) * [Geavanceerde weergave](https://nl.wordpress.org/plugins/msg-llms-txt-manager/advanced/) ## Waarderingen Er zijn nog geen beoordelingen ingediend. [Je beoordeling](https://wordpress.org/support/plugin/msg-llms-txt-manager/reviews/#new-post) [Bekijk alle beoordelingen](https://wordpress.org/support/plugin/msg-llms-txt-manager/reviews/) ## Bijdragers * [ Hugo ](https://profiles.wordpress.org/cropllm/) ## Ondersteuning Iets te melden? Hulp nodig? [Het supportforum bekijken](https://wordpress.org/support/plugin/msg-llms-txt-manager/) ## Doneren Wil je de groei van deze plugin ondersteunen? [ Doneer aan deze plugin ](https://myseogrowth.com/donate)