# llms.txt in 2026: useful, not a ranking hack
> llms.txt v2, Shopify, Google and ChatGPT: what the file proves, what it cannot prove, and where it belongs in AI commerce, without ranking myths or hype.
- Canonical HTML: https://verityscore.io/en/blog/llms-txt-2026-ecommerce/
- Markdown alternate: https://verityscore.io/en/blog/llms-txt-2026-ecommerce.md
- Language: en
- Content type: blog
- Published: 2026-06-28
- Updated: 2026-08-28
- Tags: llms-txt, llmtxt, llms-txt-v2, ecommerce, shopify, agentic-commerce, product-data
## The 60-word answer

`llms.txt` can help a compatible agent find your best pages without crawling the entire site. It is useful, inexpensive and now better defined. But the file remains a **map**, not evidence of use. It cannot replace an accessible website, current product facts, or the feeds and protocols needed to compare, recommend and purchase a product.

## llmtxt, llms txt or llms.txt: what are we discussing?

The correct name is **`llms.txt`**. “llmtxt” and “llms txt” are search variants, not competing formats.

The proposal, first published in September 2024, describes a Markdown file at the root of a site. Its purpose is straightforward: give a language model a compact list of resources worth reading first. The file can introduce the organization and group links to authoritative pages.

Three qualifications change how it should be evaluated:

- it is a community proposal, not a W3C or IETF standard;
- publishing the file proves only that it is published;
- its value depends on the pages it selects.

