Aizii Learn · AI Search

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

# Where to put llms.txt on your website

Put the store-wide llms.txt file at the root of your site, so it loads at your domain followed by llms.txt. That is the conventional location, the same way robots.txt sits at the root. The proposal also allows a file at any subpath, such as a docs folder or a help center, and a file at a subpath covers the pages under that path. Where more than one file applies to a page, the most specific one should be used. For a store with one brand and one catalog, one file at the root is the right answer. For a site with clearly separate sections, add a second file under the section it covers, and keep the root file as the map for the whole store.

Say this first, because it shapes every placement choice in this guide. No engine is documented as reading llms.txt. Google says Google Search ignores the file, and keeping one will neither harm nor help visibility or rankings in Google Search. The proposal is a community proposal, not a vendor requirement and not a standard. Placement is about making the file findable to the readers that do look for it, not about buying a place in an answer. Nothing in this guide claims otherwise.

Also say this plainly wherever the full file comes up. The proposal defines llms.txt only. It does not define llms-full.txt. The full file is a companion convention from documentation platforms, not part of the proposal, not a vendor requirement, and not documented as read by any engine. If you keep a full file, put it next to the short file it belongs with, and link to it from the short file.

## Where it goes wrong

Placement fails in a few specific ways, and most of them come from guessing the address instead of checking the proposal.

-   The file is buried in a folder nobody would look for. A store-wide file placed under a blog folder or a page path covers only the pages under that path, so the rest of the store sits outside it.
-   The file is on the wrong host. A file on a subdomain, a staging domain, or a preview domain does not describe the live store. The proposal ties a file to the path where it sits, and a file on a different host describes a different site. The live store needs its own file at its own root.
-   Two files disagree. A root file lists one set of collections while a section file lists another, or the root file points at a guide the section file dropped. Where more than one file applies, the most specific one should be used, but two files that contradict each other leave the reader to pick. Keep one source of truth per section and make the files agree.
-   The file is behind a redirect. A redirect chain or a redirect to a login page breaks it. A file that only loads after two hops is a file a simple reader may never reach. Serve it directly at its address.
-   The file is blocked by robots.txt or by a bot rule. A robots.txt rule that blocks the file, or a firewall rule that challenges every bot, can keep a reader from fetching it. It does not override a block. Check that the file itself is fetchable.
-   The file is linked nowhere. A file with no link pointing at it can still be found by a reader that guesses the conventional address, but a file at a subpath with no link is hard to find. The proposal recommends link relations to help clients find them: a link with rel alternate and type text slash markdown points to the markdown version of a page, and a link with rel describedby points to the llms.txt file that covers it. Use them for section files, where the conventional root address does not help.

## The steps

**Step 1. Decide how many files the site needs.** The marketer lists the sections of the site: the store, the help center, the guides, and any docs area. A store with one brand and one catalog needs one file at the root. A site with a help center or a docs area under its own path can add one file under that path. Do not add a file per collection or per product.

**Step 2. Publish the store-wide file at the root.** The developer publishes the file so it loads at the store domain followed by llms.txt, served as plain text over HTTPS with a 200 status. Open it in a browser and confirm it loads, the H1 names the brand, and every link loads.

**Step 3. Place section files under the section they cover.** The developer publishes each section file at that section path, so a help center file loads at the store domain followed by the help path and llms.txt. The section file lists the pages under that section only. Check that the two files agree on the facts, and if they disagree, fix the source page first, then both files.

**Step 4. Point readers at the section files.** The marketer and the developer add discovery links for the section files, because a reader that only checks the root will never find them. The proposal recommends a link with rel describedby pointing to the llms.txt file that covers a page, and a link with rel alternate and type text slash markdown pointing to the markdown version of a page. These can be HTML link elements on the page or an HTTP Link response header set in server or CDN configuration. Add them to the section pages, and confirm they point at the right file.

**Step 5. Check the file is fetchable, not just published.** The developer opens the file address in a browser, confirms a 200 status, and confirms the content is plain text. Then the developer checks the robots.txt file and the firewall rules to confirm nothing blocks the llms.txt address itself. If a bot rule blocks it, add an exception for the file address.

