llms.txt: what it is and whether your business needs one

What llms.txt is

llms.txt is a proposal published in 2024 (llmstxt.org) for a markdown file at the root of a site. It gives AI tools a short, clean overview: what the site is, and links to the pages that matter, without menus, ads and scripts in the way.

The proposed format is simple:

1. 1An H1 with the site or business name.
2. 2A short summary in a blockquote.
3. 3Optional paragraphs with more detail.
4. 4Sections of links (H2 headings), each link with a short description.

Some sites also publish llms-full.txt, with the full text of key pages in one file.

What it doesn't do

• It doesn't control crawling. Whether AI crawlers may read your site is set in robots.txt and your server or firewall settings.
• It isn't confirmed as a ranking or citation signal. The major search engines haven't said they use it to decide what to show or cite.
• It doesn't replace good pages. If your service pages don't clearly say what you offer, a summary file won't fix that.

So, should you add one?

If your site is already in good shape, adding llms.txt is a small, low-risk step: it costs a few minutes and gives any tool that does read it an accurate summary in your own words. If your site has basic problems (pages not indexed, AI crawlers blocked, unclear service pages), fix those first; they matter far more.

A sample for a small business

A clinic's llms.txt might contain (Kaveri Dental is a made-up example):

• # Kaveri Dental, Indiranagar
• A blockquote: "Family dental clinic in Indiranagar, Bengaluru, offering implants, root canals, braces and cleaning. Open Monday to Saturday."
• ## Treatments with links to each treatment page and a one-line description.
• ## Clinic with links to the about page, the team, prices and contact.

Keep it short, factual and identical to what your pages say.

Where it fits with robots.txt and sitemaps

How to write a good one

• Start with one plain sentence about what your business does, where, and for whom: the same sentence you'd say to a new customer.
• Link only your best pages: services, prices, about, contact, and any guide that answers a common question.
• Describe each link in a few words that say what's on the page, not marketing slogans.
• Use full addresses (https://...) so links work wherever the file is read.
• Keep it current. Remove pages you've deleted and add new ones.

Mistakes to avoid

• Listing every page on the site, which defeats the point of a short summary.
• Claims that aren't on your pages, such as awards or ratings that aren't shown anywhere else.
• Treating it as a substitute for robots.txt rules or for fixing pages Google can't index.

How to check it works

Open yourdomain.com/llms.txt in a browser. It should load as plain text, with your summary at the top and working links. If your site is behind bot protection, check it loads for automated requests too.

Where it sits in your priorities

For a small business, the order is: pages Google can index, AI crawlers allowed in, clear service pages with real details, consistent business details everywhere, and then small extras like llms.txt. Doing the extras first rarely changes anything.

llms-full.txt, the longer companion

Some sites publish a second file, llms-full.txt, with the full text of their key pages in one markdown document. The idea is that an AI tool can read the whole site's useful content in one request. For a small business, the short llms.txt is usually enough; a full version makes sense when you have guides or documentation that people ask assistants about.

If you publish both, generate them from the same source as your pages, so they can't say something different from your site.

Who reads it today

The proposal is public and many sites have adopted it, especially software and documentation sites. Some AI tools and developer tools read it when they're pointed at a site. The major search engines haven't said they use it for ranking or for choosing what to cite, and Google's guidance for AI features doesn't mention it. Treat it as a cheap courtesy to tools that look for it, not as a lever.

A worked example for a restaurant

A restaurant's file (Coastal Table, Kochi, is a made-up example) might read, in plain text:

1. 1A heading with the restaurant name and area.
2. 2A one-sentence summary: Kerala seafood restaurant in Fort Kochi, open for lunch and dinner, reservations for groups.
3. 3A "Menu and prices" section linking the menu page.
4. 4A "Visit" section linking the location, hours and reservations pages.
5. 5An "About" section linking the story of the restaurant and the team.

That's the whole file. Every fact in it should already be on those pages.