AI SEARCH (GEO)

Draft an llms.txt file

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

llms-txt-generator.md

Download .md

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.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{SITE_NAME}}
{{SITE_URL}}
{{WHAT_IT_DOES}}
{{PAGE_LIST}}

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.

Questions about this prompt

When is this worth doing at all?

When you have a settled set of pages worth pointing at and want one file describing what each answers. Be honest that support for llms.txt is not confirmed by the major assistant providers and remains contested, so treat it as cheap and speculative rather than as a mechanism you can rely on.

What do I need in front of me?

A page list with real URLs and a one-line purpose for each. The prompt is barred from guessing paths such as /about or /pricing, so anything absent from {{PAGE_LIST}} will not appear at all. Write those purposes as the question the page answers, since the link descriptions are built from them.

What comes back, and what should I check?

A markdown file under 400 words with an H1, a standalone blockquote summary, H2 sections grouped by purpose and a final Optional section, then a list of pages deliberately left out. Read the exclusions list. It is a quick test of whether your sense of which pages matter matches what you supplied.

What is the mistake that costs me?

Generating it once and forgetting it. A file pointing at pages you have since moved or retired is worse than no file, because it advertises dead ends as your best material. Keep it in version control beside the sitemap and regenerate when your top pages change, not on a calendar.