About this plugin
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. md to its URL. Mirrors are served with a noindex header so they never compete with your pages in search.
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.
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. 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. 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.