LLMs.txt Template
Ready-to-edit Markdown files
LLMs.txt Template and Examples
Choose a practical llms.txt template for your website type, customize the important details, review the live Markdown, then copy or download the file.
- Six website templates
- Editable live preview
- Runs in your browser
Template builder
Choose and customize a template
Website type
6 templatesThree practical steps
How to use an LLMs.txt template
Start with a structure that matches the website, then replace every sample resource with a deliberate, useful page.
- 1
Choose the closest template
Select the website type that best matches your content. The sections are starting points, not mandatory categories.
- 2
Customize the important details
Add the project name, canonical website URL, concise summary, and any context a reader needs before following links.
- 3
Replace, validate, and publish
Edit every sample link, validate the final Markdown, and publish the file at a stable public location such as
/llms.txt.
File anatomy
What belongs in an LLMs.txt template?
The proposed format is concise Markdown. It begins with one H1 naming the site or project. A short blockquote can summarize the resource, followed by optional context and H2 sections containing Markdown links.
- One clear H1 at the beginning
- A short, factual blockquote summary
- Optional context that prevents misunderstanding
- Descriptive H2 resource groups
- Absolute Markdown links with useful descriptions
- An
Optionalsection for secondary material
Choose deliberately
Which template should you use?
The best template is the smallest one that accurately represents the website’s most useful public resources.
Minimal website
Use for a small business, campaign, portfolio, landing page, or single-purpose site with only a few essential destinations.
SaaS or product
Organize product explanations, features, pricing, onboarding, documentation, security, and customer support.
Documentation portal
Prioritize getting-started guides, conceptual docs, API references, code examples, migration notes, and changelogs.
Ecommerce store
Highlight important collections, buying guides, size or compatibility help, delivery, returns, and customer service.
Publisher or blog
Group evergreen guides, main topics, editorial standards, authors, archives, and selected recent or foundational content.
Local business
Present services, service areas, locations, booking information, pricing guidance, FAQs, and contact details.
Quality over quantity
How to improve a copied example
A template becomes useful only after its sample text is replaced with accurate, curated information. Avoid turning the file into a second sitemap or an unfiltered list of every URL.
- Use canonical HTTPS URLs
- Write link labels that identify the destination
- Add brief descriptions when the destination is not obvious
- Remove duplicate, thin, outdated, or private pages
- Keep essential resources outside the Optional section
- Update the file when important URLs or products change
Private by design
Your template stays in the browser
The fields, generated Markdown, edits, copy action, and download are processed locally in the current browser tab. This page does not need to send your draft to a server.
Refreshing or closing the page clears unsaved work unless the browser restores form content automatically.
Continue your workflow
Related LLMs.txt tools
Use the template for a quick start, or switch to a guided tool for a more detailed implementation.
Common questions
LLMs.txt template FAQs
Practical answers for choosing, editing, and publishing a template.
What is an LLMs.txt template?
It is a reusable Markdown starting point containing the main structural elements of an llms.txt file. You replace the sample project details, sections, links, and descriptions with accurate information from your own website.
Is there one official template for every website?
No. The proposal defines a general order and Markdown structure, but section names and resource choices depend on the website. A documentation portal and an ecommerce store should not use identical link groups.
Which parts of the file are required?
The current proposal identifies an H1 containing the project or site name as the required element. A blockquote summary, additional context, and H2 resource sections are part of the recommended structure.
Should I include every page from my sitemap?
Usually not. The file should curate useful destinations rather than duplicate an XML sitemap. Include high-value public pages and omit thin, repetitive, outdated, private, or low-priority URLs.
What is the Optional section used for?
The section named Optional contains secondary resources that may be skipped when a shorter context is preferred. Essential documentation or product pages should normally appear in earlier sections.
Can I edit the generated template?
Yes. The live output is an editable text area. You can change section names, links, descriptions, and any other Markdown before copying or downloading the file.
Where should I publish the completed file?
The proposal primarily describes a file at the root path, such as https://example.com/llms.txt, and also permits a file in a subpath. Keep the chosen URL public and stable.
Does using a template improve Google rankings?
No ranking improvement is guaranteed. Google states that its Search systems do not use llms.txt specially and that maintaining the file neither positively nor negatively affects Google Search visibility or rankings.
Start with a clean structure