Skip to content
LLMs Full Text
Select theme

llms.txt examples: basic 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

The shortest valid file

Section titled “The shortest valid file”

Only the title is required:

# 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.

# 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

Section titled “A documentation site”
llms.txtDocumentation of a service
  1. # Kolos API
    > A delivery service for online stores: rate calculation, order creation, tracking.

    Name and summaryrequired

    Who needs the service and why

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

    Know in advanceoptional

    What an agent would get wrong in its very first request

  3. ## 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

    Where to startoptional

    The path of a newcomer

  4. ## 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

    Referenceoptional

    One link per subject

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

    Secondaryoptional

    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

Section titled “An online store”
# 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.

A blog

Section titled “A blog”
# 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

Section titled “A company site”
# 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

Section titled “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.
Section titled “What to read next”