| 开发者 | fmojibur |
|---|---|
| 更新时间 | 2026年9月17日 22:10 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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.
What makes this different
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.
One file per language
/llms.txt for the default language and /de/llms.txt, /bn/llms.txt and so on for the rest..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.
A curated list, not a URL dump
No plugin can promise that. What this one does is make your content machine readable and easy to locate in every language you publish in. Whether an AI system uses it is that system's decision.
WPML, Polylang and TranslatePress. On WPML and Polylang each language's own posts are queried. On TranslatePress, which keeps one set of posts, URLs are converted through TranslatePress and its saved translations are read for titles and descriptions.
It runs as an ordinary single language generator, with the curation, Markdown and crawler features intact.
No. The request is intercepted before WordPress routes it, so the files answer from the moment you activate the plugin.
No. Documents are generated on request and held in a transient cache whose lifetime you control.
Some plugins write a real llms.txt file into your site root. Your web server sends that file before WordPress starts, so no plugin can answer the URL while it exists. The settings screen detects this and names the file. Turn the llms.txt option off in that plugin, which removes the file. Deleting it by hand does not help, because the other plugin writes it again on its next run.
No. It reads their meta descriptions and respects their noindex settings, and its robots.txt lines survive alongside them.
It is built only when something requests it, and then cached. Keep the page and word budgets modest on shared hosting.
IP addresses are hashed with your site's own salt before being stored, and rows are deleted automatically after the retention period you choose. Logging can also be turned off entirely.