Hello @rfischmann,
Thanks for reaching out about the llms.txtfile feature. Since the llms.txt file generates correctly after regeneration and the issue returns later, this usually points to an intermittent server or caching issue rather than a problem with the file generation itself.
We recommend checking whether /llms.txt remains publicly accessible when the warning appears, and excluding it from any caching, CDN, firewall, or security rules that may temporarily block or alter access to the file.
Yeah, just checked again and the file hasn’t been updated since I opened this ticket — when I deleted it, turned the feature off and back on in Yoast SEO. It was generated correctly, but it’s been frozen since then. The warning hasn’t reappeared it, but I believe it will soon.
The file is publicly accessible, yes. It’s not cached and I don’t see any firewall/security rules blocking it or anything.
Do you want me to run any specific tests?
Thanks for checking. Since the file is accessible and remains in place, the next useful step would be to wait until the warning appears again and then check whether there are any related errors in:
- WordPress > Tools > Site Health
- your server/PHP error logs
- browser DevTools network response for
/llms.txt
It would also help to know:
- whether the warning appears after a specific event (plugin update, cache purge, cron run, etc.)
- whether object caching or server-level caching is enabled
At the moment, there’s no indication that the file generation itself is failing.
Yeah, but as I said, the file has remained stale since it was generated almost a week ago. Shouldn’t it be updated regularly, especially considering it lists only 5 posts (besides categories and tags)?
For now, the warning hasn’t reappeared in Site Health.
The only local caching I have is Redis’ Object Cache.
This file is updated weekly by a scheduled action. Disabling for a few minutes and re-enabling the feature also forces a refresh of the content is something has changed.
I didn’t know it was only once a week. Well, it was generated on May 8th, so I believe in 3 days it will try to update it, will fail and the warning will show up in Site Health. I’ll keep my eyes on it. Thanks.
