Skip to main content
Marketing & SEO

llms.txt: what is this file for, and should you publish one?

· 8 min read · Updated

This article contains affiliate links: we may earn a commission. Learn more

The llms.txt file is a Markdown site map for AI agents: it was proposed in 2024 so that an AI can quickly find the right page in a set of documentation, not to improve a ranking. Google writes in its July 2026 guide that it ignores the file, and two studies find no effect on AI citations.

We have not measured the effect of llms.txt on any engine. This article rests on the specification, Google’s documentation (read on October 21, 2026), two studies read at the source, and a survey of 26 sites that we ran with curl the same day. How we test explains why some articles stay informational. For a definition of GEO, see GEO: definition and differences from SEO.

What is the llms.txt file?

It is a Markdown text file placed at the root of a site (/llms.txt) or in a subfolder, which presents the site in a few lines and points to the useful pages. The proposal, written by Jeremy Howard in 2024 and moved to version 2 in 2026, asks that these pages also have a clean Markdown version, so that an agent does not have to clean up HTML.

The format is simple. Only the level 1 title is required. Next come, in this order, a summary as a quote block, free paragraphs, then level 2 sections that hold lists of links. A section named “Optional” groups the links an agent can skip when it is short on space.

# My site

> One sentence saying what the site is and who it is for.

## Guides
- [Get started](https://example.com/start.md): setup in 5 minutes
- [Pricing](https://example.com/pricing.md): plan grid

## Optional
- [Version history](https://example.com/versions.md)

What is llms.txt really for?

It guides an AI agent that looks for information while it helps a user, for example a coding assistant reading a library’s documentation. According to the proposal, it is mostly used for software documentation, and its author thinks of it first for inference (answering a request), although model training could benefit from it too.

So it is neither a ranking file nor a permission file. The three files at the root of a site do not have the same role:

FileWhat it doesWho reads it
robots.txtTells bots what they may crawlThe search and AI bots that respect it
sitemap.xmlLists all the pages to indexSearch engines
llms.txtOffers a selective map, read on demandAI agents that decide to read it

The proposal states that llms.txt does not replace the sitemap: a sitemap is too big to fit in a model’s context window, and it does not hold the AI-readable versions of pages.

Who publishes an llms.txt file?

Of the 26 sites we tested on October 21, 2026, 12 serve a real llms.txt file, 12 return a 404 and 2 refuse the request. Our sample is chosen, not random: it says nothing about the real share across the web.

Type of sitePublish an llms.txtDo not publish
AI vendors’ documentationOpenAI (developers.openai.com), Perplexity, Anthropic, Gemini APIplatform.openai.com, anthropic.com
Technical documentation and platformsCloudflare, Stripe, Vercel
Marketing and SEO toolsHubSpot, SemrushAhrefs, Moz; Search Engine Land refuses the request (403)
French SEO sites and web mediaSEOmix, AbondanceWebRankInfo, Blog du Modérateur
Google, major media, public bodiesdevelopers.google.com, google.com, Wikipedia (www.wikipedia.org), New York Times, BBC, francenum.gouv.fr; Le Monde refuses the request (402)
Ushayka-pacha.io

To avoid counting fake pages, we required a 200 status, a non-HTML content type and content that starts with ”#”. All four AI vendors publish the file for their documentation, but Google Search’s documentation does not. On a larger scale, SE Ranking found a file on 10.13% of nearly 300,000 domains, with adoption between 8 and 11% whatever the site’s traffic.

Do AIs and Google read the llms.txt file?

For Google, the answer is written down: its guide to optimizing for generative AI, updated on July 10, 2026, lists llms.txt files among the things you can ignore. Google Search does not use them, and publishing one neither hurts nor helps its visibility. For OpenAI, Perplexity and Anthropic, the pages we read about their bots do not say they use it to choose sources.

Two studies measure the effect, with their limits:

SourceWhat it measuredResultLimit
SE Ranking, nearly 300,000 domainsLink between having an llms.txt and being cited by AIsNo visible effect; the model predicts better without this variableCorrelation, not a direct test; page from an SEO tools vendor
OtterlyAI, one test site, 90 daysAI bot requests to /llms.txt84 out of 62,100 visits, or 0.1%; an average page gets about 265A single site; vendor of an AI tracking tool

Neither study proves that llms.txt is useless everywhere, notably for coding assistants that read documentation. They only show that, for being cited in search answers, there is no sign of an effect today.

Should you publish an llms.txt file?

It depends on your site. If you publish technical documentation or an API, that is the proposal’s use case, and the file can help the coding agents that consult it. If your site is a media outlet or a comparison site, nothing in the sources we read shows a gain in citations: do not spend time on it, and do not sell it as a guarantee.

Our own file is generated automatically from our articles, in the three languages, with their descriptions. It costs us nothing to maintain, and we expect nothing from it. We have not measured whether bots request it.

If you decide to publish one, three points matter: an accurate title and summary, links to the pages you really want read, and a curl check that it is served with a 200 and content that starts with ”#”. A badly configured site can return an HTML page with a 200 for an address that does not exist, which looks like a file when there is none. None of the 26 sites in our survey did, but the content check is what guarantees it.

What should you do instead to get cited?

The sources we read agree on the rest: indexed and crawlable pages, a robots.txt that does not block the AI search bots, and content that brings its own point of view. Our free GEO audit guide shows how to check these points and measure whether a brand is cited. To track the result every month without doing it by hand, we compared four tools in our comparison of AI visibility tracking tools, and our pick to get started is Hikoo, which listed a 7-day trial with no credit card on October 12, 2026.

What we have not verified

  • The effect of an llms.txt on ChatGPT, Perplexity, Claude or Gemini: we ran no test, we read studies and documentation.
  • Whether AI bots request our site’s llms.txt: we have not analyzed our logs.
  • The method and raw data of SE Ranking and OtterlyAI: we read their pages and did not reproduce their measurements.
  • How representative our 26 sites are: the sample is chosen, and we only tested the root of each domain.
  • The OpenAI, Perplexity and Anthropic documentation on their bots, as of October 18, 2026.
  • Demand outside France: the search volume we cite (1,000 to 1,300 per month depending on how “llms txt” is written) comes from a tool that only covers France.

FAQ

It is a Markdown text file placed at the root of a website (/llms.txt) that gives AI agents an annotated map of the site, with links to the useful pages. Jeremy Howard proposed it in 2024 to help AIs read documentation at the moment they need it.

No. Google's guide of July 10, 2026 says Google Search does not use llms.txt files and ignores them: publishing one neither hurts nor helps in Google. Google adds that you do not need to create one to appear in its generative AI features.

There is no public evidence. OpenAI, Perplexity and Anthropic do not say their bots use it to choose sources. An SE Ranking study of nearly 300,000 domains finds no link with citations, and OtterlyAI saw 84 requests out of 62,100 AI bot visits over 90 days.

robots.txt tells bots what they may crawl, sitemap.xml lists the pages for search engines to index, and llms.txt offers a selective map that an AI agent reads on demand when it looks for information. None of the three replaces the others.

Run curl -s -o /dev/null -w '%{http_code} %{content_type}' https://your-site.com/llms.txt: expect a 200 and a text type, not HTML. Then curl -s https://your-site.com/llms.txt | head -3 should show a title starting with '#'. A 200 with HTML is a fake error page.

Related articles