For an independent explanation, examples and a validator, see [llmtxt.info's guide to llms.txt](https://llmtxt.info/what-is-llms-txt/).

## What version 2 actually changes

Version 2, announced in August 2026, turns a simple convention into a more precise discovery mechanism.

| Change | Practical effect | What it does not prove |
|---|---|---|
| Files scoped to subpaths | A catalogue, docs area or help centre can have its own map | That an agent visits the subpath |
| Most specific file takes priority | `/help/llms.txt` can describe help content better than the root file | That every platform implements the rule |
| `rel="alternate"` to Markdown | An HTML page can announce a compact representation | That an agent chooses it |
| `rel="describedby"` to `llms.txt` | A page can identify the map covering it | That the link affects recommendations |
| Two Markdown page conventions | `page.html.md` or `page.md` become predictable | That every CMS generates them |

One misconception is worth removing: only the H1 title is required by the format. A summary, notes and link sections are useful but optional. A long template is not automatically more compliant.

## Do not shorten the evidence chain

Discussion about `llms.txt` often collapses eight different states:

| State | Question | Required evidence |
|---|---|---|
| Published | Does the file exist? | HTTP 200 response |
| Accessible | Can an allowed crawler retrieve it? | Test using real controls and protection |
| Valid | Does it follow the format? | Checked H1, Markdown and links |
| Retrieved | Did an agent request it? | Server log with a verified crawler |
| Followed | Did it visit a listed URL? | Correlated request sequence |
| Used | Did content contribute to an answer? | Controlled test or platform trace |
| Cited | Did the brand or page appear? | Dated observation of the answer |
| Converted | Did that presence create value? | Attributable click, cart or sale |

**A request for the file does not prove a citation. A citation does not prove a sale.** This distinction makes the file testable without promising an outcome no primary source guarantees.

## What Google, OpenAI and Anthropic actually say

### Google: no special signal

Google states that its AI features in Search rely on existing fundamentals. No special AI file, special markup or new structured data is required. Its guide says files such as `llms.txt` are not used for ranking or generative features.

Lighthouse nevertheless offers an `llms.txt` audit under agentic browsing. There is no conflict: Lighthouse checks the presence and syntax of an optional resource. A 404 makes the audit not applicable. Passing it is not a Google Search endorsement.

### OpenAI: robots.txt remains the documented control

OpenAI distinguishes OAI-SearchBot, used for search features, from GPTBot, associated with training. Its publisher guidance tells site owners to manage access through `robots.txt` and keep pages accessible if they should appear with a link and summary.

OpenAI also publishes an `llms.txt` file for its developer documentation. That is a useful example of a documentation map. It is not a commitment to read every merchant's file, nor a requirement for ChatGPT citations.

### Anthropic: separate crawlers controlled through robots.txt

Anthropic documents ClaudeBot for training, Claude-SearchBot for search and Claude-User for user-triggered visits. Its public controls again rely on `robots.txt`. The absence of official instructions asking publishers for `llms.txt` does not prove zero internal use, but it prevents us from calling the file a requirement.

## Published adoption and measured use are different

The 24 August 2026 snapshot from [the llmtxt.info observatory](https://llmtxt.info/observatory/) tested a fixed panel of 219 organizations weighted towards developer tools. Among 218 reachable hosts, 119 served a qualifying file, or 54.6%. In the small ecommerce category, 7 out of 13 did so.

Those figures are useful for tracking change over time, but they do not describe the entire web. The panel is deliberately technical, the ecommerce sample is tiny and the test measures publication, not consumption.

Shopify makes the gap even clearer. In [Verity Score's barometer of 475 French Shopify stores](/en/blog/geo-barometer-shopify/), 465 stores, or 97.9%, served an `llms.txt` file. Yet 97% of the observed files still followed the platform template. The high rate mainly describes a native feature, not 465 distinct editorial strategies.

## Shopify: inspect before creating

Since May 2026, Shopify has served `/agents.md`, `/llms.txt` and `/llms-full.txt` by default. Themes can customize them through:

- `templates/agents.md.liquid`;
- `templates/llms.txt.liquid`;
- `templates/llms-full.txt.liquid`.

The first action is not “create a file.” Open all three URLs and ask:

1. Does the content describe the store accurately?
2. Do the priority links match current categories and policies?
3. Is an essential page missing?
4. Does the file repeat volatile data likely to become false?

Our analysis of [Shopify, agents.md, llms.txt and AI commerce protocols](/en/blog/shopify-agents-md-llms-txt-ucp-ai-commerce/) explains the platform-generated layer.

## What belongs in an ecommerce file?

A good merchant file is not a second sitemap. It selects resources that help an agent understand the offer and answer purchase objections.

### Include

- a brand or About page establishing seller identity;
- major categories with clear propositions;
- buying, compatibility and sizing guides;
- shipping, returns, warranty and payment policies;
- support pages answering recurring questions;
- a small set of stable expert resources.

### Exclude

- cart, login, checkout and internal search;
- thin filters and faceted variants;
- private, temporary or non-canonical pages;
- internal instructions and sensitive data;
- prices, promotions or inventory copied by hand.

Volatile facts need a controlled dynamic source. An outdated price in a static file can be more harmful than a missing file.

### A minimal annotated example

    # Example Home

    > Durable furniture made in France and delivered across the EU.

    ## Shop

    - [Dining tables](https://example.com/tables): materials, dimensions and lead times
    - [Sizing guide](https://example.com/sizing): choose the right dimensions

    ## Trust and service

    - [Shipping](https://example.com/shipping): regions, timeframes and costs
    - [Returns](https://example.com/returns): conditions and process

The example stays deliberately short. Every link has an explicit job. It includes no inventory, price or invented transactional capability.

## The eight-check quality test

Before calling the file ready:

1. **Response**: the expected path returns HTTP 200, not a soft 404.
2. **Type**: the server returns readable text with the correct encoding.
3. **Structure**: an H1 clearly identifies the site or section.
4. **Selection**: each URL genuinely deserves priority.
5. **Destination**: links resolve without loops or long redirect chains.
6. **Consistency**: URLs are canonical, public and in the right language.
7. **Freshness**: content follows page and policy changes.
8. **Security**: no private URL, internal instruction or sensitive fact is exposed.

Our [implementation guide to llms.txt](/en/kb/llms-txt/) covers creation. This article answers a different question: should the file be prioritized?

## Where does llms.txt belong in the backlog?

| Situation | Priority | Why |
|---|---|---|
| File absent, fundamentals solid | Medium | Low cost, potential discovery benefit |
| Shopify with a native file | Low to medium | Audit and customize before recreating |
| Blocked or inaccessible pages | Very low | A map cannot repair access |
| Inconsistent price or inventory | Very low | Product truth comes before discovery |
| Rich, stable documentation | High | The format excels as an editorial index |
| Highly dynamic catalogue | Secondary | Feeds and structured data take priority |

For a merchant, the recommended order is:

1. deliberately allow or block the relevant crawlers;
2. serve fast, public and well-linked pages;
3. publish consistent product identity, price, availability, shipping, returns and review data;
4. maintain sitemaps, canonicals and structured data;
5. add or improve `llms.txt`;
6. measure every stage in the evidence chain.

## From discovery to agentic commerce

An `llms.txt` file can help an agent **understand where to read**. It does not automatically let that agent:

- know real-time inventory;
- negotiate a capability;
- build a cart;
- apply a promotion;
- start checkout;
- confirm an order.

Those actions belong to product feeds, APIs and agentic commerce protocols. [Agentic Commerce Protocol's analysis](https://agenticcommerceprotocol.info/analysis/llms-txt-agentic-commerce) compares the role of `llms.txt` with ACP, UCP, AP2, MCP and x402 using dated primary sources.

The difference fits in one sentence: **`llms.txt` describes resources; a transactional protocol describes capabilities and actions.**

## Verdict: useful when you measure the right thing

In 2026, publishing a well-curated `llms.txt` file is reasonable once the fundamentals are solid. Version 2 improves discovery, CMS platforms reduce deployment work and maintenance can stay inexpensive.

But “the file exists” is not a success criterion. Compare an expected number with an observed number: verified requests, followed links, observed citations, clicks or conversions. Until those stages are measured, the benefit is **unmeasured**, not zero and not guaranteed.

---

## Read next

- [Create an llms.txt file step by step](/en/kb/llms-txt/)
- [Barometer: what 475 Shopify stores actually do](/en/blog/geo-barometer-shopify/)
- [Shopify, agents.md, llms.txt and UCP](/en/blog/shopify-agents-md-llms-txt-ucp-ai-commerce/)
- [robots.txt and AI crawlers](/en/kb/robots-crawlers/)
## FAQ

### Which spelling is correct: llmtxt, llms txt or llms.txt?

The file and proposal are named llms.txt. llmtxt and llms txt are common search variants, not separate formats.

### Does llms.txt improve Google rankings?

No. Google says it does not use AI text files such as llms.txt for ranking or its generative features. The file may still act as a content map for other tools, but no unmeasured Google effect should be attributed to it.

### Does ChatGPT require an llms.txt file to cite a site?

No. OpenAI's official publisher instructions focus on OAI-SearchBot and robots.txt. OpenAI publishes an llms.txt file for its own developer documentation, but that does not prove ChatGPT requires or consumes every site's file.

### Does Shopify create llms.txt automatically?

Yes. Shopify serves llms.txt, llms-full.txt and agents.md by default and allows merchants to customize them with Liquid templates. A Shopify merchant should inspect the files already served before creating anything.

### What belongs in an ecommerce llms.txt file?

Use a short selection of stable canonical pages: brand, major categories, buying guides, sizing, shipping, returns, warranties and support. Include price, inventory or promotions only when updates are automated and controlled.

### How should llms.txt value be measured?

Measure availability, verified server requests, followed links, observed citations, clicks and conversions separately. One stage never proves the next automatically.

## Sources

- [The llms.txt v2 proposal](https://llmstxt.org/) (official)
- [llms.txt change history](https://llmstxt.org/changes.html) (official)
- [Google Search: guide to AI features](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) (official)
- [OpenAI: publishers and developers FAQ](https://help.openai.com/en/articles/12627856-publishers-and-developers-faq) (official)
- [Anthropic: web crawlers and controls](https://privacy.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler) (official)
- [Shopify: customize llms.txt, llms-full.txt and agents.md](https://shopify.dev/changelog/customize-llmstxt-llms-fulltxt-and-agentsmd) (official)
- [Independent llmtxt.info observatory, 24 August 2026 snapshot](https://llmtxt.info/observatory/) (case_study)