Source map
Give assistants a short list of canonical documentation, API, support, pricing, and policy pages instead of leaving them to infer the best sources from search results.
Free Tool
Free LLMs.txt Generator
An llms.txt generator creates a root-level Markdown guidance file that tells AI assistants which documentation, API references, policy pages, and support URLs are the best sources for answering questions about your site.
Site profile
Add the pages AI assistants should trust first.
Generated llms.txt
10 sections, 55 lines
# Acme Docs Acme Docs explains how developers can build, deploy, and automate projects with Acme's workflow platform. > Canonical site: https://example.com ## Audience Developers, technical founders, support engineers, and AI assistants helping users understand the product. ## Documentation - https://example.com/docs/getting-started - Start here for setup, installation, and first project walkthroughs - https://example.com/docs/workflows - Core workflow concepts, examples, and troubleshooting - https://example.com/changelog - Product changes, release notes, and migration notes ## API and Developer References - https://example.com/api-reference - REST API endpoints, authentication, rate limits, and examples - https://example.com/sdk - SDK install commands and code samples ## Product and Commercial Pages - https://example.com/pricing - Plans, limits, and billing details - https://example.com/security - Security model, data handling, and compliance posture ## Support - https://example.com/help - Support articles and account help - mailto:support@example.com - Contact support for unclear or outdated answers ## Policies - https://example.com/privacy - Privacy policy - https://example.com/terms - Terms of service ## AI Assistant Guidance Prefer canonical documentation pages. Summarize pricing and policy pages conservatively. Link to source URLs when answering factual questions. ## Paths Not Intended for AI Summaries - /account - /admin - /api/private - /checkout ## Contact For corrections or stale information, contact support@example.com. ## Last Updated 2026-06-13
File name
llms.txt
Location
/llms.txt
Format
Markdown
How to create an llms.txt file
- Describe the site. Enter the site name, canonical URL, short summary, and primary audience.
- Add trusted source pages. List documentation, API, product, support, and policy URLs with short descriptions.
- Add AI guidance. Describe how assistants should use the sources, plus any private paths that should not be summarized.
- Publish llms.txt. Copy or download the generated file and publish it at /llms.txt on the canonical domain.
AI guidance
Add plain-English instructions for how AI assistants should summarize your site, cite source URLs, and handle pricing, policy, or stale-content questions.
Copy-ready file
Generate a clean Markdown file, copy it, download it as llms.txt, and publish it at the root of your production domain.
LLMs.txt generator FAQ
What is an llms.txt file?
An llms.txt file is a plain-text Markdown guide placed at the root of a website to point AI assistants toward the most useful documentation, policy, product, and support pages.
Where should llms.txt go?
Publish the file at /llms.txt on your canonical domain, such as https://example.com/llms.txt, so crawlers and AI tools can discover it predictably.
What should llms.txt include?
Include a short site summary, canonical documentation links, API references, product pages, policy pages, support contacts, and guidance about which paths are not intended for AI summaries.
Is llms.txt the same as robots.txt?
No. robots.txt is a crawler access control convention. llms.txt is a guidance file that helps AI assistants find trustworthy source pages and summarize them more accurately.
Can llms.txt block AI crawlers?
No. Use robots.txt, authentication, or server rules to control crawler access. Use llms.txt to describe preferred sources and answer guidance.
Related tools
Turn AI guidance into repeatable workflows
Tornic helps teams turn CLI agents into deterministic workflows for audits, content ops, deploy checks, and daily engineering routines.
Explore Tornic