How should we actually audit llms.txt? I built a Chrome extension to find out
I’ve been playing with llms.txt audits for a while and ended up building a Chrome extension around it: LLMs.txt Compliance Inspector v1.2.
Important disclaimer before anyone reaches for the pitchforks: I’m not claiming llms.txt improves rankings or AI citations. The evidence for that is weak at best right now.
What interested me was a different problem: if people are going to create these files anyway, how do we evaluate whether they’re actually well structured and useful?
Most checkers I found basically answer:
“Does /llms.txt exist? ✅”
I wanted something closer to a technical audit.
It checks llms.txt and llms-full.txt, structure, links, missing sections, technical issues and recommendations.
I also deliberately treat different sites differently. A Shopify store, WooCommerce store, blog, SaaS/API documentation site and corporate website shouldn’t necessarily get the same checklist.
This is still very much my interpretation of an emerging convention, which is exactly why I’d like TechSEO people to break it.
Chrome extension:
https://chromewebstore.google.com/detail/llmstxt-compliance-inspec/kobabmaojpooanphhogepogipcnajcao
I’m particularly interested in:
• checks you think are bullshit
• checks I’m missing
• things that should be warnings rather than errors
• whether site-type-specific auditing makes sense at all
Roast away 😄