llms.txt generator for online stores
This llms.txt generator drafts the file from your store’s own pages, or lets you fill in the details yourself, and copies it out in the order the spec asks for.
Generate from your store
Type your site’s address and we fill in the builder below from your own pages: the name, the summary, and the pages your menus, footer and sitemap point to, each with its own title and description. Anything your pages do not say stays empty for you to write.
An llms.txt builder for a store
Filled in with an invented store to start. Type over it, or clear it and start from nothing.
Your store
Becomes the H1.
What you sell, where you ship, which currency.
Plain paragraphs, no headings.
Links
One link per line, as Title | URL | note. The note is optional.
Your main collections and best sellers.
Shipping, returns, sizes, contact.
Pages an agent can skip: about, blog.
llms.txt28 lines
# Northwind Linen > Linen bedding and clothing, made in Portugal. We ship to the EU and the UK; prices are in EUR. Every product page states its price, stock and delivery time. Returns are free within 30 days. ## Products - [Bedding](https://example.com/collections/bedding): sheets, duvet covers and pillowcases - [Shirts](https://example.com/collections/shirts): men’s and women’s, sizes XS to XXL - [Dresses](https://example.com/collections/dresses) - [Towels](https://example.com/collections/towels) - [Gift cards](https://example.com/products/gift-card): from 25 EUR - [New in](https://example.com/collections/new) - [Sale](https://example.com/collections/sale) ## Policies and help - [Shipping](https://example.com/policies/shipping-policy): costs and delivery times by country - [Returns](https://example.com/policies/refund-policy): 30 days from delivery - [Size guide](https://example.com/pages/size-guide) - [Care guide](https://example.com/pages/linen-care) - [Contact](https://example.com/pages/contact): email and phone, weekdays 9 to 17 CET ## Optional - [About us](https://example.com/pages/about) - [Journal](https://example.com/blogs/journal)
Checks4 of 4 met
- Passes: Starts with an H1, the store’s name (the only part the spec requires) (the spec)
- Passes: Has a one-line blockquote summary (the spec)
- Passes: Lists at least one page as a Markdown link (our DISC-002)
- Passes: Has at least 20 non-empty lines (now 20) (our DISC-002)
Our check also follows the first five links and wants each to load, which a page in your browser cannot test. The builder runs in your browser and sends nothing; only Generate llms.txt, above it, asks our server to read your store.
Check the rest of your store.
Free, no account, about five minutes.
What the builder does
Type your store’s name, a one-line summary and your links, and the builder writes an llms.txt in the spec’s order: the name as the H1, the summary as a blockquote, a few plain paragraphs, then your links in sections. Links go one per line, as Title | URL | note. It starts with Northwind Linen, an invented store that ships linen to the EU and the UK and has never sold a thing, so type your own details over its. As you type, a list under the file shows which of the spec’s rules and our DISC-002’s rules the file meets.
Or let us start it for you. Type your address into Generate from your store, and our server reads your robots.txt, your homepage and your sitemap, picks the key pages your menus, footer and sitemap point to (100 at most), reads each one, then fills the builder with what they say: the name, the meta description, and your pages in sections (collections and policies for a store; product, pricing, docs, blog and legal pages for any other site), each with its own title and description. You can watch the file fill in as the pages are read, and edit it while it does. Where your pages say nothing, the field stays empty, because a summary we made up would be worse than none.
What a store’s file should hold
Start with your store’s name as customers know it, then a summary that states a fact: what you sell, where you ship and in which currency. In our view it is the line a model is most likely to repeat, so save the slogan for your homepage. Then your main collections and a few best sellers, your shipping, returns, sizing and contact pages in a section of their own, and anything an agent can skip, such as the blog, under Optional.
Leave out cart, checkout and account pages, which tell a model nothing about your shop, and anything you would rather not see quoted back.
How big the file should be
Our rule of thumb: list your key pages, somewhere between 10 and 100 links in 5 to 9 sections, and keep the whole file small. The drafts we generate stop at 30 KB.
An agent that can read your file in one sitting gets the shape of your site. Give it every URL you have and it gets a phone book, and nobody has read one of those cover to cover in years.
So the generator leaves out sign-in, cart and search pages, tag pages and single blog posts. Your blog page stands in for its posts, and the posts are happy to be found from there.
How to publish it
The file goes at /llms.txt on your domain. Shopify already serves one for every store, built from the store’s own data; to write your own, add an llms.txt.liquid template to your theme. On WooCommerce the usual route is a plugin, and Yoast SEO has a setting for it. The full guide covers BigCommerce and Magento as well.
What to expect from it
llms.txt is a proposal, and no standards body has adopted it. Google says its Search ignores the file, and we found no AI vendor that says its assistants read a store’s copy. Some tools do look for it, Lighthouse’s experimental Agentic Browsing category among them, and it takes about half an hour to write. Our check also follows the first five links and wants each one to load, which a page in your browser cannot test. The builder runs in your browser and sends nothing you type. Generate from your store is the exception: it sends the address to our server, which reads the pages that go in the draft, about 100 at most, four a second at most, and obeys its robots.txt.
Frequently asked questions
What is an llms.txt file?
A Markdown file at /llms.txt that gives a language model a short map of your site: its name as a heading, a one-line summary, and links to the pages that matter. It is a proposal by Jeremy Howard, first published in September 2024, and no standards body has adopted it.
Where does llms.txt go?
At the root of your domain, so that yourstore.com/llms.txt answers with the file and a 200 status, as text/plain or text/markdown. Version 2 of the proposal also lets a file sit under a path and cover the pages below it, but for a store we would use the root.
What do I do with the file once it is generated?
Copy it and publish it at /llms.txt. Shopify already serves a default file there, and an llms.txt.liquid template in your theme replaces it. On WooCommerce a plugin such as Yoast SEO can serve it. Anywhere else, upload it as a text file at the site root. Then open yourstore.com/llms.txt in a browser and check that you get the file back, not your home page.
Will llms.txt get my store indexed or cited by AI assistants?
Nobody can promise that. Google says its Search ignores llms.txt, and none of the AI vendors whose crawler pages we read says its bots read a site’s copy. It is a cheap, low-risk convention: it costs nothing to serve, and some tools look for it, Lighthouse’s experimental Agentic Browsing category among them. Publish it on those terms and keep your expectations modest.
What does Generate from your store read?
Your robots.txt first. If it asks bots like ours to stay out, we stop there and read nothing else. Otherwise the homepage, your sitemaps and every page the draft lists, about 100 at most, four a second at most and never past a robots.txt rule, sent from our server as Storewalk. The draft holds only what those pages say, and we keep it for a day so a second click does not read your site again. Regenerate reads it afresh when you have changed your pages; it can run once every ten minutes per site, which is enough for anyone who is not trying to make it do push-ups.
How long should a store’s llms.txt be?
The spec requires only the H1. Our DISC-002 passes a file with an H1, at least 20 non-empty lines and at least one link, when its first five links load. The 20 lines are our threshold, not the spec’s.
The full guide
llms.txt for online stores: what to put in it
What llms.txt is, who says they read it, what a store’s file should hold and how to publish one on Shopify, WooCommerce, BigCommerce and Magento, with a builder that writes yours.