Pavlo Samsonov

Hi @gooloode,

Thanks for your message — I understand the confusion here.

The file is not stored inside the plugin directory, which is why you don’t see it in the usual places. It’s generated dynamically and saved in your WordPress uploads directory, and then copied to the site root. Where the file is actually located

The plugin creates the file in:

/wp-content/uploads/{your-domain}.llms.txt

For example:

/wp-content/uploads/example.com.llms.txt

It also creates a temporary file during generation:

/wp-content/uploads/{your-domain}.temp.llms.txt

Public file (what you’re seeing)

After generation, the file is copied to your site root:

/llms.txt

So even after uninstall, this file may still exist at:

https://yoursite.com/llms.txt

Why you still see it after uninstall

Because:

• The plugin writes a physical file to the server
• WordPress does not automatically delete files on uninstall
• CDN/cache won’t affect this — it’s a real file

How to remove it manually

Please delete these files:

1. Root file (most important):

/public_html/llms.txt

2. Uploads files:

/wp-content/uploads/{your-domain}.llms.txt
/wp-content/uploads/{your-domain}.temp.llms.txt

Why you didn’t see it in cPanel

Most likely you were looking in:

• /wp-content/plugins/

But the file is in:

• /public_html/ (root)
• /wp-content/uploads/

If you still can’t find it, let me know your hosting setup and I’ll point you to the exact path

Best regards,
LLMs Plugin Support Team

Hi @hchouhan ,

Yes — the plugin already provides built-in support for adding fully custom content to the generated llms.txt file.

In the Custom LLMS.txt Content section you can define:

• LLMS.txt Title – custom heading shown at the very top of the file
• LLMS.txt Description – introductory text before any URLs
• LLMS.txt After Description – additional notes or context inserted right before the URL list
• LLMS.txt End File Description – footer text appended at the bottom of the file

This allows you to add custom headings, explanations, disclaimers, contact information, or any other manual content alongside the automatically generated URLs — without modifying the file manually.

So all required custom text and structure can be configured directly from the plugin settings.

Hope this helps 👍

Best regards,

LLMs Plugin Support Team

Hi @ericknwwd , thanks for reporting this.

Could you please check the plugin debug log and let me know if there are any errors there when the generation fails? That would help a lot.

Also, could you share:

• Which hosting/server you are using (e.g. shared hosting, VPS, Cloudways, WP Engine, etc.)
• Your PHP version
• WordPress version
• Plugin version
• Whether WP_DEBUG is enabled

The more details you can provide, the faster I can identify what’s causing the “Request Failed” issue.

Thanks!

Best regards,
LLMs Plugin Support Team

Hey @esekaweb 👋

If your site is using a multilingual plugin such as Polylang, the plugin automatically manages translations for each post or page — for example, like this:
🔗 https://snipboard.io/2GDBN6.jpg

When the LLMs.txt file is generated, it includes all available links across the site — for all translated posts and pages that exist in your Polylang setup.
Here’s what that looks like:
🔗 https://snipboard.io/wz5hgm.jpg

So there’s no duplication — the crawler reading your LLMs.txt file will see every valid URL from all active languages (or from the specific post types you’ve chosen).

In other words, you don’t need to create separate .md files per language — the crawler automatically detects all accessible posts and pages across translations.

Best regards,

LLMs Plugin Support Team

Hi @afijadior,

Thank you for the update and for testing version 8.2.1.

I’ve now completely reworked the way this text is rendered in the “AI Crawler Detection” column — instead of using printf with placeholders, the output is now split into multiple translation strings, which prevents the ArgumentCountError in all environments and configurations.

This fully avoids the fatal error — even on setups where translation or string formatting behaves differently.

Please update to the latest version and let me know if everything works as expected on your end.

Best regards,

LLMs Plugin Support Team

Hi @sayingitfirst

Thanks for the update!

Could you please confirm whether you’re using the filter

apply_filters('llms_generator_get_post_meta_description', false, $post)

This filter allows you to output custom content above the detailed page description.

Also, have you tried regenerating the file using the “Delete and Recreate” button in the LLMs.txt Reset section on the plugin settings page?

This ensures that cached data is cleared and the latest content is included.

Best regards,

LLMs Plugin Support Team

Hi @wsteindl,

Thanks for your feedback — this has been addressed in version 8.2.0.

In this update, we’ve improved how the Custom LLMs.txt Text fields are handled and documented.

Each section (Title, Description, After Description, End File Description) is now clearly defined and generated in the correct position within the llms.txt file.

Additionally, we introduced a new LLMs.txt Reset feature in the settings panel. It allows you to safely delete outdated or duplicate files and rebuild a fresh version automatically — no manual removal required.

Please update to v8.2.0 and regenerate your file — the custom text should now appear as expected.

Best regards,

LLMs Plugin Support Team

Hi @m2sistemiweb

Due to the fact that this file can sometimes become quite large, the browser will not be able to handle it reliably. For that reason, the best option is to use FTP access: download the file, edit it locally, and then upload it back.

Making this universally editable directly from the plugin would not be practical, since some servers also do not allow creating or modifying this file in the root directory.

Best regards,

LLMs Plugin Support Team