How to Set Up llms.txt for a SaaS Website

Why Does a SaaS Site Need llms.txt?

llms.txt is a text index of site materials that helps quickly find useful pages about a product. For SaaS, it typically includes a service description, use cases, documentation, pricing, and support information.

The file does not replace the site, sitemap, or documentation. Its purpose is to provide a compact overview and direct users to full sources. Therefore, you should start not by generating Markdown, but by asking: what materials need to be read to understand what the product does, who it is for, and how to use it?

Before preparation, gather:

• the main product page and key feature pages;
• current documentation and user guides;
• pricing, plan limits, and trial access terms, if published;
• security, integration, and support information;
• developer pages, if the service has an API.

For each material, use its permanent canonical URL. If you first want to understand the file's purpose and common questions around it, read the llms.txt guide.

Which URLs to Include in an Example llms.txt for SaaS

A good example llms.txt for SaaS contains not the maximum number of links, but a clear product route. Select pages that explain the service's value and answer practical buyer or user questions.

Divide materials into groups, for example:

• About the product: overview, features, industry use cases, and integrations.
• Usage: getting started, guides, help center, and troubleshooting common issues.
• Commercial information: pricing, plan comparison, and limit descriptions.
• Technical materials: API, requirements, security, and service status.

Do not add a page just because it exists. Exclude outdated documentation versions, duplicates, site search results, login pages, personal accounts, and materials requiring authentication. For similar pages, keep the main version, not a set of nearly identical links.

Manually verify relevance: the link title must accurately reflect the target page's content, and the page itself must be accessible to visitors. If pricing changes, point to the page with current terms, not a saved presentation. Such selection keeps the file compact and reduces the risk of directing readers to conflicting information.

How to Structure the File and Format Links

The llms.txt structure should be simple: a brief service description, then thematic headings and links with explanations. The file uses Markdown, so a plain text editor and verified URLs are sufficient.

Example foundation for a SaaS site:

# Product Name

> Brief description of the service and its main purpose.

## Product

• Product overview — /product: features and use cases.
• Integrations — /integrations: connected services.

Documentation

• Getting started — /docs/getting-started: account setup.
• API — /docs/api: technical documentation.

Pricing and Support

• Pricing — /pricing: plan details and terms.
• Support — /help: answers to user questions.

Replace example addresses with your site's actual URLs. The description under each link should help understand what is on the target page; do not turn it into a marketing slogan. Use consistent headings, clear names, and absolute links. Do not include secrets, personal data, or closed documentation content. Details on technical signals and site preparation are collected in the technical AEO material.

How to Add llms.txt to a Service Site

To add llms.txt to a service site, save the prepared Markdown as a plain text file and place it in the domain's root directory. The expected address is https://your-domain/llms.txt, not a URL inside the documentation section.

The publication method depends on the site setup. In a CMS, upload the file to the root via the standard file manager or ask a technical specialist to add it to the repository. For a site built from code, include the file in public static resources and verify the deployment configuration so the next build does not remove it.

After publication, run a quick check:

• open the address in a browser without logging in;
• ensure the server returns the file content, not an error page or HTML site wrapper;
• verify all links lead to the intended pages and do not require authentication;
• open the file from a mobile device or in a private window to rule out session influence.

Then incorporate publication into the regular site release process. This keeps the file in place when the theme, CMS, or documentation structure changes.

How to Maintain the File After Publication

After publishing llms.txt, maintain it in line with product and site changes. Assign an owner—for example, a documentation editor or site specialist—and add link verification to the process of updating important pages.

A practical workflow: the page owner reports a URL or content change; the file owner checks whether the link or description needs updating; after the update, open the file at the public address and review the affected sections. It is also useful to store the source file in the same repository or workspace where documentation is maintained.

During checks, focus on three things: links open, labels match current content, and sections do not contradict each other. If the product renames a feature or changes pricing, update not only the page but also the brief description in the file. Do not add unverified promises about service capabilities.

For SaaS, where evaluating presence in AI-based search system responses is important, llms.txt should be considered part of a broader effort, not a standalone switch. Practical directions for such a business are described in the AI visibility for SaaS section.

What Limitations to Consider and What to Do Next

llms.txt simplifies navigation through selected materials but does not control how third-party systems crawl the site or use its content. The file's presence does not guarantee that a specific model will read it, cite a page, or change its perception of the product; the platforms themselves control crawling, indexing, and response generation rules. Therefore, promising site appearance in responses solely through file publication is not possible.

A practical quality criterion is not the number of links but the accuracy of the route. Ask a colleague who did not create the file to find answers to questions: what does the product do, where are the guides, what are the pricing terms, and where to study the API. If the needed page is hard to find or the description is misleading, restructure the sections.

For the next step:

• cross-check URLs in the file with the site's navigation and canonical addresses;
• align product descriptions with documentation and pricing owners;
• verify public access after each significant release;
• consider a technical audit if you need to align the file with other site elements.

If you need help not only with llms.txt but also with SaaS visibility in AI responses, explore AI visibility services and technical AEO.