**Step 6. Put the full file next to its short file.** If the store keeps a full text companion file, the developer publishes it at the same path as the short file it belongs with, so the root full file sits next to the root short file, and a section full file sits next to its section short file. The marketer adds one line to the short file pointing at the full file, so a reader that starts from the short file can find the full one. Remember the status: the full file is a companion convention, not part of the proposal, not a vendor requirement, and not documented as read by any engine.

## The machine-readable piece

This is the root file for a store, following the proposal format. It sits at the site root, so it covers the whole store. Replace the placeholders with your own pages.

```
# Example Outdoor Supply
> Example Outdoor Supply sells hiking, camping, and climbing gear, with fitting guides and repair advice, shipping across the country.
## Shop
- [Hiking](https://[yourdomain.com]/collections/hiking): Boots, packs, and poles, listed with size and weight.
- [Camping](https://[yourdomain.com]/collections/camping): Tents, sleeping bags, and stoves, listed with season rating and packed size.
- [Climbing](https://[yourdomain.com]/collections/climbing): Ropes, harnesses, and hardware, listed with rating and weight.
## Guides
- [Boot fitting](https://[yourdomain.com]/pages/boot-fitting): How to fit a hiking boot, with sizing steps and break-in advice.
- [Tent care](https://[yourdomain.com]/pages/tent-care): How to clean, dry, and store a tent between trips.
## Help
- [Shipping and returns](https://[yourdomain.com]/pages/shipping-returns): Shipping regions, delivery times, and the returns policy.
## Full text
- [Full guide text](https://[yourdomain.com]/llms-full.txt): The full text of the guides above in one file.
```

This is the section file for the same store, covering only the help center. It sits under the help path, so it covers the pages under that path.

```
# Example Outdoor Supply help
> Help pages for Example Outdoor Supply, covering shipping, returns, repairs, and warranties.
## Help
- [Shipping and returns](https://[yourdomain.com]/help/shipping-returns): Shipping regions, delivery times, and the returns policy.
- [Repairs](https://[yourdomain.com]/help/repairs): How to send gear in for repair, and what the repair service covers.
- [Warranties](https://[yourdomain.com]/help/warranties): Warranty terms for each brand the store carries.
```

And this is the discovery header the proposal recommends, set in server or CDN configuration, so a reader can find the section file and the markdown version of a page. Replace the paths with your own.

```
Link: </help/shipping-returns.md>; rel="alternate"; type="text/markdown", </help/llms.txt>; rel="describedby"
```

Check every file after you publish it. Open the root address and each section address in a browser and confirm each one loads as plain text, and confirm the discovery link points at the right file. Do not add a field, a page, or a value you cannot verify against the live site.

## What it looks like when it works

On the page, nothing looks different to a human reader. These are files for machines, not pages for shoppers. The change is under the surface: one file sits at the root and maps the whole store, a section file sits under the help center and maps only the help pages, and each page carries a link that points at the file covering it. A reader that checks the root finds the store map. A reader that lands deep in the help center finds the help map without guessing.

Say you run an outdoor gear store, selling hiking, camping, and climbing gear, with a boot fitting guide, a tent care guide, and a help center covering shipping, returns, repairs, and warranties. The marketer decides the site needs two files: one at the root for the store, and one under the help path for the help center. The developer publishes the root file and confirms it loads at the domain followed by llms.txt. Then the developer publishes the help file under the help path and adds the discovery links to the help pages. The marketer checks that both files name the same brand and state the same shipping regions. When the store adds a repairs page, the help file is updated the same day the page goes live. A shopper asks an assistant how to return a tent that does not fit. The assistant can follow the root file to the help center, then the help file to the returns page, and cite the store with the policy 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 where to put llms.txt on a website, at the root and under a section. It does not cover the full technical audit that checks every crawler and every page, 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 the common mistakes inside the file itself, which have their own guide. That is a separate job, 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/)
-   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.
