

Every language's file listed on the settings screen, with the translation plugin that was detected.
If your site is multilingual, AI assistants are probably only reading one of your languages.
Assistants such as ChatGPT, Claude, Perplexity and Gemini look for a plain text file called llms.txt at the root of a site to learn what it is about and which pages matter. On a WPML, Polylang or TranslatePress site, the file that gets produced describes your default language only. Every page you paid a translator for stays out of it.
This plugin is built around that one problem. It produces a separate file for each published language, cross links them, and points each entry at the correct translated URL.
The author surveyed the plugins in this directory that generate llms.txt files. They generate a single file from the default language. None of them read WPML, Polylang or TranslatePress and none of them produce a per language file. This plugin exists to close that specific gap, and everything in it is shaped by that goal rather than by generating one more copy of the same file.
/llms.txt for the default language and /de/llms.txt, /bn/llms.txt and so on for the rest.Files are generated when they are requested. The plugin never writes to your web root, never needs write permission there, and never asks you to re-save your permalinks. Activate it and the file answers immediately, on plain permalinks as well as pretty ones, in a subdirectory install, and on multisite.
Add .md to any page URL to get a clean Markdown version of it. Page builder wrappers, inline styles and scripts are removed, so a model reads your writing rather than your CSS. Optionally serve llms-full.txt, which embeds the page text, with page and word budgets so it stays sensible on shared hosting.
An optional log records visits from GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended and a dozen more, and shows which language each one asked for. Visitor IP addresses are hashed before they are stored and old rows are removed on a schedule you choose.
Allow or block each AI crawler from one table, and list every language’s file at the end of robots.txt. The lines survive even when another SEO plugin rebuilds robots.txt.
The plugin makes no external requests, sends no data anywhere, contains no tracking and loads no third party scripts. Everything it stores stays in your own database.