Pavlo Samsonov

Hi @corpconv

Thanks for the feedback! Just to confirm — is WP-Cron working correctly on your site?

In version 7.0+, LLMS.txt generation has moved to asynchronous cron-based indexing for performance reasons. After saving the settings, the system begins indexing the database and generating content in the background.

⏱️ It typically takes around 15–20 minutes (depending on your database size and cron configuration) before the .txt file appears and the indicator turns green.

If your site has cron disabled (DISABLE_WP_CRON), or if it’s hosted in an environment without real traffic (e.g., local/staging), the scheduled tasks might not run. In that case, you can trigger the process manually by visiting:

https://yoursite.com/wp-cron.php?doing_wp_cron

Let us know if that helps or if you’d like assistance confirming that cron jobs are executing properly!

Best regards,

LLMs Plugin Support Team

Hi @donbowman, thank you again for the valuable insights — you’re absolutely right.

We’ve implemented major improvements in version 7.0.0 to address the challenges in stateless and large-scale environments:

✅ The plugin no longer relies on real-time synchronous file writes.
✅ All generation is now handled via asynchronous cron jobs, minimizing any impact on frontend or admin experience.
✅ A dedicated llms_txt_cache database table is now used to index and store structured content before the file is created.
✅ Final export writes the file in chunks (500 records per batch) instead of appending each entry one-by-one, significantly reducing I/O operations and improving compatibility with stateless systems.

We did evaluate update_option()-based fallbacks, but they’re not suitable for large datasets — our DB-first caching model avoids memory and timeout issues while preserving performance.

Let us know if you run into anything else — we’re actively improving support for multi-instance and stateless environments in future updates.

Hi @csmarty

Thanks for reporting this. The issue you’re experiencing — “No LLMS.txt file found in root directory” — can sometimes occur if the file generation process was interrupted, especially on large databases. In earlier versions of the plugin, LLMS.txt was written synchronously and in a single request, which could be fragile on high-content or low-memory sites.

Starting from version 7.0.0, we’ve rebuilt the generation system to address this:

✅ A new database table indexes all LLMS content for better scalability

⚙️ The LLMS.txt file is now generated asynchronously via scheduled cron jobs

📉 We’ve significantly reduced filesystem operations to prevent timeouts and locking issues

If you’re seeing this message, we recommend triggering a regeneration from the plugin settings or simply waiting for the next scheduled cron event to complete the process. You should also ensure WP cron is working on your setup (wp cron event list if you’re using WP-CLI).

Let us know if the issue persists after updating to 7.0.0 — happy to help!

Thanks for reporting this, @slaffik — we’ve reviewed and updated the logic for retrieving the tagline in the latest version.

As of v6.1.2, the plugin retrieves the tagline using the following fallback order:

1. ✅ If the Yoast SEO plugin is active and configured, we pull the homepage meta description from Yoast settings.
2. 🛠️ If Yoast is not active or no meta description is found, we fall back to Settings → General → Tagline.
3. 🧩 If that is also empty, we fall back to the content of the static front page (if defined via Settings → Reading).

This should now correctly prioritize the intended homepage description and avoid pulling data from the blog/posts page.

Let us know if you still see any mismatches — happy to take a closer look.

Best regards,

LLMs Plugin Support Team

Hi @dgeihouse

Thanks for the detailed explanation.

This kind of issue can depend heavily on the specific server setup. On some servers, access to files in sub-directories from the root URL (like domain.com/llms.txt) can be restricted due to file system permissions or web server configuration. Another possibility is that the file is not being properly generated or routed when accessed from the root.

To diagnose this properly, we’d need to take a closer look at the server environment — including the .htaccess rules, file paths, and how the llms.txt is being handled in the sub-directory. Every server setup can behave a bit differently, so it really requires a case-by-case investigation.

If you’re able to provide temporary access or server details (even limited), that would help us quickly pinpoint the issue.

Best regards,

LLMs Plugin Support Team

Hi @csmarty

Yes, this plugin is actively maintained and supported.

If you encounter any issues or have specific questions regarding its functionality, please don’t hesitate to share the details — we’ll be glad to assist you.

Best regards,

LLMs Plugin Support Team

Hi @uttamgorain and thanks for your feedback!

The placeholder %%excerpt%% is a Yoast SEO variable that’s meant to be automatically replaced with your post’s excerpt. If you’re seeing it appear literally in the output, it means that the content hasn’t been parsed through the correct filter.

✅ Resolved in version 6.0.9: We’ve updated the plugin to automatically process Yoast SEO variables like %%excerpt%%, %%title%%, and %%sitename%%, so they now appear correctly in the generated output.

If you’re still seeing this issue, make sure you’re using version 6.0.9 or later and regenerate the content.

Let us know if the problem persists — we’re happy to help further!

Best regards,

LLMs Plugin Support Team