Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# What is llms-full.txt and when do you need it

llms-full.txt is one Markdown file that carries the full text of your most important pages, so a reader can load the whole thing in a single fetch instead of chasing link after link. Think of llms.txt as the table of contents and llms-full.txt as the book. The short file lists your collections and guides with a line of description each. The full file holds the guides themselves, start to finish.

Say this plainly first, because the status of the file decides everything else in this guide. The current llms.txt proposal at llmstxt.org defines llms.txt only, and it does not mention llms-full.txt. The full file grew up next to the proposal as a companion convention used by documentation platforms, not as part of the proposal itself. No vendor requires it, and no engine is documented as reading it. Build it only after llms.txt exists and is current. It is an extra, not a replacement, and it is not a ticket into an answer.

Whether you need it comes down to three questions. Do you publish guides that run long, the kind a reader needs in full rather than as a summary? Do you have enough of them that following links one by one is a chore? And do the guides change slowly enough that a single file can keep up with them? Three yes answers means the full file earns its keep. Any no means the short file is enough for now.

## Where it goes wrong

The full file is simple to build and easy to get wrong. The mistakes below are the ones that turn a useful document into a liability.

-   The store buys the full file before it has a short file. A full-text file built from a sloppy index inherits every gap in it: missing guides, dead links, stale collections. The short file is the map, and a map with the wrong roads builds a book with the wrong chapters.
-   The store treats the file as a place to dump the catalog. Product pages do not belong in a full-text file. A reader who opens the file wants the guides, and a thousand product descriptions in the way means the guides never get read. Keep products in the short file as collections.
-   The store lets prices and stock slip into the text. A guide that mentions a price becomes wrong the day the price moves, and a full file is rebuilt far less often than a product page. Any number that changes belongs on the product page and in the structured data, never in a static document.
-   The store writes the file once and walks away. Guides get rewritten, new guides get published, old ones get retired, and the full file still carries the first draft. A reader who compares the file with the live guides and finds a mismatch stops trusting both.
-   The store locks the file behind a login or a redirect chain. A file that returns anything other than plain text with a 200 status at its plain address does not exist to a reader. Publish it at the root, open it in a browser, and confirm it loads before you tell anyone it is there.
-   The store expects the file to earn citations. Nothing in the proposal or in any vendor doc cited here says a full-text file wins a recommendation, a citation, or a place in an answer. The file serves a reader that already found you. It does not make you findable.
-   The store writes the file from memory instead of from the live pages. A guide paraphrased from memory drifts from the guide on the site within a month: a step reordered, a measurement changed, a warning dropped. Build from the live pages, every time, and check the facts match before you publish.

## The steps

**Step 1. Run the three-question test.** The marketer answers the three questions from the opening: long guides, enough of them to matter, and a pace of change the file can keep up with. If any answer is no, stop here and put the effort into llms.txt and the guides themselves. The full file is a convenience for a reader, and a convenience nobody needs is clutter.

**Step 2. Finish the short file.** The marketer confirms llms.txt is live at the site root, current, and in the proposal format: an H1 with the brand name, a blockquote summary, and H2 sections of links with one-line descriptions. The full file is assembled from the pages the short file lists, so a wrong short file produces a wrong full file. Read our llms.txt guide for the format and a complete sample.

**Step 3. Pick the pages that earn a place.** The marketer chooses the guides whose full text a reader actually needs: repair guides, buying guides, size and fit guides, care instructions, and the policy pages shoppers ask about. Leave out every product page, every sale page that will expire, anything behind a login, and the cart and checkout pages. If the chosen list is too long for one document, plan to split it by section now, not after it is built.

**Step 4. Pick the build route.** The developer chooses how the file gets made. If the guides live on a documentation platform such as Mintlify, the platform generates both files from the same source and keeps them in step on every publish. If the guides live on the store platform, the developer builds the file from the live pages, by hand for a small library or with a build script for a large one. The route differs. The rule does not: the file comes from live pages, not from memory and not from a draft.

**Step 5. Assemble the file in the short file's order.** The developer turns each chosen page into one section, in the same order the short file lists them, with the page title as the heading and the full text beneath it. Navigation, cookie banners, ads, and layout get stripped out. The words, the headings, and the links that matter stay. Then the marketer reads the file against the live pages and checks the facts: the steps in order, the measurements right, the limits stated.

