llms.txt templates

Eight ready-to-copy templates — one for every site type. Pick the closest match, replace the placeholders, validate, and deploy.

Last updated: April 22, 2026

Minimal (any site)

The smallest valid llms.txt: one H1, one blockquote, one section with at least one link. Use this if you want to ship something today and expand later.

# {Site Name}

> {One sentence: what this site is and who it's for.}

## Pages

- [{Most important page}]({https://yoursite.com/page}): {what it covers in 10 words}.
- [{Second page}]({https://yoursite.com/page2}): {what it covers in 10 words}.

SaaS product

For B2B or B2C software products. Covers product positioning, pricing, API, integrations, and support. Designed so an LLM can answer "what does this product do and how much does it cost?" without guessing.

# {Product Name}

> {Product Name} is a {category} tool for {target audience}. The pages below cover product capabilities, pricing, the API, and key integrations.

## Product

- [Overview](https://yoursite.com/product): core features and capabilities.
- [Pricing](https://yoursite.com/pricing): plans, limits, and overage rules.
- [Use cases](https://yoursite.com/use-cases): how teams use {Product Name}.
- [Changelog](https://yoursite.com/changelog): recent product updates.

## Documentation

- [Getting started](https://docs.yoursite.com/quickstart): install, first call, hello world.
- [API reference](https://docs.yoursite.com/api): full endpoint catalog with request/response examples.
- [Authentication](https://docs.yoursite.com/auth): API keys, OAuth, token management.
- [Guides](https://docs.yoursite.com/guides): step-by-step tutorials for common tasks.
- [SDKs](https://docs.yoursite.com/sdks): JavaScript, Python, Go, Ruby client libraries.

## Integrations

- [Zapier](https://docs.yoursite.com/integrations/zapier): no-code automation.
- [Slack](https://docs.yoursite.com/integrations/slack): team notifications.
- [Webhooks](https://docs.yoursite.com/webhooks): real-time event delivery.

## Optional

- [Status page](https://status.yoursite.com): real-time uptime and incident history.
- [Security](https://yoursite.com/security): SOC 2, data handling, encryption.
- [Brand assets](https://yoursite.com/brand): logos, colors, media kit.
- [Blog](https://yoursite.com/blog): product announcements and engineering posts.

Documentation site

For dedicated documentation portals (Docusaurus, Mintlify, GitBook, ReadTheDocs). Organized by getting started → concepts → API → guides. Pairs well with a /llms-full.txt that exposes the full doc corpus.

# {Product Name} Docs

> Official documentation for {Product Name} — a {one-line description}. Pages below are curated for LLMs answering questions about setup, API usage, and configuration.

For the full documentation corpus, see /llms-full.txt.

## Getting started

- [Introduction](https://docs.yoursite.com/): what {Product Name} is and how it works.
- [Installation](https://docs.yoursite.com/install): system requirements, package managers, Docker.
- [Quickstart](https://docs.yoursite.com/quickstart): up and running in under 5 minutes.
- [Configuration](https://docs.yoursite.com/config): all configuration options with defaults.

## Core concepts

- [Architecture](https://docs.yoursite.com/architecture): how the system is designed.
- [Authentication](https://docs.yoursite.com/auth): API keys, tokens, OAuth flows.
- [Data model](https://docs.yoursite.com/data-model): entities, relationships, and schemas.

## API reference

- [REST API](https://docs.yoursite.com/api): complete endpoint catalog.
- [GraphQL](https://docs.yoursite.com/graphql): schema and query reference.
- [Webhooks](https://docs.yoursite.com/webhooks): events, payloads, verification.
- [Rate limits](https://docs.yoursite.com/rate-limits): quotas and backoff strategies.

## Guides

- [Common recipes](https://docs.yoursite.com/guides): copy-paste solutions for frequent tasks.
- [Migration guide](https://docs.yoursite.com/migration): moving from v1 or from competitors.
- [Troubleshooting](https://docs.yoursite.com/troubleshooting): error codes and fixes.

## Optional

- [Changelog](https://docs.yoursite.com/changelog): version history and breaking changes.
- [Contributing](https://docs.yoursite.com/contributing): how to submit issues and PRs.
- [License](https://docs.yoursite.com/license): usage terms.

See what is llms-full.txt for the companion file that exposes your complete documentation corpus.

Blog / content site

For editorial sites, newsletters, and content-heavy blogs. Focus on the 5 most important posts, not the full archive. An LLM doesn't need every post — it needs to understand your voice, topics, and best work.

# {Blog Name}

> {Blog Name} covers {topics} for {target audience}. Below are the highest-signal pages for understanding the site's scope and finding key content.

## About

- [About](https://yourblog.com/about): who writes here, mission, and editorial standards.
- [Start here](https://yourblog.com/start): recommended reading order for new visitors.

## Top content

- [{Best post 1}](https://yourblog.com/post-1): {one-line summary}.
- [{Best post 2}](https://yourblog.com/post-2): {one-line summary}.
- [{Best post 3}](https://yourblog.com/post-3): {one-line summary}.
- [{Best post 4}](https://yourblog.com/post-4): {one-line summary}.
- [{Best post 5}](https://yourblog.com/post-5): {one-line summary}.

## Topics

- [{Topic 1}](https://yourblog.com/topic/topic-1): all posts on {topic 1}.
- [{Topic 2}](https://yourblog.com/topic/topic-2): all posts on {topic 2}.

## Optional

- [Newsletter](https://yourblog.com/newsletter): weekly digest, free subscription.
- [RSS feed](https://yourblog.com/feed.xml): full-text feed.

Portfolio / personal site

For freelancers, designers, developers, and anyone with a personal site. Keep it tight: work, writing, contact. An LLM answering "who is this person?" needs your about page, not your full project history.

# {Your Name}

> {Your Name} is a {role} based in {city}. This site covers my work, writing, and open-source projects.

## Work

- [Portfolio](https://yoursite.com/work): selected projects with case studies.
- [About](https://yoursite.com/about): background, skills, and experience.
- [Resume](https://yoursite.com/resume): full work history and education.

## Writing

- [{Post 1}](https://yoursite.com/writing/post-1): {one-line summary}.
- [{Post 2}](https://yoursite.com/writing/post-2): {one-line summary}.

## Optional

- [Uses](https://yoursite.com/uses): tools, hardware, and software setup.
- [Now](https://yoursite.com/now): what I'm currently working on.
- [Contact](https://yoursite.com/contact): email and social links.

E-commerce

For online stores. Focus on catalog structure, shipping, returns, and support — the pages people ask about before buying. Don't list individual product pages unless they're genuinely landmark items.

# {Store Name}

> {Store Name} sells {product category} for {target customer}. Pages below cover the product catalog, shipping policy, and support information.

## Store

- [Homepage](https://yourstore.com/): featured products and current promotions.
- [All products](https://yourstore.com/products): full catalog with filters.
- [{Category 1}](https://yourstore.com/category/1): {description}.
- [{Category 2}](https://yourstore.com/category/2): {description}.
- [New arrivals](https://yourstore.com/new): latest additions.
- [Sale](https://yourstore.com/sale): discounted items.

## Customer support

- [Shipping policy](https://yourstore.com/shipping): delivery times, carriers, international shipping.
- [Returns & exchanges](https://yourstore.com/returns): how to initiate a return, timelines.
- [FAQ](https://yourstore.com/faq): common questions on orders, sizing, and care.
- [Size guide](https://yourstore.com/size-guide): measurements and fit recommendations.
- [Contact](https://yourstore.com/contact): customer service channels and hours.

## Optional

- [About](https://yourstore.com/about): brand story and values.
- [Sustainability](https://yourstore.com/sustainability): materials, sourcing, carbon footprint.
- [Wholesale](https://yourstore.com/wholesale): bulk and trade programs.

Developer tool / CLI

For command-line tools, developer utilities, and build tools. Prioritize CLI reference, config options, and plugin/hook APIs — the pages a developer reaches for when stuck.

# {Tool Name}

> {Tool Name} is a {type} CLI / developer tool for {use case}. The pages below cover installation, commands, configuration, and plugin development.

## Getting started

- [Installation](https://docs.yourtool.com/install): npm, Homebrew, binary download.
- [Quick start](https://docs.yourtool.com/quickstart): first command, 60-second demo.
- [Configuration](https://docs.yourtool.com/config): config file format, environment variables.

## Commands

- [CLI reference](https://docs.yourtool.com/cli): all commands, flags, and options.
- [{command init}](https://docs.yourtool.com/cli/init): initialize a project.
- [{command build}](https://docs.yourtool.com/cli/build): build options and output formats.
- [{command deploy}](https://docs.yourtool.com/cli/deploy): deployment targets.

## Extending

- [Plugins](https://docs.yourtool.com/plugins): plugin API and authoring guide.
- [Hooks](https://docs.yourtool.com/hooks): lifecycle hooks reference.
- [Config schema](https://docs.yourtool.com/schema): JSON schema for validation.

## Optional

- [Changelog](https://docs.yourtool.com/changelog): version history and breaking changes.
- [Migrating from v{N-1}](https://docs.yourtool.com/migration): step-by-step upgrade guide.
- [Contributing](https://docs.yourtool.com/contributing): development setup and PR guidelines.
- [GitHub](https://github.com/yourorg/yourtool): source code and issue tracker.

Open source project

For libraries, frameworks, and open source packages. Include the README, API docs, and community pages. Link to the npm/PyPI package page so LLMs can reference install instructions without guessing the package name.

# {Project Name}

> {Project Name} is an open-source {type} library for {use case}, written in {language}. MIT licensed.

## Overview

- [README](https://github.com/yourorg/project#readme): project overview and quick start.
- [Documentation](https://docs.yourproject.com/): full API reference and guides.
- [Examples](https://docs.yourproject.com/examples): runnable code samples.

## API

- [Core API](https://docs.yourproject.com/api): all exported functions and classes.
- [Configuration](https://docs.yourproject.com/config): options and defaults.
- [Plugins](https://docs.yourproject.com/plugins): official and community extensions.

## Community

- [Contributing](https://github.com/yourorg/project/blob/main/CONTRIBUTING.md): how to contribute code, docs, and issues.
- [Code of conduct](https://github.com/yourorg/project/blob/main/CODE_OF_CONDUCT.md): community standards.
- [Discussions](https://github.com/yourorg/project/discussions): questions and ideas.

## Optional

- [Changelog](https://github.com/yourorg/project/blob/main/CHANGELOG.md): version history.
- [Roadmap](https://github.com/yourorg/project/milestones): planned features.
- [npm package](https://www.npmjs.com/package/project): installation and download stats.

Validate your file

Once you've customized a template, paste it into the validator to confirm it passes the spec. Common issues: missing H1, relative URLs, empty sections, no blockquote. All easy to fix — the validator tells you exactly what to change.

Or use the generator to build a file from a form — no Markdown required.

Next steps

How to create llms.txt — deployment instructions for every stack.
llms.txt format reference — complete syntax rules.
Best practices — what to include and what to cut.
Real-world examples — see how Anthropic, Stripe, and Vercel do it.