# llms.txt example: basic files and templates

> Sample llms.txt files with commentary for a documentation site, an online store, a blog and a company site - what goes into each section, why, and what to change for your own site

Page: https://llms-full-txt.ru/en/examples/basic/
Site index: https://llms-full-txt.ru/en/llms.txt

Below are four sample `llms.txt` files for different sites. Their addresses and names are for teaching: the `.example` domain does not exist.

The structure is the same everywhere: a name, a summary, sections with links. What differs is what counts as the main material.

Copy the approach, not the text: which sections were chosen and what the notes say.

## The shortest valid file

Only the title is required:

```markdown
# Kolos
```

The file is formally valid and useless: an agent has nowhere to go. A working minimum is a name, a summary and at least one section.

```markdown
# Kolos

> A bakery in Leeds: bread and pastry with delivery.

## Main

- [Menu and prices](https://kolos.example/menu.md): the full range with ingredients
- [Delivery](https://kolos.example/delivery.md): areas, hours, cost
```

## A documentation site

- llms.txt
- Documentation of a service
- Name and summary

```
# Kolos API
> A delivery service for online stores: rate calculation, order creation, tracking.
```

- Who needs the service and why
- Know in advance

```
Every request needs a key in the Authorization header.
The API version is part of the address: /v2/.
```

- What an agent would get wrong in its very first request
- Where to start

```
## Start
- [Quick start](https://kolos.example/docs/start.md): the key, the first request, the first order
- [Authentication](https://kolos.example/docs/auth.md): keys, permissions, expiry
```

- The path of a newcomer
- Reference

```
## API
- [Orders](https://kolos.example/docs/orders.md): create, change, cancel
- [Rates](https://kolos.example/docs/rates.md): cost by address and weight
- [Errors](https://kolos.example/docs/errors.md): codes and what to do about them
```

- One link per subject
- Secondary

```
## Optional
- [Changelog](https://kolos.example/docs/changelog.md): versions and dates
```

- Can be skipped when a short context is needed

Why this way:

- Links point to Markdown versions of pages: an agent does not have to parse HTML.
- The "know in advance" block saves mistakes. It holds what applies to every request.
- The reference does not list every method: one page per subject.

## An online store

```markdown
# Volna

> An online store of home appliances: kettles, coffee makers, vacuum cleaners. Delivery across the UK.

Prices on the site include VAT. Availability is refreshed hourly.

## Catalog

- [Kettles](https://volna.example/category/kettles/): electric and stovetop, 1 to 2.5 l
- [Coffee makers](https://volna.example/category/coffee/): drip, espresso, capsule
- [Vacuum cleaners](https://volna.example/category/vacuum/): corded, stick, robots

## For customers

- [Delivery](https://volna.example/delivery/): cities, times, cost, pickup
- [Payment](https://volna.example/payment/): cards, instalments, pay on delivery
- [Returns and warranty](https://volna.example/returns/): terms, conditions, service address
- [Contacts](https://volna.example/contacts/): phone, address, opening hours

## Optional

- [About the company](https://volna.example/about/): legal details and history
```

Why this way:

- The file lists categories, not every product. There are thousands of products, and their list is already in `sitemap.xml`.
- The "For customers" section answers the most frequent questions: delivery, payment, returns.
- Prices are left out: they change. A machine takes the exact price and availability from the product page, from structured data.

What describes a product page: [Structured data and JSON-LD](https://llms-full-txt.ru/en/guides/json-ld/).

## A blog

```markdown
# Notes on the web

> A blog about how sites work: speed, accessibility, search. One author, a new post every two weeks.

## Main posts

- [Why a site is slow](https://notes.example/slow-site.md): five causes and how to find yours
- [Accessibility from zero](https://notes.example/a11y-start.md): what to check on any site in an hour
- [How to read a Lighthouse report](https://notes.example/lighthouse.md): which numbers matter and which do not

## Topics

- [Speed](https://notes.example/topics/speed/): posts about loading and rendering
- [Accessibility](https://notes.example/topics/a11y/): posts about keyboard, contrast, screen readers

## Optional

- [All posts](https://notes.example/archive/): the full list by date
- [About the author](https://notes.example/about/): experience and contacts
```

Why this way:

- The best posts come first, not the latest. RSS exists for the stream of new entries.
- The full archive is moved to `Optional`.
- The summary says who writes and how often: that helps judge the source.

## A company site

```markdown
# Opora Bureau

> We design and build timber-frame houses in Yorkshire. Fixed-price contracts.

## Services

- [Design](https://opora.example/design/): what a project includes, timing, what the client provides
- [Construction](https://opora.example/build/): stages, timing, warranty
- [Ready projects](https://opora.example/projects/): floor plans and areas

## How we work

- [Stages and payment](https://opora.example/process/): from survey to handover
- [Questions and answers](https://opora.example/faq/): plot, foundation, winter, mortgage
- [Contacts](https://opora.example/contacts/): address, phone, opening hours
```

Why this way:

- There is no section with news and vacancies: they do not answer a client's questions.
- The questions and answers page is a must: those are ready answers.

## What good files have in common

- The summary answers "what is here and for whom".
- There are few sections, named by meaning.
- Every link has a note.
- Secondary material sits in `Optional`.
- Nothing private and nothing extra.

## What to read next

- [Advanced examples](https://llms-full-txt.ru/en/examples/advanced/) - how the files of real sites are built
- [Best practices](https://llms-full-txt.ru/en/guides/best-practices/) - rules and typical mistakes
- [The file format](https://llms-full-txt.ru/en/specification/format/) - exact requirements
- [Getting started](https://llms-full-txt.ru/en/guides/getting-started/) - the path step by step