BlogVindbaarheid & contentWhat is llms.txt and does your site need it?

What is llms.txt and does your site need it?

Robots.txt tells search engines where they may go; llms.txt tells AI assistants what your site is. What goes in the file, what it does and doesn't do, and how to set it up.

Bobby van Wordragen·

What is llms.txt?

llms.txt is a text file in the root of your site (for example yoursite.com/llms.txt) that gives AI assistants a short, structured summary of what your site is and which pages matter. Where robots.txt says where crawlers may go, llms.txt says what a language model should know about you. It is a young standard: useful as a summary for assistants such as ChatGPT and Claude, but Google does not use it for AI Overviews or AI Mode.
  • One markdown file with your most important pages and a short description of each.
  • Meant for language models with a limited context window: the essentials without the noise.
  • Honest picture: Google ignores it for its AI features; for other assistants it is a cheap summary.

It gets searched for a lot and explained well surprisingly rarely: llms.txt. Some present it as the key to AI findability, others as hype that does nothing. The truth lies in between, and it can be told quite precisely, including what the file does and doesn't take care of for you.

What goes in an llms.txt

The file is deliberately simple: markdown, starting with the name of your site and a short description, followed by a structured list of your most important pages with one sentence of explanation per link. No scripts, no styling, no marketing: a table of contents for a reader who has no time.

That reader is a language model. An AI assistant that wants to understand your site can't always crawl and parse a hundred pages; an llms.txt gives it the essentials in a single file. Larger sites sometimes also add an llms-full.txt with the full text content of their most important pages, so a model doesn't have to plough through HTML, menus and cookie banners.

What it does do, and what it doesn't

First the honest side: llms.txt is a proposed standard, not an agreement. Nobody can guarantee you that an llms.txt leads to more citations. Anyone selling it as a miracle cure is exaggerating.

Google has now been explicit about it. Its guide to generative AI features (May 2026) states that Google treats llms.txt as an ordinary text file: it does not help you appear in AI Overviews or AI Mode. There, only plain good SEO counts. Other crawlers can still use the file.

Why we switch it on by default anyway: it costs nothing, it can't do any harm, and it solves a real problem. AI crawlers that do visit your site (and they demonstrably do, just look for GPTBot and ClaudeBot in your server logs) get the essentials in a readable form instead of a pile of HTML. Think of it as something for ChatGPT, Claude and Perplexity, not for Google.

How to set it up (and how not to)

By hand it is half an hour's work: create a text file, start with # Name of your site and a blockquote with one sentence about what you do, and below that, per section (## Products, ## Knowledge base), list your most important pages as markdown links with one sentence of explanation. Upload it to the root so it can be reached at /llms.txt.

The pitfall isn't creating it but keeping it up to date: an llms.txt that links to pages that no longer exist, or describes your old range, gives AI assistants exactly the wrong summary. That is why we generate it instead of writing it: on a Neuramerce site, llms.txt is built automatically from your real pages and updated with every change. The file can't go out of date because it isn't a separate file.

So: does your site need it?

If being found matters to you: yes, for the same reason as a sitemap. The investment is minimal, the risk is zero, and it prepares you for a search landscape in which a growing share of questions ends up with an AI assistant instead of ten blue links.

Do make sure the basics are in place first: an llms.txt that points to sloppy pages just summarises sloppiness. Work through the twelve basic tips first, and use the free site scan to check how readable your site currently is for search engines and AI alike.

Frequently asked questions

What is the difference between llms.txt and robots.txt?
Robots.txt says where crawlers may and may not go (access). llms.txt says what a language model should know about your site (content). They complement each other rather than replace each other.
Does llms.txt guarantee that ChatGPT will cite me?
No. It is a young proposed standard without commitments from AI companies, and Google has confirmed it does not use llms.txt for AI Overviews and AI Mode. It is cheap preparation for other assistants, not a miracle cure. The quality of your pages themselves remains decisive.
Where do I put the file?
In the root of your domain, so it can be reached at yoursite.com/llms.txt. It is plain markdown; a text editor is all you need.
What is llms-full.txt?
An extended version with the full text content of your most important pages, so a language model doesn't have to plough through HTML. Useful for documentation-style sites; for most business sites the regular llms.txt is enough.
Do I have to keep llms.txt up to date by hand?
If you write it yourself, yes, and outdated content does more harm than having no file at all. On a Neuramerce site, llms.txt is generated automatically from your real pages and updated with every change.

About the author

Bobby van Wordragen

Bobby van Wordragen

I'm the founder of Neuramerce and have worked in e-commerce since 2004. I started out as an employee, and in 2009 I went out on my own with an agency for web development and online marketing. Until 2015 I worked there for dozens of clients. I then sold the agency because I wanted to focus on my own e-commerce with Hilox Lighting. Grill Bill came later. Both sell products I enjoy because of my hobbies. For more than 22 years I juggled dozens of CMSs, customer service tools, ERP and CRM systems and social media tools, from Magento and Drupal to WordPress and WooCommerce. All that time I wondered why there wasn't simply one system that works well and intuitively, is affordable and is fast. So I started building my own e-commerce platform. I run the migrations myself, from WooCommerce shops with dozens of plugins to stacks of twelve separate tools. I write about what actually happens in practice, including the costs.