What Is an llms.txt File and How To Write One

What an llms.txt file is

An llms.txt file is a plain text file you place at the root of your website. It tells AI engines what you do, who you serve, and which pages matter most.

Think of it as a short map written for machines. A person browses your site and figures things out, while a model often samples a few pages and moves on.

The format is simple. It is plain text with a few headings and a list of links, each with a short note.

Why llms.txt helps AI visibility

AI engines work under a budget. They cannot read every page on every site, so they take shortcuts.

When the file states your category and your buyer in the first lines, the model starts from a strong base. It knows what you are before it reads a single marketing page.

This is one of the fastest answer engine optimization wins available. It takes an afternoon, and it removes the guesswork that makes models recommend a clearer competitor.

How to write your llms.txt

Start with one heading that names your product. Under it, write one or two plain sentences that say what you do and who you serve.

Then add a short list of your most important pages. For each one, write the link and a brief note on what the reader will find there.

Keep the language plain and honest. Name your category, your main features, your pricing page, and your best proof.

A simple shape to follow looks like this:

• A title line with your product name
• One or two sentences on what you do and who you serve
• A list of key pages, each with a short note
• A short section for docs, pricing, and contact

Where to put the file

Save the file as llms.txt and place it at the root of your domain. It should load at yoursite.com/llms.txt with nothing else in the path.

That root location matters. It is the first place AI engines look, the same way they look for robots.txt.

After you upload it, open the address in a browser to confirm it loads as plain text.

Common mistakes to avoid

The most common mistake is writing it like an ad. Marketing language gives a model nothing solid to hold, so write in plain, checkable statements.

The second mistake is letting it go stale. When you change pricing or add a flagship feature, update the file so the map still matches the territory.

The last mistake is skipping the rest of the work. An llms.txt file helps engines read you, but your homepage, your FAQ schema, and your comparison pages still have to do their part. For the full method, read the Answer Engine Optimization Playbook.