**Step 6. Publish at the root and point at it from the short file.** The developer publishes the file at the site root, next to llms.txt, and opens it in a browser at the store domain followed by llms-full.txt to confirm it loads as plain text over HTTPS with a 200 status. Then the marketer adds one line to llms.txt that points at the full file, so a reader starting from the short file can find it. There is no submission step, no search console entry, and no ping endpoint. Publish it, verify it loads, and fetch it again after every change.

**Step 7. Tie the rebuild to the guide routine.** The marketer and the developer agree on the trigger: whenever a guide in the file changes, a guide is added, or a guide is removed, the file is rebuilt the same day. The rebuild belongs in the same routine that publishes a guide, so it happens without a separate project. Each rebuild includes a size check. If the file has grown past what a reader can use in one document, split it by section and link the sections from llms.txt.

## The machine-readable piece

This is the llms.txt index for a store with a repair guide library, following the proposal format. It lists the collections and the guides, and it points at the full file. Replace yourdomain.com with your actual domain.

```
# Spoke and Chain Supply
> Spoke and Chain Supply sells bicycle parts, tools, and accessories, shipping across the country. The shop publishes repair guides and runs a wheel truing service by mail.
## Shop
- [Drivetrain](https://[yourdomain.com]/collections/drivetrain): Chains, cassettes, and chainrings, listed with speed count and compatibility.
- [Wheels](https://[yourdomain.com]/collections/wheels): Rims, spokes, and hubs, listed with size and axle standard.
- [Tools](https://[yourdomain.com]/collections/tools): Workshop tools for home mechanics, listed with the jobs each tool covers.
## Guides
- [Fix a flat](https://[yourdomain.com]/pages/fix-a-flat): The full flat repair, from removing the wheel to seating the tire.
- [Adjust a derailleur](https://[yourdomain.com]/pages/adjust-derailleur): Indexing steps, limit screws, and cable tension.
## Full text
- [Full guide text](https://[yourdomain.com]/llms-full.txt): The full text of the guides above in one file.
```

And this is the shape of the full file itself. Each page becomes one section, in the same order as the short file lists them, with the page title as the heading and the full text beneath it. This excerpt shows one page. A real file holds every chosen guide, in order.

```
# Spoke and Chain Supply guides

## Fix a flat

Spoke and Chain Supply walks a home mechanic through a full flat repair, from removing the wheel to seating the tire and checking the pressure. The guide gives the steps in order, the tools needed, and the mistakes that cause a second flat on the same ride. Prices and stock are not in this file. See the product pages for current prices.
```

Check both files after every rebuild. Open your domain followed by llms.txt and confirm the links load. Open your domain followed by llms-full.txt and confirm the full text loads and matches the live guides. If a guide changed and the full file did not, rebuild it.

## What it looks like when it works

On the page, nothing looks different to a shopper. These are files for machines, not pages for people. The change is under the surface: the short file maps the store in a page of links, and the full file carries the guides as one document, in the same order, with the same words as the live pages. A reader that starts from the short file can follow one link and read the whole guide library.

Say you run a bicycle parts store with a large catalog and a library of repair guides. The marketer runs the three-question test and gets three yes answers. The short file gets finished first, listing the collections and the guides with one-line descriptions. Then the marketer picks the guides for the full file: fixing a flat, adjusting a derailleur, and truing a wheel, leaving out the product pages and the sale pages. The developer builds the full file from the live guides, strips the navigation and banners, and publishes it at the site root. The marketer checks the file, finds a price printed in one guide, and replaces it with a product page link. When a guide is rewritten, the full file is rebuilt the same day. A shopper asks an assistant how to fix a flat on a first long ride. The assistant reads the guide in full and answers with the steps as written.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •The llms.txt format and a complete sample, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •The markup AI systems read to verify facts, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •The complete crawler rule reference, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

This guide covers adding llms-full.txt for a store with a guide library. It does not cover the full technical audit, the transaction layer that lets an agent complete a purchase, or the per-engine playbooks for getting each assistant to find you. It does not cover keeping prices and availability accurate, which belong on the product page, in the structured data, and in the feed. Those are separate jobs, and this guide is the map, not the whole trip.

## Check your own store now

Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   llms.txt proposal (specific): [https://llmstxt.org](https://llmstxt.org/)
-   Mintlify, How to help AI coding agents find your docs (specific): [https://www.mintlify.com/library/how-to-help-ai-coding-agents-find-your-docs](https://www.mintlify.com/library/how-to-help-ai-coding-agents-find-your-docs)
-   Google Search Central, Optimizing your website for generative AI features on Google Search (specific): [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
-   Google Search Central, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   Schema.org, Product type (specific): [https://schema.org/Product](https://schema.org/Product)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
