Setting up llms.txt: a practical guide (and what it won't do for you)

What llms.txt actually is (and isn't)

People navigate a site with menus, images, and layout. AI systems skip all of that — it just gets in the way. The llms.txt is meant to hand them the essentials directly: a plain text file with no design, no navigation, just core facts and links to the pages that hold the real detail.

What matters most is what it isn't. It's not a ranking signal, not a citation guarantee, and not a substitute for good content. Google's John Mueller has said plainly that no Google Search system reads or acts on llms.txt, and Google's own guidance says it neither helps nor hurts. An Ahrefs analysis of roughly 137,000 sites that published one found about 97% saw no measurable referral traffic from it. Treat it as a tidy summary for anyone who does look, not a growth lever.

Where to put the file

The llms.txt lives at the root of your domain — your-domain.com/llms.txt — the same place as your robots.txt file. It has to be reachable as plain text, with no login and no redirect in the way. The format follows a loose Markdown-style convention: a heading with your name, a short description block, then sections sorted by topic with links.

Technically, making the file is trivial — write a text file, fill it in, drop it in the root directory. On most modern site builders that just means the public folder. The real effort isn't technical; it's the discipline of keeping the content short and true.

Step by step

Start with a heading and a two- or three-sentence description: who you are, where you're based, who you serve. Then add sections. One for what you offer, linking to your service pages. One for facts people ask about often — hours, prices, directions. One linking to the pages that answer your most common customer questions.

Write every line so it can stand alone. Instead of "Experience unique moments," write "Boutique hotel with 24 rooms, its own sauna, five minutes on foot from the lake." The first is advertising copy; the second is an answer. Only the second is useful to a machine.

• Add a heading with your company name
• Description block: who, where, for whom (two to three sentences)
• Offering section with links to your service pages
• Facts section: hours, prices, directions, what sets you apart
• Answers section: links to pages that answer real customer questions
• Upload the file as /llms.txt at the root of your domain

A template you can adapt

Use the pattern below as a starting point. Swap in your real facts and cut anything that doesn't apply. Keep it brief — an llms.txt is not a brochure.

For example: start with a name line, then a description block — "We're a family-run business in Rottach-Egern renting e-bikes for tours around Lake Tegernsee." Follow with an offering section linking to pricing and availability, a facts section with hours and daily rates, and an answers section pointing to a page titled "E-bike tours at Lake Tegernsee." The result is a file a machine can scan in seconds.

Common mistakes

The biggest mistake is advertising language. An llms.txt full of adjectives helps no one — it should carry facts, not tone. The second is stale or contradictory information: if the file lists different hours than your website or directory listings, you confuse the machine more than you help it. Keep every source in sync.

The third mistake is publishing it and forgetting about it. When your offering changes, update the llms.txt like you would any other important page. It's a living document, not a one-time checkbox.

What llms.txt can't do

The file is a nice-to-have, not a fix. It doesn't change whether AI systems cite you — that's decided by the content itself, by whether other trustworthy sites mention you, and by whether your pages actually answer the questions people ask. An llms.txt just points to the answers; it can't invent them, and there's no confirmed evidence yet that it moves citation or ranking outcomes.

It works best as one piece of a whole: content worth quoting, a clean technical structure, and an llms.txt tying the two together. That combination is what actually gives a model something to read and something to recommend — the file alone won't get you there.

llms.txt vs. robots.txt

Both files sit in the same directory and are plain text, but they do different jobs. robots.txt controls access — it tells automated visitors what they can and can't look at. It's a gate, not content. llms.txt does the opposite: it summarizes what your site is about and points to your most important answers.

They complement each other but don't substitute for one another. A robots.txt that blocks everything makes you invisible no matter how good your llms.txt is. And the best access rules are pointless if a crawler that does get through finds only marketing copy and no facts. Check both: does robots.txt allow the pages that matter, and does llms.txt actually lead to real answers?

A full example

To make this concrete, here's a full example for a small business. At the top, the name line — say, "Radhaus Tegernsee." Below it, a description block: "Family-run business in Rottach-Egern. We sell and repair bicycles and rent e-bikes for tours around Lake Tegernsee. Same-day workshop service."

Three sections follow. Under "Offering," links to the sales, repair, and e-bike rental pages, each with a short line on what's there. Under "Facts," hours, the daily rental rate, and the address — brief and verifiable. Under "Answers," a link to a page titled "E-bike tours at Lake Tegernsee: routes, prices, equipment" — exactly the content that answers common customer questions.

The result is a file a machine can take in within seconds: who the business is, what it does, where the detail lives. No line is advertising; every line carries information. That's what a good llms.txt looks like.

How to check whether it's working

The first check is trivial: open your-domain.com/llms.txt in a browser. If plain text loads with no error and no redirect, the file is reachable. Then click every link in it — does it lead to a page that actually delivers the answer it promises? Dead or misleading links do more damage than the file does good.

The second check is about content. Read each line as a machine would and ask: is this a verifiable fact or just a mood? Cut anything that's pure marketing. The third check is consistency with your other sources — do the hours in the llms.txt match your website and your directory listings? Contradictions are one of the few things that can actively make the file worse.

In the end, only observation tells you anything. After publishing the file, ask your most important customer questions to a few AI tools again over the following weeks and watch whether your pages come up more. Set expectations honestly: most sites that publish llms.txt see no measurable change in referral traffic from it, so treat any shift you do notice as likely coming from your content and mentions elsewhere, not from the file itself.

Who this is worth the effort for

The payoff isn't spread evenly. Businesses that benefit most are the ones whose strengths translate into clear facts and that live on recommendations — hotels, clinics, law firms, tradespeople, restaurants, local service providers. For them a single AI answer often decides whether someone reaches out, so anything that makes the facts easier to find is worth doing.

The effect is smaller for very large sites with thousands of pages, where one summary file can only cover a fraction of the content. It still won't hurt there, but it's no substitute for a clean structure across the whole site. And for businesses whose value is hard to reduce to facts, the real work is making those strengths verifiable in the first place — the file comes after that.

The honest take: for most small and medium-sized businesses, an llms.txt takes under an hour, costs nothing to host, and can't hurt. It just isn't a proven way to get cited more often — there's no confirmed ranking or visibility benefit today. Do it as basic hygiene, then put your real effort into the content and mentions that actually move the needle.