# Draft an llms.txt file

> Use when you want a structured llms.txt pointing assistants at your most useful pages.

## Fill in before running

- `{{SITE_NAME}}`
- `{{SITE_URL}}`
- `{{WHAT_IT_DOES}}`
- `{{PAGE_LIST}}`

## Prompt

```
You are drafting an llms.txt file for a website.

Site: {{SITE_NAME}} at {{SITE_URL}}
What the site does: {{WHAT_IT_DOES}}
Page list with URLs and one-line purposes: {{PAGE_LIST}}

Produce a markdown file in this structure:
- An H1 with the site name.
- A blockquote of one or two sentences describing what the site is, written so it stands alone.
- A short paragraph of context if needed, no more than 60 words.
- H2 sections grouping links by purpose (for example Docs, Product, Pricing, Policies, About). Each link as "- [Title](URL): one clause on what the page answers".
- A final H2 called Optional for lower priority pages.

Then, separately, list any pages from {{PAGE_LIST}} you deliberately left out and why.

Constraints:
- Use only URLs present in {{PAGE_LIST}}. Do not guess paths such as /about or /pricing.
- Link descriptions must say what question the page answers, not what section it is in.
- Keep the whole file under 400 words unless the page list forces otherwise.
- Plain ASCII, no decorative characters.
```

## Getting a better result

- Serve it at /llms.txt as plain text and keep it in version control alongside your sitemap.
- Descriptions that name a question outperform descriptions that name a page type.
- Regenerate whenever your top pages change; a stale file points assistants at dead ends.

---

From the QuQi prompt library - https://www.quqi.io/prompts/llms-txt-generator