by
Hugo
1 (0 reviews)
MSG LLMs TXT Manager
Serve your content as clean Markdown to AI agents, publish llms.txt and llms-full.txt, and see which agents actually fetch what.
MSG LLMs TXT Manager ranks #30,752 among WordPress.org plugins with 10+ active installations, is #1,371 of 4,265 in the SEO & Marketing category, a 1/5 rating from 0 reviews, and was last updated Sep 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v2.2.1
Current Version v2.2.1
Updated 1 month ago
Last Update on 28 Sep, 2026
Refreshed 1 week ago
Last Refreshed on
#1,371 of 4,265 in SEO & Marketing
Top 50% by installs
Downloads -30.8% this week
Rank
#30,752
—
No change
Active Installs
10+
—
No change
KW Avg Position
171.5
—
No change
Downloads
1.1K
+7 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 20
10+
20+
7,579
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 2 more installs to reach 20+
Rank Changes
Current
#30,752
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 2.2.1
- Last Updated
- Sep 28, 2026
- Requires WP
- 6.0+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Hugo
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Yoast SEO – Advanced SEO with real-time guidance and built-in AI
10M+ installs
#2
Rank Math SEO – AI SEO Tools to Dominate SEO Rankings
4M+ installs
#13
Redirection
2M+ installs
#21
All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)
2M+ installs
#22
MC4WP: Mailchimp for WordPress
1M+ installs
#35
Hostinger Reach – AI-Powered Email Marketing for WordPress
1M+ installs
#41
XML Sitemap Generator for Google
1M+ installs
#56
EWWW Image Optimizer
1M+ installs
#60
Frequently Asked Questions
Common questions about MSG LLMs TXT Manager
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.
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.
No. Every mirror is sent with an X-Robots-Tag: noindex, nofollow header, so search engines will not index them.
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.
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.
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.
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.
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.
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.
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.
