The llms.txt file: what it is and whether your online store needs it

The llms.txt file is a plain text file in Markdown format that you place in the root directory of your website. It gives language models a short description of the site and links to its most important content. Does an online store have to have one? No. It is optional, because this is a proposal from September 2024, not an adopted standard. Below I explain what the file is, how it differs from robots.txt and sitemap.xml, when it makes sense and how to prepare it.

What is llms.txt and where did it come from?

It is a file for language models. It gives AI agents an entry point to the site’s content, chosen by the site owner. A quick note on terms: a language model is a program trained on huge amounts of text that understands questions and generates answers. An AI agent is a tool built on such a model that browses websites and carries out tasks on its own. The idea appeared in September 2024. The llms.txt proposal says the file sits at /llms.txt or in a subdirectory (e.g. /docs/llms.txt) and covers the URLs under its path. Why Markdown and not XML? Because both people and models can read it. And a fixed layout means a standard parser can process the file.

How does llms.txt work and what should it contain?

The agent reads a small file with a description and links. It fetches details from the linked pages only when it needs them. That leads to a simple requirement: the file should be short so it fits in the model’s context, meaning the amount of text the model can handle at once. Typical contents:

• the site name as a heading,
• a short description of what the business does,
• tips on how to use the content,
• sections with links to key pages, for a store: categories, shipping, returns, terms and conditions, contact.

Ideally, the links should point to model-friendly content. For example, Markdown versions of pages without menus, scripts and ads (the model would throw them out anyway, so why feed them to it).

llms.txt vs robots.txt and sitemap.xml: what is the difference?

Nothing here replaces anything. llms.txt complements both files. Robots.txt tells crawlers where they are allowed to go. llms.txt adds context to content that is already open to them. Sitemap.xml lists every page for search engines to index, while llms.txt is a curated, annotated summary made with models in mind. The file can also point to the structured data used on the site, so the model knows how to read it.

Does an online store need llms.txt?

Need is too strong a word. A store can add one at low cost, as a tidy overview of its offer for AI tools. For now, these files show up mostly in software documentation, although the authors of the proposal also mention companies describing their structure and policies. What about AI and store visibility? Nobody promises anything here. It is not known which AI systems read this file or how they treat it. In my view, it makes sense for a large catalogue, when customers ask a lot about shipping and returns, or when you simply want to organise information about your offer. A small site with no time to keep the file up to date? It can safely skip it.

How to prepare llms.txt for your store step by step

In general, it is simple: you pick the most important content, describe it in Markdown, save the file in the root directory and test it with an AI agent. Step by step:

1. Pick the key categories and information pages.
2. Write a short description of the store and its product range.
3. Arrange sections of links, each with a one-sentence description.
4. Save the file as /llms.txt in the server’s root directory.
5. Ask an agent questions about the store, giving it only this file as a starting point.

And remember to keep it updated. Changing categories, shipping costs or return rules? Update the file, because an outdated one misleads. In WordPress with WooCommerce you usually create it by hand and upload it via FTP or your hosting file manager. In PrestaShop it is easier: the WS LLMS module generates an up-to-date llms.txt in a few clicks, combines Markdown content with selected categories, shows a live preview and saves the finished file straight to the root directory.

What to know before adding a file for language models

It is an experiment. The risk is small, but there is no guarantee of any effect on traffic or sales. The file is public, so do not put anything in it you would not show customers: margins, supplier details, internal procedures. It will not do your SEO for you either. Good product descriptions, including those written with AI help, and structured data still decide how search engines see your store. In practice, I recommend treating llms.txt as a simple, optional extra and watching where the proposal goes in the coming months.

Frequently asked questions