Question 1

What is llms.txt?

Accepted Answer

llms.txt is a plain-text file you place at the root of your website (yoursite.com/llms.txt) that tells AI tools and agents which pages matter and how to read them. It uses Markdown: an H1 with your site name, a blockquote summary, and H2 sections containing curated link lists. Think of it as a sitemap written for large language models instead of crawlers.

Question 2

Where do I put the llms.txt file?

Accepted Answer

At the root of your domain, served at https://yoursite.com/llms.txt as text/plain. Many teams also publish an llms-full.txt with the full content inlined, but the curated link list in llms.txt is the place to start.

Question 3

How does the sitemap import work?

Accepted Answer

Paste your sitemap.xml URL (or your site root and we'll try /sitemap.xml). We read the listed pages, group them by URL path into sections, and fetch a capped number of pages to pull in their titles and descriptions. You then edit everything before exporting. Large sitemaps are capped and clearly flagged.

Question 4

How is llms.txt different from a sitemap.xml?

Accepted Answer

A sitemap.xml is written for search-engine crawlers: it lists every indexable URL on your site in XML so bots can discover pages and decide how often to re-crawl them. An llms.txt is written for large language models: it is a curated Markdown file that names your most important pages, groups them into sections, and adds a one-line summary of each, so an AI agent with a limited context window can decide what to read first. A sitemap optimizes for coverage; llms.txt optimizes for relevance and comprehension. They are complementary - keep the sitemap for SEO crawlers and add llms.txt for AI answer engines. Both live at the root of your domain.

Question 5

Is the llms.txt generator free?

Accepted Answer

Yes. No sign up, no limits, no watermarks. The output is plain text you can commit and host anywhere.

Question 6

Does my data leave my browser?

Accepted Answer

The editor itself is entirely client-side. The only network call is the optional sitemap import, which fetches the public pages at the URL you provide and returns the parsed structure - it is not stored.

Question 7

How do I keep llms.txt up to date?

Accepted Answer

Treat it like any other file in your repo: commit it, and update it when your documentation structure changes. Moxie Docs keeps the documentation behind these links current automatically on every merge, so the pages your llms.txt points to stay accurate.

	llms.txt	sitemap.xml
Primary audience	AI agents and large language models	Search-engine crawlers
Format	Markdown (human-readable)	XML
Purpose	Curate the pages that matter, each with a summary	List every indexable URL for discovery
Includes summaries	Yes - one line of context per link	No - URLs and metadata only
Served at	/llms.txt	/sitemap.xml

llms.txt Generator

What goes in an llms.txt

llms.txt vs sitemap.xml

Primary audience

Format

Purpose

Includes summaries

Served at

Frequently asked questions

Your llms.txt is only as good as the docs behind it

llms.txt Generator

What goes in an llms.txt

llms.txt vs sitemap.xml

Primary audience

Format

Purpose

Includes summaries

Served at

Frequently asked questions

What is llms.txt?+

Where do I put the llms.txt file?+

How does the sitemap import work?+

How is llms.txt different from a sitemap.xml?+

Is the llms.txt generator free?+

Does my data leave my browser?+

How do I keep llms.txt up to date?+

Your llms.txt is only as good as the docs behind it