EN
Language · same page NLNederlands/llms-txt-uitleg-voordelen-en-advies-de-toekomst-van-seo/ ENEnglish (UK)/en/llms-txt-explanation-benefits-and-advice-the-future-of-seo/ ESEspañolnot translated yet We do not remember your choice and never redirect you automatically.
DOC.K · knowledge base · AI and SEO reg. L.000 · llms.txt explained

Llms.txt explained: the benefits, the limits, and our advice for the future of SEO

Llms.txt is a text file in the root of your website that is supposed to tell AI systems such as ChatGPT, Claude and Perplexity which content on your site is worth the most. Supposed to, because that is the honest part straight away: it is a proposal from 2024, not an official standard, and no large AI company has confirmed that it actually uses the file. Below you can read exactly what llms.txt does and does not do, how to write one in ten minutes, and when your time is better spent somewhere else.

Download the llms.txt skill ↓4.0 KB · zip with SKILL.md · builds a correct llms.txt for your site · for Claude and Codex · MIT licence · free, no account needed
CLAUDE CODE
  1. Unpack the zip into ~/.claude/skills/ (or .claude/skills/ in your project).
  2. Claude then recognises the skill on the subject by itself.
  3. Or call it directly with /llms-txt-generator.
CLAUDE.AI
  1. Go to Customize and then Skills.
  2. Upload the zip there as a skill.
  3. Or paste the contents of SKILL.md into the project instructions of a Project.
CODEX
  1. Open the file SKILL.md from the zip.
  2. Paste the contents into your AGENTS.md, or put it in your repository as a separate file and refer to it from AGENTS.md.
  3. Codex reads it along at every session.
Section 01 · The file

What is llms.txt and what does it look like?

reg. L.001

The idea is simple. Language models have a limited context window and handle clean text better than HTML full of navigation, scripts and pop-ups. A small markdown file in a fixed place gives an AI assistant the core of your site in one go: who you are, and where your best content sits. Think of it as a sitemap, but selected instead of complete, and written for models instead of crawlers.

FIG.01: What an llms.txt looks like, line by linesheet 1/4
theseo.nl/llms.txt · markdown · plain text
# TheSEO
> Dutch agency for visibility, in Google and in AI answers. Guides, free tools and downloadable skills.
 
