JumpsuitAI – llms.txt + Markdown Endpoints

We have a vacation rental website and were manually creating our llms.txt file. This was working perfectly until Google implemented Agentic Browsing in their default Lighthouse configuration. At that point, we needed the llms.txt file to be compliant with specifications (i.e., actually follow the rules), not simply exist.I installed Jumpsuit AI, selected which pages and post types to include, and ran PageSpeed Insights immediately afterward. All three relevant tests passed: Accessibility Tree Well Formed, CLS = 0.001, and llms.txt received no flags other than “recommendations.”The biggest advantage to me was that nothing else on the site was touched to achieve this. The .md endpoint works seamlessly as well. If you’re looking for a very lightweight version of your pages for any service that does support markdown but isn’t capable of rendering full HTML, it’s another great feature.The settings page is simple; the per-page “Hide from LLMs” toggle provides the level of granularity I wanted, rather than a yes/no option.If you’ve already taken care of keeping CLS low and your markup semantically correct, this plugin will complete the necessary requirements to pass Agentic Browsing.

This is lightweight and does a great job for our Agency to create all the files we need. Best solution we’ve found.