April 3, 20266 min read

llms.txt Template: 5 Ready-Made Examples for SaaS, Agencies, E-commerce, and Local Business

Ready-to-use llms.txt templates for different website types: SaaS, digital agency, online store, local business, and personal brand. What to include, how to structure it, and what mistakes to avoid.

Vladislav Puchkov

Founder of GEO Scout, GEO optimization expert

For the conceptual background, see what llms.txt is and why your website needs it. This article focuses on the practical question: what exactly should you put into the file so that it becomes useful for AI systems.

The principle of a good llms.txt

A useful llms.txt answers three questions:

What is this site and what does the company do?
Which pages matter most for understanding the business?
Which pages are the most useful AI-citable resources?

Bad llms.txt files:

dump URLs without context
do not separate critical pages from secondary ones
duplicate the sitemap
provide no navigational clues

Good llms.txt files:

group pages by purpose
explain what each section is for
put the highest-value pages near the top

Base llms.txt structure

For many websites, a simple structure works well:

# Company Name
 
Short company and product description.
 
## Main pages
- /about — official company overview
- /pricing — plans and terms
- /contact — contact details
 
## Products or services
- /product-a — product page
- /service-b — service page
 
## Helpful resources
- /faq — common questions
- /blog/... — expert content
- /docs/... — documentation or knowledge base

After that, the file should be adapted to the business model.

Template 1: llms.txt for SaaS

For SaaS, the most valuable pages are usually:

product overview
pricing
integrations
docs
security / compliance
FAQ

# TaskFlow
 
TaskFlow is a project management platform for IT teams in Russia and CIS.
 
## Core pages
- /about — company facts, team, market focus
- /pricing — current plans and feature limits
- /security — security practices and certifications
 
## Product
- /product — overview of the platform
- /features — key feature breakdown
- /integrations — supported integrations
 
## Documentation
- /docs — product documentation
- /help — knowledge base and support articles
- /api — API reference
 
## Buying and evaluation
- /compare/taskflow-vs-jira — competitor comparison
- /faq — buyer questions and answers
- /case-studies — implementation examples

Why this works: SaaS buying queries are often comparative. AI systems rely not only on the homepage, but also on docs, pricing, integrations, and proof pages.

Template 2: llms.txt for a digital agency

For agencies, AI usually needs to understand:

specialization
services
proof of work
team expertise
methodology

# AgencyName
 
AgencyName is a digital agency focused on SEO, GEO, and performance marketing for B2B and e-commerce companies.
 
## Company
- /about — team, expertise, markets
- /contact — contacts and locations
 
## Services
- /services/seo — SEO services
- /services/geo — GEO services
- /services/content-marketing — content production
 
## Proof
- /cases — measurable case studies
- /reviews — client testimonials
- /blog — expert articles and research
 
## Buying support
- /pricing — service packages
- /faq — common client questions

The key point: if the agency has no proof, llms.txt alone will not solve anything. It can only help AI systems reach the evidence faster.

Template 3: llms.txt for e-commerce

For online stores, the strongest pages are not just product cards:

category pages
shipping
payment
return policy
brand pages
buying guides

# StoreName
 
StoreName is an online shop selling electronics across Russia.
 
## Main pages
- /about — store overview and trust signals
- /delivery — shipping terms and regions
- /payment — payment methods
- /returns — return and warranty policy
 
## Catalog
- /catalog — product categories
- /catalog/laptops — laptops category
- /catalog/smartphones — smartphones category
- /brands — brand pages
 
## Helpful content
- /faq — customer questions and answers
- /blog — buying guides and comparisons
- /contacts — support contacts and pickup points

If you sell complex products, include comparison and buying-guide pages in llms.txt. AI often uses those resources for “what should I choose?” prompts.

Template 4: llms.txt for a local business

For local businesses, AI needs to understand:

where the company is located
what services it provides
which areas it serves
how to contact or book

# ClinicName
 
ClinicName is a private dental clinic in Moscow.
 
## Main pages
- /about — clinic overview, doctors, licenses
- /contacts — address, phone, map, working hours
 
## Services
- /services/implantation — dental implantation
- /services/cleaning — professional cleaning
- /services/braces — orthodontics
 
## Trust and answers
- /doctors — specialist profiles
- /prices — current prices
- /faq — common patient questions
- /reviews — patient reviews

This is especially useful in categories where AI often makes local recommendations: clinics, restaurants, legal firms, and service studios.

Template 5: llms.txt for a personal brand

For a personal brand, the file should connect identity, expertise, and proof:

# Vladislav Puchkov
 
Vladislav Puchkov is the founder of GEO Scout and a specialist in Generative Engine Optimization.
 
## Core pages
- /about — biography, expertise, speaking, and media
- /contact — contact details and social profiles
 
## Proof of expertise
- /cases — selected client or product cases
- /blog — expert articles and research
- /speaking — talks, interviews, podcasts
 
## Helpful pages
- /services/consulting — consulting offer
- /faq — common GEO questions

This is particularly useful when expertise is spread across multiple formats: articles, interviews, podcasts, and talks.

What not to put into llms.txt

Do not overload the file with pages that do not help answer user questions:

legal boilerplate
every catalog URL
empty tag archives
outdated campaign landing pages
low-value utility pages

llms.txt should be a curated map, not a raw export of site URLs.

How often to update llms.txt

A reasonable update cycle:

quarterly for a standard corporate site
after launching new products or services
after restructuring docs, FAQ, or the blog
after publishing new case studies or comparisons

If your information architecture changes, update llms.txt immediately.

Pre-publish checklist

The file starts with a clear company description
Pages are grouped by purpose, not dumped as a flat list
Product, service, docs, FAQ, About, and Contact are included
High-citation-potential pages are near the top
Outdated or low-value pages are excluded
The file matches the live site structure

Частые вопросы

What should always be included in llms.txt?

A useful llms.txt should include a short company description, the main sections of the site, links to product or service pages, documentation, FAQ, blog resources, contact pages, and any usage notes that help AI systems navigate the site.

Can one llms.txt template work for every website?

A base structure can be reused, but the content should vary by business model. SaaS sites need docs and integrations, e-commerce sites need categories and service pages, and local businesses need services, addresses, and trust signals.

Does llms.txt replace robots.txt or sitemap.xml?

No. llms.txt does not replace robots.txt or sitemap.xml. It complements them as a navigation layer for AI systems by highlighting the most useful pages rather than controlling indexing.