Does llm.txt for SEO do anything? What Google has said, what the data shows, and what to do instead

Last updated: November 4, 2026

Say you spent twenty minutes last month generating an llms.txt file, uploaded it to your store's root, and now you are watching rankings and ChatGPT referrals for a change. Nothing moved. That is the normal outcome, and this guide explains why without pretending the file is useless. "llm.txt for SEO" is really two claims wearing one name: that the file helps you rank in Google, and that it helps AI assistants find and cite your store. The first claim has been answered by Google. The second has not been confirmed by any AI provider as of November 2026. Both answers are below, with the sources, so you can decide whether twenty minutes is worth it for your store.

What is llms.txt, and who proposed it?

llms.txt is a plain Markdown file placed at a website's root that gives large language models a short summary of the site and a curated list of links. It was proposed by Jeremy Howard in September 2024 at llmstxt.org. The only required part is an H1 with the site's name. It is a community proposal, not a standard adopted by Google, OpenAI or Anthropic.

The proposal page describes the format: an H1, a blockquote summary, optional detail sections, H2 lists of links, and an "Optional" section for secondary material. It also suggests publishing Markdown copies of pages at the same URL with .md appended. The page notes that OpenAI, Anthropic and Google's Gemini publish llms.txt files for their own developer documentation. Publishing a file for your docs is not the same as reading other sites' files, and the proposal does not claim that any AI system consumes them.

Is llm.txt the same as llms.txt?

People use both spellings for the same idea. The proposal names the file llms.txt, plural, with an s. "llm.txt" is a common misspelling that search engines treat as the same query. If you create the file, name it llms.txt, because that is the path anyone who does look for it would request.

A related file, llms-full.txt, is used by some documentation sites to hold the complete text rather than a list of links. The proposal page itself does not define it. Treat it as a convention from documentation tooling, not part of the spec.

What has Google said about llms.txt and SEO?

Google has not said that llms.txt affects Google Search rankings, and its Search Advocate John Mueller has said that no AI services have stated they use the file. Google briefly published llms.txt files across its own developer sites after a CMS update and removed the one on its Search documentation within a day, per Search Engine Land's reporting.

The Search Engine Land article quotes Mueller: "None of the AI services have said they're using llms.txt". It also reports his comment that files on other Google properties are not findable by default and are "there for other purposes". The article states that no major LLM provider, including Google, has officially committed to parsing the file. That is the full extent of what can be sourced to Google as of November 2026. Anything stronger, in either direction, is opinion.

On the other side of the ledger, Google's Chrome team added an llms.txt check to Lighthouse in May 2026, describing the file as an emerging convention and telling site owners to place it in the root directory. An audit tool checking for a file is not a ranking signal, and the two Google teams are saying different things. Both are true at once: Chrome's tooling encourages the file, Search has not said it uses it.

What does the data show about AI crawlers and llms.txt?

The one published study with server logs, from Search Engine Land, tracked 10 sites for 90 days before and after adding llms.txt. AI crawlers rarely requested the file, crawl frequency was unchanged on the sites that documented it, eight sites saw no measurable change in AI referral traffic, two grew for reasons the authors attributed to other changes, and one declined.

Three details from the study matter for a store. The sites were in finance, B2B software, ecommerce, insurance and pet care, so the ecommerce case was covered. The measure was referral traffic from ChatGPT, Claude, Perplexity and Gemini, which is the number a store cares about. And the authors checked for other site changes in the same window, which is why the two sites that grew were not credited to the file.

That is a small sample and a short window, and the article does not date itself on the page, so treat it as the best available evidence rather than a verdict. It agrees with what the Reddit threads on this search say, where the top-voted answers in r/SEO and r/SEO_for_AI advise against spending time on the file. It also agrees with what you will see in your own server logs: requests for /llms.txt from AI user agents are rare, and when they appear they are usually from tools that audit sites, not from assistants answering users.

Then why does every SEO plugin offer an llms.txt generator?

Because the file is cheap to generate, cannot harm a site, and customers ask for it. Yoast, Rank Math and most AI visibility tools, including StorePinger, generate one. The honest framing is that the file is a low-cost bet on a convention that may be adopted, not a tactic with measured results today.

There is a second, less flattering reason. A generator is a feature that demos well and ships in an afternoon, and a feature list with "AI visibility" on it sells plugins. That applies to StorePinger as much as to anyone. The difference worth paying attention to is whether a tool also measures the result, because measurement is where the honest signal lives.

StorePinger's feature list says exactly that: it writes an llms.txt file for the store and tracks visits from AI tools. The tracking is the part with a measurable result, because a visit from ChatGPT either arrives or it does not, and the AI visibility report counts it. The file is the part that costs a click and waits. The free online generator on this site produces a file in the proposal's format in a minute, which is the right amount of time to spend on it.

Could llms.txt still matter later?

Possibly. Conventions become standards when a large consumer adopts them, and none has, as of November 2026. If OpenAI, Anthropic or Google announced that an assistant reads /llms.txt when choosing what to cite, the file would matter the next day. Having one in place costs almost nothing and means you would not be starting from zero. That is a reasonable hedge, not a strategy.

