Auto-generated llms.txt fails Markdown link format (PageSpeed Insights audit failure)
Hi Brizy team,
My site (choosepack.com) runs on Brizy Cloud PRO. I've noticed that Brizy automatically generates /llms.txt and /llms-full.txt for every project, which is a great feature. However, the auto-generated /llms.txt file is failing Google PageSpeed Insights' "Agentic Browsing" audit with the error: "File does not appear to contain any links."
The issue: The native file lists page URLs as plain text (one per line), but the llms.txt standard (llmstxt.org) requires a Markdown file with an H1 header and proper Markdown-formatted links, e.g.:
- [Page Title](https://example.com/page): short description
Because the current output doesn't use this link syntax, it's flagged as non-compliant by automated auditors, even though the URLs themselves are correct.
I also tried working around this by setting up a custom redirect from /llms.txt to an external, spec-compliant file (hosted on Cloudflare), but the redirect never takes effect — Brizy's native auto-generated file always takes priority at that path, even on the PRO plan.
Two questions:
- Is it possible to manually edit or override the content of the auto-generated
/llms.txtfile anywhere in the project settings? - If not, could
/llms.txtbe made a non-reserved path so it can be redirected to an external, spec-compliant file?
Either fix would resolve the audit failure. Happy to provide the PageSpeed Insights report or any other details if useful.
screenshot link PageSpeed Insights:
https://drive.google.com/file/d/1_LMxzpU3mpm5ImKZA3_AmvI85KF95HtU/view
Thanks for your help,
Mr TB
My site: choosepack.com
-
yes it's very annoying, just as the automated schema which is very basic but adds to the one we can create manually. Plese start thinking modern SEO. You are far behind everything on the market now. This should not be a very difficult task to allow us to add manual text for llms, scchema and OKF
0 -
Hi Touhami,
Thank you for taking the time to share your detailed feedback.
Our llms.txt functionality is still under development and has not been officially launched yet. This is why the currently generated files may not fully follow the expected format or support manual overrides.
The feature should be rolled out soon. We appreciate you highlighting the formatting issue, and we will pass your concerns on to our team for review.
Kind regards,
Ariel H.0 -
even if it's not official, Google already reads it and it messes with our SEO as the schema function
0 -
Hi Jean-Pierre,
We understand your concern, especially since Google may already be reading the file and it could potentially affect your SEO.
We have already raised this with our developers. We will share any updates once we receive further information.
Kind regards,
Ariel H.0
Please sign in to leave a comment.
Comments
4 comments