Generate an llms.txt file for your site
On this page
llms.txt is a typical method for giving AI tools and large language models (LLMs) structured, plain text context about your site. This is similar to how robots.txt gives instructions to search engine crawlers. Learn more about llms.txt.
:::note
Serving llms.txt requires StoreConnect website v21 or later.
:::
Unlike robots.txt, StoreConnect does not auto-generate an llms.txt file for you. You need to create and maintain it yourself using a content page.
How llms.txt works
llms.txt is served through the same mechanism as any other alternate content type on a content page: a Page record with a file extension in its Path field. There is no dedicated llms.txt feature or setting, you have full control over the file’s content and when it changes.
llms.txt format and content
You can use any number of AI tools to generate a basic llms.txt for your site. The output will look something like this:
```markdown
[Your Store Name]
[Your Store Name] is a premium online retailer specializing in [Niche], offering high-quality [Product Category] with fast, worldwide shipping and easy returns.
Core Categories
Customer Care
Featured Products
- Premium Leather Jacket - $299.00
- Handcrafted Ceramic Mug - $24.00 ```
Create your llms.txt file
- In Salesforce, create a new Page record on the store.
- Set the Path field to
llms.txt(no leading/). - Replace the default
{{ content_page | render_content_blocks }}snippet in the Content Body field with your llms.txt content. - Save the record.
To update the llms.txt later, update the content body in this record.
The file appears at https://your-store.com/llms.txt as plain text, without the header, footer, or theme wrapper.
Writing dynamic content
The Content Body field is rendered through Liquid, so llms.txt content can be generated dynamically — for example, listing current product categories or pulling values from store variables — instead of maintaining a fully static file.
Remove llms.txt
Delete the Page record with Path llms.txt, or clear its Content Body. Removing the page means requests to llms.txt return a 404 — there is no auto-generated fallback.
llms.txt and stealth mode
llms.txt and Stealth mode work in opposite directions: llms.txt gives AI tools content to read, while stealth mode tells crawlers to stay away.
Enabling stealth mode does not take your llms.txt page offline. Stealth mode only suppresses robots.txt, the sitemap, and merchant feeds — a custom llms.txt content page is not on that list, so anyone who requests the URL directly still receives the file. What changes is that compliant crawlers no longer read or index it:
- Stealth mode’s robots.txt returns
Disallow: /, which instructs compliant crawlers not to request any path on the store, including/llms.txt. - Every response from the store, including
/llms.txt, carries anX-Robots-Tag: noindex, nofollowheader, which instructs compliant crawlers not to index the content.
In short, stealth mode leaves the file readable but tells well-behaved AI crawlers not to fetch or index it. If your goal is to block AI crawlers from your store, use stealth mode. An llms.txt file cannot do this — it provides information to AI tools, it does not control their access.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.