Pavlo Samsonov

Hi @designsonline, thank you for your thoughtful feedback and for using the plugin!

In the current version of the plugin, there is already support for page/post-level control.
When you enable the option:
“Turn on options at the page level admin with .md support and ability to not include individual pages”,
you’ll see a meta box (on each page/post edit screen) called Llms.txt.

Inside that meta box there is a checkbox:
✅ Do not include this page in llms.txt
When checked, the page/post will not appear in the llms.txt file.
When unchecked, the page/post will appear (assuming the post type is enabled in the general plugin settings).

So, by default, all enabled post types are included in llms.txt, but you can use this checkbox to exclude individual posts/pages you don’t want in the file.

We understand your suggestion about inverting the logic — selecting only the specific posts to include rather than including everything by default — and this is a good idea for a future improvement. We’ll explore adding an “only include checked” mode in a future release.

Thanks again for your suggestion and for helping improve the plugin!

Best regards,

LLMs Plugin Support Team

Hi @alexclassroom

Thanks for pointing this out!

We’ve fixed the i18n issue in class-llms-md.php (line 21) by properly wrapping the meta box title in __() with the correct text domain.

This fix is included in version 8.0.4, which also addresses several PHP warnings and improves default value handling. Please update to the latest version and let us know if you spot anything else.

Thanks again for contributing!

Best regards,

LLMs Plugin Support Team

Hi @slaffik

Thanks for reporting this!

We’ve confirmed that the PHP warning about “Undefined array key ‘llms_allow_indexing’” has already been fixed in version 7.1.6, where a proper check and a default value were added.

Please update to the latest version of the plugin and check — the warning should no longer appear.

If you still see anything similar after updating, let us know and we’ll help.

Thanks again for your feedback!

Best regards,

LLMs Plugin Support Team

Hi @veerap,

Thank you for pointing this out and providing a detailed report!
✅ This issue with the add_submenu_page() 7th parameter (where an icon string was mistakenly passed instead of a numeric position) has already been fixed in version 7.1.5 of the plugin.

We now correctly pass an integer to comply with the WordPress documentation you linked — and the PHP notice no longer occurs even with WP_DEBUG enabled.

If you update to the latest release, this problem should be resolved. Please let us know if you notice anything else.

Thanks again for helping improve the plugin!

Best regards,

LLMs Plugin Support Team

Hi @tunjic,

Thanks for pointing this out — that’s a great observation.

Indeed, Yoast SEO has recently added support for generating an llms.txt file (link).

It would be valuable to review how the Yoast implementation compares with ours in terms of flexibility, configurability, and how it integrates with existing workflows.

From what we can already note:

• Yoast’s llms.txt feature is bundled into their SEO suite and is enabled alongside other SEO-related settings.
• Our plugin focuses exclusively on llms.txt generation and tracking, with optional bot visit logging and global experiment participation — which is not part of Yoast’s feature set.
• We also offer more granular controls and visibility into which bots are accessing the file, which Yoast currently does not provide.

We’ll definitely explore this further and document how the two solutions complement or differ, so users can choose the best fit for their needs — or even use them together if appropriate.

Thank you for bringing this up!

Best regards,

LLMs Plugin Support Team

Hi @pontikis,

Thank you for your feedback and for testing the plugin thoroughly.

You are correct — the checkbox in the plugin settings can control the response headers only when the request to llms.txt is routed through WordPress/PHP (e.g., a dynamic URL like https://medisign.gr/llms.txt handled via a rewrite rule).

However, if there is a physical llms.txt file on the server, the web server (Apache, Nginx, etc.) will serve that file directly, bypassing PHP entirely. In this case, WordPress cannot set the X-Robots-Tag header because it never sees the request.

Unfortunately, due to differences in server configurations and how static files are served, adding the header for a real file requires manual action by the site owner (such as adding the .htaccess snippet you shared, or configuring it in the Nginx config).

So the checkbox works for dynamically-generated llms.txt but cannot affect a static file served directly by the server — this is expected behavior.

We’ll consider clarifying this in the plugin’s documentation so it’s clear what the checkbox covers.

Thanks again for bringing this up and for your suggestion!

Best regards,

LLMs Plugin Support Team

Hi @gnissley,

Thanks for reaching out and for providing the details!

The LLMS plugin automatically generates the llms.txt file in your site’s WordPress root directory (ABSPATH) the first time it runs its generator cron task. If you see the message “No LLMS.txt file found in root directory”, here are some steps you can take to resolve it:

✅ Make sure the scheduled task has run at least once. You can trigger it manually by running:

wp cron event run llms_update_llms_file_cron --url=your-site-url

or, if you don’t have WP-CLI access, simply wait for the WordPress cron to fire or save/update any post to trigger it if your settings are immediate.

✅ Ensure the web server has write permissions to the WordPress root directory. The plugin needs to write the llms.txt file next to wp-config.php. If permissions are too strict, it won’t succeed. You can chmod or adjust permissions temporarily to test.

✅ You don’t need to manually create the file — the plugin overwrites it with fresh content every time. If you did create one, make sure it’s writable and owned by the same user WordPress runs under.

✅ Check your site’s error logs (or enable WP_DEBUG_LOG) to see if the plugin logs any PHP errors when it attempts to write the file.

If none of the above helps, please let us know your:

• WordPress version
• LLMS plugin version
• Any relevant errors from the log
• If possible, whether it works when running wp cron event run manually.

We’re here to help and can guide you through a deeper investigation if needed.

Best regards,

LLMS Plugin Support Team