One more honest point. The absence of a documented consumer is not proof that no assistant reads the file. It is proof that none has said so, and that server logs do not show it at a rate anyone has measured. A store owner cannot act on a possibility that leaves no trace in logs. You can act on a cheap hedge, which is what the file is.

Two things would change the picture. First, an AI provider documenting the file the way OpenAI documents its crawlers. OpenAI's bots documentation explains OAI-SearchBot, ChatGPT-User and GPTBot and how robots.txt controls each. It does not mention llms.txt. Second, server logs showing assistants fetching the file before citing a site. Watch your own logs for /llms.txt requests from the user agents OpenAI documents. If they appear regularly, the convention has turned into behaviour.

How do AI assistants actually find a store, if not through llms.txt?

The same way search engines do: by crawling pages that robots.txt allows, reading the text and structured data on them, and cross-checking against other sites that mention the store. OpenAI documents a dedicated crawler, OAI-SearchBot, for ChatGPT's search features, and a separate user agent, ChatGPT-User, for pages an assistant opens because a user asked. Neither needs a summary file to find a product page that is linked, fast and clear.

This is the practical reason the file has not mattered. An assistant answering "best stainless travel mug under $30" runs a search, opens a handful of pages that rank for it, and reads them. Your product page is in that handful or it is not, and what decides it is the same set of things that decides a Google ranking plus how plainly the page answers the question. A curated list at /llms.txt sits one level above the pages the assistant is already reading, and nothing published so far shows an assistant climbing to that level first.

Where a summary file could help is a site whose pages are hard to read: heavy scripts, content loaded after the page, thin product descriptions. For those sites the better fix is still the pages themselves, because the assistant will land on the page, not the summary, when it follows a search result.

What should the file contain if you do make one?

The H1 with your store name, a two-sentence blockquote saying what you sell and for whom, and H2 lists of your most important category and product URLs with one-line descriptions. Twenty to fifty links is plenty. Leave out cart, checkout, account, admin and search pages, and anything you would not want quoted.

For a WooCommerce store the natural structure is one H2 per top-level category with its products underneath, then an H2 for policy pages such as shipping and returns, then an Optional section for the blog. A generator that reads the catalog does this in seconds and keeps the links real. The best practices guide has the full structure and an example file, and the free generator on this site produces one from a URL.

What should a store do for SEO and AI visibility instead?

Do the things both Google Search and AI assistants are documented to rely on: let the crawlers in, keep product pages crawlable and fast, answer real questions on them, mark products up with structured data, and keep names, prices and availability consistent everywhere. These are measurable, they help today, and an llms.txt file is a footnote to them, not a substitute.

A worked example, not a customer result. A store with 1,000 daily visits sees 20 a day from ChatGPT and Perplexity combined, 2% of traffic, and those 20 visits produce one order a day on average. Over a month that is 30 orders from AI assistants. That number comes from the sales by source report, which names AI tools as a source. Nothing in it depends on the llms.txt file. If the store adds the file and the 20 becomes 25 three months later, the file may have helped, or the store's structured data did, or the assistant's index grew. The report cannot tell you which, and neither can anyone else yet.

How to decide in one minute

If a generator can make the file for you, make it, upload it, and stop thinking about it. If adding it means paying someone, editing templates or maintaining a list of URLs by hand, skip it until a provider confirms they read it. Spend the saved time on product page answers and structured data, which move measurable numbers.

1. Generate the file with a tool that reads your catalog, so the links are real.
2. Upload it to the root. The placement guide covers WordPress specifics.
3. Open it in a browser to confirm it is served as plain text.
4. Note the date. Regenerate it when the catalog changes, or not at all if that is a chore.
5. Turn on AI visit tracking so that if assistants start sending buyers, you see it the week it happens.

Common mistakes

• Calling it an SEO tactic. Google has stated no ranking effect. Say "AI visibility hedge" and you will be accurate.
• Hand-building a long file. If no one reads it, the hours are gone. Generate it.
• Listing staging, admin or cart URLs. The file is public. Anyone can read it.
• Letting it drift. A file that links to deleted products is worse than none, if anyone does read it.
• Blocking the crawlers that do matter. A robots.txt that disallows OAI-SearchBot removes the store from ChatGPT search answers per OpenAI's documentation, and no llms.txt file fixes that.
• Measuring the file instead of the visits. Track AI referrals and orders. That is the number that moves. The ChatGPT traffic guide shows how.

Conclusion

llm.txt for SEO is a short story with a clear ending as of November 2026: Google has stated no ranking effect, no AI provider has said it reads the file, and the one log-based study found crawlers rarely ask for it. The file is still worth a minute of your time, because a minute is all it costs, Chrome's audit tool now looks for it, and a convention can become a standard overnight. Make it with a generator, put it at the root, then spend your real effort on crawlable product pages, clear answers, structured data and consistent prices, and on tracking whether AI assistants send buyers at all. The what is llms.txt guide covers the format, the best practices guide covers what to put in it, and the AI visibility feature shows what the tracking looks like.