## Guides
- [Local SEO checklist](https://theseo.nl/lokale-seo-checklist-2026/): step by step plan for local visibility
- [Technical SEO](https://theseo.nl/en/technical-seo/): speed, crawling and indexing explained
 
## Tools
- [Free SEO scan](https://theseo.nl/en/gratis-seo-scan/): 24 checkpoints, results straight away
 
## Optional
- [About us](https://theseo.nl/en/about-us/): background of the agency
Four fixed parts. An H1 with the name of your site (the only required element), a blockquote with a summary in two sentences, then H2 headings per category with links plus a one line description, and optionally a section called Optional with links a model may skip when space is tight. That is all there is to it.
Select, do not listAn llms.txt is not a second sitemap. Where sitemap.xml lists every page, llms.txt points only at your best work: the ten to twenty five pages that answer real questions. Anyone who tips their whole site into it makes the file useless for exactly the purpose it was invented for: finding the core quickly.
There is a big brother as wellBesides llms.txt the proposal also describes llms-full.txt: a variant that holds the full content rather than the links. That one mainly makes sense for documentation sites, where a model can read the entire manual in one go. For an ordinary company website the index variant is more than enough.
Section 02 · The family

Robots.txt, sitemap.xml and llms.txt: three jobs

reg. L.002

The three files in your root look alike but each does something different, and only one of the three is a proposal without confirmed readers. Mix them up and you start expecting things from llms.txt that it cannot deliver: it blocks nothing, it manages no crawl budget and it replaces no sitemap.

FIG.02: Three files in the root, side by sidesheet 2/4
FILE 01 · ROBOTS.TXT The doorkeeper Controls access: which crawler may go where. This is also where you keep out training bots such as GPTBot or Google-Extended, if that is what you want. It is the only one of the three files that can hold anything back.
JOBcontrolling access for crawlers
READ BYevery well behaved bot, from Googlebot to GPTBot
SINCE1994 as a convention; formally recorded since 2022
widely supported and documented
FILE 02 · SITEMAP.XML The floor plan Lists which pages exist and when they were last updated. Search engines use it to crawl your site efficiently. Here completeness is the whole point: everything that may be indexed is in there.
JOBlisting pages for crawling
READ BYsearch engines, demonstrably and daily
SINCE2005, open standard at sitemaps.org
widely supported and documented
FILE 03 · LLMS.TXT The invitation Points out your best content for language models, with a description and context. It blocks nothing and it lists nothing exhaustively: it selects. Invented for the moment an AI puts an answer together live and needs a reliable source fast.
JOBpointing out the best content for AI
READ BYunconfirmed; no large company has committed to it
SINCE2024, proposal at llmstxt.org
proposal, not a standard
What this means for your prioritiesRobots.txt and sitemap.xml are foundations: mistakes there demonstrably cost you visibility. Llms.txt is an experiment on top of that foundation. If your technical base is not sound yet, start with technical SEO and let the free SEO scan check the 24 basics first.
Llms.txt is not a lock on the doorIf you do not want your content used for AI training, you arrange that in robots.txt with the user agents the AI companies document for that purpose. Llms.txt has no part in it: it is an invitation, not a shield. Anyone using it as protection is protecting nothing.
Section 03 · The status

A proposal, not a standard

reg. L.003

This is the part most articles about llms.txt skip, and precisely the part you need to know before you put time into it. The file has existed since September 2024, there is plenty of tooling to make one, but to this day there is no confirmation that a large AI system uses it in production. That may change. It may also quietly die off, the way earlier well meant files did.

FIG.03: The short history of a proposalsheet 3/4
SEP 2024 · THE PROPOSAL Jeremy Howard publishes llmstxt.org The co-founder of Answer.AI proposes the format: markdown, a fixed place in the root, selected links with context. The aim: bring language models with a limited context window to the core of a site quickly.
2025 · THE TOOLING Generators, plugins and directories Documentation platforms start generating the file automatically, SEO plugins add support and directories such as llmstxt.site collect sites that have one. An ecosystem of makers appears.
2025 · THE CAVEAT Google shrugs John Mueller of Google publicly compares llms.txt to the keywords meta tag: in his view no AI system uses the file. None of the large companies contradicts that with a commitment.
TODAY · YOUR CHOICE Small file, unproven effect So there are plenty of makers, but no confirmed readers. What is left is a cost and benefit judgement: it costs little, it can do no harm as long as you maintain it, and it is ready if adoption ever arrives.
Nuance you will not read anywhere else: some AI companies publish an llms.txt for their own documentation. That is not the same as confirming that their models read the file on your site. The first is using a format, the second is supporting a format. Only the second would make llms.txt a standard.
1L.01 · file, in one fixed place: /llms.txt in your root
2L.02 · variants in the proposal: llms.txt and llms-full.txt
0L.03 · large AI companies that have confirmed they read it
2024L.04 · year of the proposal, published at llmstxt.org
L.01 to L.04 · properties of the proposal itself, not measurements. How we do measure AI visibility is set out at the AI Index.
Section 04 · The decision

Should you do anything with it?

reg. L.004

The honest judgement is not a yes or a no for everybody. It depends on the kind of site you have and on what you expect. Four situations, four answers. The thread running through them: do it for the right reason, and do not count on a file that may never be read.

FIG.04: Four situations, four honest answerssheet 4/4
DO IT You have a knowledge base, documentation or a lot of guides This is the scenario the proposal was invented for. You have content with lasting value and a logical split into categories. Writing an llms.txt costs you half an hour with the free generator and your selection is ready for the moment readers do arrive.
CAN WAIT You have a small brochure site of five pages A model that has to understand five clean pages does not need an index. Your time pays off better in the content itself: make sure every page answers one question really well. Start at improving SEO and come back here later.
WRONG REASON You expect it to lift your rankings Then you will be disappointed. Llms.txt is not a ranking factor, Google has nowhere said that it counts, and it replaces no structured data, metadata or sitemap. Everything that demonstrably does count is in the local SEO checklist and at technical SEO.
DO IT, WITH UPKEEP You want to be ready for search through AI Fine reason, with one condition: upkeep. An llms.txt that points at outdated or dead pages does more harm than no file at all, because if a model ever does read it, you are reading it the wrong things. Plan a quarterly check, just as you do for your sitemap.
DOC.01

What llms.txt does not do, and what does handle that

Knowing what the file is not matters just as much as knowing what it is. Llms.txt blocks no crawlers and no bots: every bot that wants to read your site can carry on doing so, with or without an llms.txt. Nor does it decide whether your content is used for AI training. There are other, properly documented mechanisms for that: OpenAI describes the user agent GPTBot with which you keep training crawlers out in robots.txt, and Google documents Google-Extended for the same purpose with Gemini.

So anyone who wants to shield their content arranges that in robots.txt and not in llms.txt. What we allow AI systems to do with the content of this site is a separate choice, and it is written out in our AI policy. The two files get lumped together in article after article, and that is exactly how site owners end up with a false sense of control.

It has no effect on your rankings in Google either. There is no indication at all that llms.txt counts in ordinary search results, and Google has hinted more than once that it does nothing with it. For AI Overviews, the AI answers at the top of Google, there is no documented relationship with llms.txt either: those answers come about through the ordinary crawling and indexing systems. What AI Overviews mean for your visibility, and what you can and cannot steer there, we have set out separately in the article on AI Overviews and local SEO.

Finally, the file replaces no SEO fundamentals. Structured data remains the way you tell machines what a page is, your metadata still decides how you appear in results, and your sitemap remains the file that is demonstrably read every day. A handy self test: our AI snippet previewer shows what your page looks like when a machine summarises it. If that picture is already messy, an llms.txt will not fix it; the page itself is next in line.

DOC.02

How to write an llms.txt that holds up

Start with the selection, because it decides everything else. Walk through your site and pick the pages that answer a real question or document real knowledge: guides, explainers, tools, documentation. A good rule of thumb is ten to twenty five links. Product pages, campaign pages and anything that will be out of date in three months you leave out.

For every link you write a one line description that says factually what a reader will find there. No marketing language: a language model has no use for the word leading, but it does have use for being told that a page holds a step by step plan for local visibility. The blockquote at the top describes your site the way an outsider would summarise it, not the way you sell it yourself.

Then the building. You can do that by hand in any text editor, but our free llms.txt generator is quicker: you enter your subjects and categories and the tool sets up the structure for you, including the right order of H1, blockquote and category blocks. Working in Claude or Codex? The downloadable skill at the top of this page does the same in your own environment: it asks you for your site details, selects strictly and hands over the file together with placement and maintenance instructions.

You save the result as llms.txt in the root of your domain, straight after your domain name. Then check in your browser that the file is shown as plain text and not as a download or an error page.

And then the part everybody skips: upkeep. An llms.txt is a promise about what your best content is, and promises go stale. Plan a ten minute check every quarter: do all the links still work, are the pages described still current, and is there new content that deserves a place. If in the meantime you want to know whether anything is happening at all with your file, look in your server logs to see whether the path /llms.txt is being requested and by which user agents. That is not science, but it is the only real measurement that exists at this moment. Everything beyond it is speculation, ours just as much as that of anyone who tells you otherwise.

DOC.03

Llms.txt in the bigger story: AI visibility

The question behind llms.txt is bigger than the file itself: how do you make sure AI systems know your company, name it and cite it? More and more people put their question to an assistant instead of a search box, and the answer they get comes from training data and from sources fetched live. On the first you have hardly any influence, on the second you do: with content that really answers a question, a clean technical base and a consistent brand story.

Whether a model already knows your name today you can test in thirty seconds with the free AI brand checker: it puts a question about your industry to a language model and looks at whether your company name appears in the answer.

Want to follow it more systematically? Then look at the AI Index: our running measurement in which we track per industry which Dutch companies a language model names in answer to common questions, with the movement over the months. There you see the playing field of which llms.txt is a tiny part. Would you rather have that measured for your own company than read it off an index? That is what our service AI visibility does: first the measurement, then the work, and no promise of a place in an answer.

Because let us keep the proportions honest: whether AI names you depends on what has been written about you, how consistently your name and story appear online and how good your content is. Google also works with signals such as brand trust, which we wrote about in the article on preferred sources and brand trust. A small text file in your root does not change that balance of power, and we would rather say so than pretend otherwise.

What is shifting: AI is beginning not only to answer but also to act. Google is experimenting with agents that search and even buy on behalf of a customer, and that puts entirely different demands on your site than a classic visitor does, as we set out in agentic commerce.

In that playing field a readable, structured and honest web of pages is your best preparation. Llms.txt fits that direction, and that is why we think it is worth the ten minutes of work, even without proof that it is read today. Anyone who wants to go deeper, or wants to teach their own team how AI deals with web content, can turn to our AI training or the service AI and automation.

DOC.04 · FAQ

Frequently asked questions about llms.txt

Is llms.txt an official standard?

No. It is a proposal that Jeremy Howard of Answer.AI published on llmstxt.org in September 2024. There is no standards body that maintains it and there is no obligation to support it. That does not make the file pointless, but it does mean you should treat it as an experiment and not as a fixed part of technical SEO.

Do ChatGPT, Claude or Google use my llms.txt?

There is no confirmation of that. OpenAI, Google, Anthropic and Perplexity have none of them made public that their production systems fetch and use the file. John Mueller of Google even compared the file to the keywords meta tag in 2025. Want to know whether anything is happening on your own domain? Look in your server logs to see whether the path /llms.txt is being requested and by which user agents.

Does llms.txt block AI bots or AI training?

No. Think of llms.txt as an invitation, not a lock. To keep crawlers or training bots out you use robots.txt, with user agents such as GPTBot from OpenAI or Google-Extended from Google. Those are documented mechanisms described by the makers themselves. Llms.txt has no part in that: it points at content, it shields nothing at all.

What is the difference between llms.txt and llms-full.txt?

Llms.txt is an index: a short markdown file with links to your best pages, each with a one line description. Llms-full.txt is the extended variant that holds the full content of those pages in one file. That second form mainly makes sense for documentation sites, where a language model can read the entire manual in one go. For an ordinary company website the index is enough.

Does llms.txt help my ranking in Google?

No. The file is not a ranking factor and Google has nowhere said that it counts. Expecting it to lift your rankings is the wrong reason to start. The things that demonstrably do count stay exactly where they were: technology, content that solves the search question, internal structure and links. Start there, and see llms.txt as a small extra for the long term.

How do I write an llms.txt myself?

Pick ten to twenty five pages with lasting value, split them into logical categories and write a factual one line description for each link. Above that put an H1 with your site name and a blockquote with a summary in two sentences. Save the lot as llms.txt in the root of your domain. Our free generator builds the structure for you, and the downloadable skill on this page does the same in Claude or Codex.

DOC.05

Ten minutes of work, no illusions

Our summary in three sentences. Making one is a decent, cheap experiment: do it if your content is worth it, maintain it like a promise, and expect nothing from it today. The real gain is in what you do along the way: selecting your best content forces you to see where your site is strong and where it is weak, and that insight is worth more than the file itself.

Start with the generator or the skill at the top, check your basics with the free scan, and read on in the knowledge base. And if the question is what all this costs when we look over your shoulder: every rate is out in the open on the pricing page, and for everything beyond that there is the contact page.

Working on the AI visibility of a website
Working on the AI visibility of a website
Section 05 · Next stepreachable 24/7
Book a call
Gianluca, founder of TheSEO
Written by GianlucaFounder of TheSEO. Has been building visibility for companies since 2017, in Google and in AI answers. More about the institute.