Forum Replies Created

Viewing 15 replies - 31 through 45 (of 115 total)
  • Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @turpin @drzivil @rocketmartue ,

    Thank you for your feedback!

    We’ve identified the cause of the 404 issue when using llms-sitemap.xml with Yoast SEO. This has been fully resolved in version 8.1.0 of the plugin.

    Please update to the latest release and re-save your permalinks under Settings → Permalinks to refresh rewrite rules. The sitemap should now be accessible without returning a 404 error.

    Let us know if you experience any further issues after updating.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @danielcyclr

    Sure, you can reach me at samsonov.teamwork@gmail.com. Please feel free to share the development site details there.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @vgaran,

    Thanks for reporting this issue.

    We’ve identified the bug where llms.txt was generating duplicated URLs with the same language code for all translations when using WPML.

    This has now been fixed in version 8.0.9 – each language version will correctly generate its own URLs in the llms.txt file. Please update to the latest release and re-generate the file to apply the fix.

    Let us know if the issue persists after updating.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @garrigan

    This behavior is possible because some server configurations don’t allow the plugin to create a physical llms.txt file in the site root.

    When that happens, visiting https://[site-domain]/llms.txt triggers a redirect to https://[site-domain]/llms.txt/, where the plugin dynamically serves the file content.

    So this redirect and final 200 OK response is expected behavior when there is no physical file in the root directory.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @anitaign

    We do generate separate llms.txt files for each site within a Multisite installation.

    You can find these files in the /wp-content/uploads/ directory – they follow the format:

    [site-domain].llms.txt

    When you access https://[site-domain]/llms.txt, the plugin automatically serves the corresponding file for that site.

    If you have any questions or run into issues with this setup, feel free to let me know.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @mazursv

    Thank you for the detailed report. With such a large database size (50k+ products), processing everything in one go can easily exceed PHP memory limits, even with optimized code. To properly handle this, I’d need access to your codebase and database to test a chunked processing approach or alternative cron-based execution.

    This would help identify bottlenecks, test batch sizes, and implement a solution that can handle your data volume without hitting memory errors.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @iidazero

    Thank you for the detailed report. Based on the description, the issue seems to be related to the large database size and the substantial amount of content per post. To properly analyze and resolve this for such large-scale data, I would need access to your codebase and a copy of your database.

    This would allow me to:

    • Identify where the generation process is failing
    • Optimize or adjust the generation logic for high-volume content
    • Test and validate a fallback mechanism if necessary

    If providing full access isn’t possible, a staging environment replicating your setup would also help me investigate the problem more effectively.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @ooya

    Thank you for reporting this issue. Based on the information provided, it’s difficult to determine the exact cause. I haven’t encountered this behavior on multiple other sites using the plugin, so it could be related to:

    • The specific plugin version you’re using
    • Your server configuration
    • A conflict with another plugin, theme, or custom code on your site

    To investigate further, I may need:

    • Details about your plugin and WordPress version
    • Access to a staging site where the problem can be reproduced

    Once I have this information, I can check for conflicts and help identify a fix.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @birdmarketing

    I have tested this on a staging site with WPML and a properly configured multilingual setup. The llms.txt file generates links for all available language versions.

    If you enable the following checkboxes in the settings:
    • Include meta information (publish date, author, etc.)
    • Include post excerpts / meta descriptions
    • Include detailed content
    • Include taxonomies (categories, tags, etc.)

    …the content is displayed for each language-specific link.

    If the issue persists on your site, I may need temporary access to review your WPML configuration and resolve the problem directly.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @brandongrm,

    I believe it would be best to share a quick instruction on how to properly use this feature:

    1️⃣ When you enable the checkbox “Turn on options at the page level admin with .md support and ability to not include individual pages” in the plugin settings, it activates a sidebar (see screenshot: https://snipboard.io/RI35r4.jpg) on each page and post editor.

    This sidebar allows you to:

    • Exclude a specific page from the llms.txt file.
    • Upload an additional Markdown (.md) file for this page/post, which will serve as extra descriptive information for AI crawler detection.

    2️⃣ After you upload the .md file, you must save/update the post. Once the page reloads, you should see a link to the uploaded file (highlighted in red in the screenshot above). From there, you can also delete the file if needed.

    3️⃣ If you check the option “Do not include this page in llms.txt”, then that specific post (example screenshot: https://snipboard.io/UBNCSm.jpg) will not be included in the final llms.txt file.

    Please try these steps and let me know if the functionality works as expected on your side.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @danielcyclr , thanks for the kind words and detailed feedback!

    ACF support is definitely something we’re interested in adding — and your use case helps confirm that it’s important.

    To implement this properly, I’ll need access to your site or a full backup (staging is fine). That way I can test and validate how your ACF-based content is structured and pulled into the front end.

    My plan is to implement a solution where either:
    • a button lets you manually pull in the rendered content from the page (ideal for bespoke templates), or
    • a checkbox enables content fetching via frontend request (useful for pages relying entirely on ACF blocks).

    Let me know if you’re open to sharing access or a copy — that would speed things up significantly.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @m_scud ,

    Thanks for your report!

    In the latest version of the plugin, we no longer trigger cache clearing when the LLMS file is regenerated via cron or during regular content updates. This change was made specifically to avoid unnecessary full-site cache purges in production environments.

    Please update to the most recent version of the plugin and let us know if the issue still persists.

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @mykytawdm ! Thanks for your feedback.

    This issue has been resolved in version 8.0.8 of the plugin.

    Dynamic tags from Rank Math (such as %title%, %customterm()%, etc.) are now correctly rendered inside the llms.txt file titles and descriptions for all post types.

    Please update to the latest version and let us know if everything works as expected.

    Thanks again for reporting this!

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @torao9340

    Thanks for the follow-up.

    Unfortunately, I haven’t been able to reproduce the issue on my end.

    To help troubleshoot and fix this properly, would it be possible for you to:

    • Provide access to a development/staging copy of the site where the issue occurs, or
    • Send a backup or duplicate of the site so I can investigate in a controlled environment.

    This will allow me to isolate the problem in combination with your theme/plugins and provide a targeted fix.

    Looking forward to your reply!

    Best regards,

    LLMs Plugin Support Team

    Plugin Author Pavlo Samsonov

    (@samsonovteamwork)

    Hi @alexclassroom

    Thanks for pointing this out, Alex!

    We’ve updated the string in class-llms-md.php on line 89 to use esc_html_e() with the correct text domain website-llms-txt, so it’s now fully translatable. This fix is included in version 8.0.7.

    Appreciate your attention to detail! 🙌

    Best regards,

    LLMs Plugin Support Team

Viewing 15 replies - 31 through 45 (of 115 total)