Project LLMs.txt

Časté otázky

What is llms.txt?

llms.txt is an emerging open standard – think robots.txt for AI. It’s a clean, structured Markdown file placed at the root of your site (yourdomain.com/llms.txt) that gives AI assistants and agents a reliable, structured entry point into your content. See llmstxt.org for the full spec.

Do AI assistants actually use it?

No major search engine or LLM provider has officially announced that they seek out llms.txt files. But that’s not the whole picture.

Markdown is the format AI reads best, and this plugin converts your entire site into exactly that. When any AI tool – a browsing agent, a coding assistant, an AI-powered search product – visits your site and finds a clean /llms.txt, it gets a structured index of everything on your site in one fetch, already in the format it reads most cleanly. It doesn’t have to fight through navigation, ads, or page-builder markup to understand what your site is about. That’s a real advantage regardless of whether the tool came looking for the file or just happened to land on your domain.

What actively uses it today: AI agents, coding assistants, MCP servers, and developer-facing AI products. Companies like Stripe, Vercel, Cloudflare, and Anthropic already publish their own llms.txt files for this reason.

Publishing now costs nothing and keeps your site ready as the ecosystem matures.

Does this work with Elementor / Divi / Visual Composer?

Yes. By default the plugin reads your published content, which covers shortcode-based builders like Divi (classic) and Visual Composer, whose layouts expand through WordPress’s normal content filters.

For builders or theme sections that render their layout outside the editor (for example Elementor, which stores its layout separately and renders it through a hook), switch Extraction Method to Full-page scrape under Settings → Content Extraction. That loads each page the way a browser does and keeps just the main content.

If automatic content detection grabs the wrong zone, you can also set a custom CSS selector in the same place (e.g., .site-content, main article, #content).

Does it support WooCommerce?

Yes, WooCommerce products are a first-class content type. Product files include: name, SKU, price (regular + sale), stock status, short description, full description, categories, tags, dimensions/weight, product variations with pricing, customer reviews, and upsell/related products.

Does it respect my SEO noindex settings?

Yes. If a page is set to noindex or nofollow in Yoast, Rank Math, SEOPress, AIOSEO, or Slim SEO, it is left out of your llms.txt files automatically. Pages you keep out of search stay out of AI, with no extra configuration. Developers can extend the check with the llmstxt_seo_noindex_check filter.

Does it keep up with bulk imports?

Yes, with a little code. The plugin exposes regeneration action hooks (such as llmstxt_regenerate) that any plugin or script can fire. We document a WP All Import example using pmxi_after_xml_import, so your llms.txt rebuilds after a bulk import, migration, or programmatic update.

Where are the files written?

By default, files are written to your WordPress root directory – the same folder as wp-config.php. They’ll be accessible at yourdomain.com/llms.txt and yourdomain.com/llms-full.txt.

If your host doesn’t allow writes to the root directory, switch to Live Endpoint mode in Settings. This serves the files dynamically via WordPress rewrite rules with no filesystem writes.

Will this affect my site’s performance?

For your visitors, no. The generated files are static and served directly by your web server, with no PHP execution per request.

Generation itself does real work: it runs on-demand when you click Generate (in batches, so it stays within PHP time limits), and for Pro users auto-regeneration runs in the background via WP Cron. On very large sites a full regeneration can take a little while, which is why auto-regeneration is debounced and scoped: routine edits re-render only the posts that changed rather than the whole site.

Is my content sent anywhere?

No. All processing happens on your own server. The plugin does not send your content to any external API or service. It only reads your existing published content and writes .txt / .md files to disk.

Can I exclude specific pages?

Yes. In Settings → Content to Include, check any pages you want left out of the AI files. When WooCommerce is active, its Cart, Checkout, and My Account pages are excluded automatically – they’re checkout mechanics with no value to AI assistants. Developers can adjust the final list with the llmstxt_exclude_ids filter.

Does it work with multisite?

Single-site only for now. Multisite support is on the roadmap.

How often should I regenerate?

With the free version, regenerate manually after significant content updates. With Pro, auto-regeneration handles this for you – files update automatically within about a minute of any publish event.

Can I customize the Markdown output?

Free: No. The default templates produce clean, well-structured Markdown out of the box, and you can preview the generated Markdown for any page, but customizing it requires Pro.
Pro: Full template editor with per-content-type templates, plus per-page overrides to hand-edit any page’s output and field mapping to pull ACF and custom meta into your files. Use {{variable}} tokens (e.g., {{title}}, {{price}}, {{content}}) and conditional blocks {{#variable}}...{{/variable}}.

My site root isn’t writable – what do I do?

Switch to Live Endpoint mode in Settings → File Serving Mode. The files will be served dynamically via WordPress. Alternatively, contact your host or adjust directory permissions to allow PHP writes to your root.