AI discovery
llms.txt for SaaS: useful file, realistic expectations
What an llms.txt file can communicate, what it cannot guarantee, and how to publish a concise version for a SaaS product.
An llms.txt file is a plain-text guide placed at the root of a website. Its purpose is to give compatible AI systems a compact description of the product and point them toward the most useful public pages.
It is not a switch for rankings or AI answers. Google has said its systems do not use llms.txt for AI Overviews or AI Mode. The file can still be a tidy machine-readable map for tools that choose to read it.
Write for retrieval, not promotion
Open with the product name and one factual sentence. Then list the pages that answer real questions: documentation, pricing, security, terms, contact, and the XML sitemap. Keep claims consistent with visible pages.
- Use stable canonical HTTPS links.
- State important limitations next to capabilities.
- Keep plan details on the pricing page if they change often.
- Avoid keyword lists, testimonials without sources, or hidden claims.
Keep the short file short
The root file should help a system choose what to read next. A separate llms-full.txt can hold a longer product summary, but it should still link back to canonical web pages rather than becoming a shadow version of the whole site.
Pair it with foundations that search engines use
A clean sitemap, crawlable pages, descriptive titles, useful body content, canonical URLs, and accurate structured data remain the practical foundation. llms.txt does not replace any of them.
If you want AI systems to understand a feature, explain that feature on a normal public page first. The machine-readable file should summarize and route, not introduce a different story.
Maintain it like documentation
Check the file during releases that change pricing, product names, public routes, or ownership. Broken links and stale plan claims make the file less trustworthy. A scanner can verify that the file exists and that its important links are reachable, but usefulness still depends on careful editing.
Primary source
Check your production site
See which of these issues are visible now.
ScanMySaaS checks the public surface and keeps the affected URL with every finding. Verify results before changing production.
Run a free scan