llms.txt is a proposed convention for a single Markdown file at the root of a domain that gives large language models a clean, curated map of a site's most important content. It was proposed in September 2024 and published at llmstxt.org.

Do AI engines actually read llms.txt?

No major AI company has publicly committed to parsing it. It remains a community proposal rather than an adopted standard, and practitioners consistently report no measurable citation or ranking lift from adding one.

How is llms.txt different from robots.txt and sitemap.xml?

robots.txt states what bots may access, sitemap.xml lists every URL for discovery, and llms.txt curates and summarizes your best content for a model. The first two are access and index files; the third adds editorial judgment.

Is llms.txt worth building?

For a well-structured site it is about twenty minutes of work, cannot hurt your rankings, and is a reasonable low-cost bet on where AI search is heading. It is not worth delaying crawler access, rendering, or content structure for.

What is llms-full.txt?

A companion convention that includes the full text of key pages in one file, rather than just links and descriptions. It is aimed at documentation sites where a model may benefit from the entire corpus in a single fetch, and adoption is even less established.

Where should llms.txt live?

At the root of your domain, served at yourdomain.com/llms.txt as plain text or Markdown. On a static site that usually means the public folder.

What Is llms.txt? Honest Guide and Template

llms.txt is a proposed convention for a Markdown file at your domain root that hands large language models a curated map of your best content. It is cheap to build, it cannot hurt you, and no major AI engine has committed to reading it. Here is the honest version, separated from the hype.

What llms.txt actually is

Proposed in September 2024 by Jeremy Howard of Answer.AI and published at llmstxt.org, llms.txt is a single Markdown file at /llms.txt.

Instead of making a model crawl and guess its way through your navigation, boilerplate, and footers, you hand it a short document that says: here is who we are, and here are the pages that matter. It is plain Markdown, an H1 with your name, a one-line summary, then linked lists of key pages with short descriptions.

Think of it as an executive summary of your site, written for machines.

How it differs from robots.txt and sitemap.xml

These three get lumped together but do different jobs.

File	Audience	Job	Status
`robots.txt`	Crawlers	States what bots may access	Long-established standard
`sitemap.xml`	Search engines	Lists every URL for discovery	Long-established standard
`llms.txt`	AI models	Curates and summarizes your best content	Community proposal

robots.txt is a bouncer and sitemap.xml is an index. llms.txt is the only one that adds editorial judgment: it does not list everything, it lists what you would actually want quoted.

There is also a companion idea, llms-full.txt, which embeds the full text of key pages rather than links to them. It is aimed mainly at documentation sites, and its adoption is even thinner.

The honest part: is anyone reading it?

This is where most articles go quiet, so let us be direct. As of September 2026, no major AI company publicly commits to parsing llms.txt. It is a community proposal, not an adopted standard, and practitioners consistently report no measurable citation or ranking lift from adding one.

So if a vendor tells you llms.txt will get you into ChatGPT’s answers this quarter, be skeptical. What demonstrably decides citation today is retrieval eligibility and quotable structure, covered in retrieval vs citation.

llms.txt is a low-cost bet on where AI search is heading, not a lever that moves results today.

So is it worth building?

For most sites, yes, if it is genuinely cheap, and for a well-structured site it is.

Low cost. Twenty minutes and one file for a small site.
Low risk. It cannot hurt your Google rankings; anything that does not understand it ignores it.
Forward-looking. If adoption grows the way robots.txt and sitemaps did, a well-made file costs nothing to have waiting.
A useful forcing function. Writing a clean summary of your best pages is exactly the entity-clarity work that helps GEO anyway.

When to skip it: if your site cannot be crawled, does not render without JavaScript, or is not indexed in Bing, llms.txt is decoration on a locked door. Fix those first using the technical SEO checklist for AI search. It is also not worth maintaining on a large, fast-changing site where it will silently go stale, which is worse than not having one.

How to build one

Create a Markdown file named llms.txt.
Start with an # H1 of your brand name, then a > blockquote one-line summary.
Add ## sections, such as Services, Blog, About, with bulleted links in the form [Anchor](URL): short description.
Keep descriptions factual and specific. This is content a model may lift verbatim, so write it as you would want to be quoted.
Save it at your site root so it serves at yourdomain.com/llms.txt. On a static site that is the public/ folder.
Keep it current when you ship important pages, and delete it if you stop maintaining it.

A minimal example:

# Ambeltek

> New-age web development, AI SEO and GEO. Websites engineered to rank on
> Google and get cited by AI engines like ChatGPT, Perplexity, and Gemini.

## Services
- [Web Development](https://ambeltek.com/services/web-development/): Fast, structured, conversion-focused sites.
- [GEO](https://ambeltek.com/services/geo/): Getting your brand cited inside AI answers.

## Blog
- [What Is GEO?](https://ambeltek.com/blog/what-is-geo/): The evolution of SEO for AI answers.

What to do instead, if you only have an hour

If llms.txt is the only AI-facing change you make, you have spent your hour on the least proven item on the list. In rough order of demonstrated impact:

Confirm retrieval crawlers can reach you, including at the CDN layer. See robots.txt for AI crawlers.
Get indexed in Bing, since ChatGPT’s search leans on it heavily.
Lead every section with a self-contained answer. See content chunking for AI.
Define one Organization entity with a stable identifier.
Then write llms.txt.

See it live

We practice what we write: ambeltek.com/llms.txt is a real, working example you can open right now. It sits alongside our AI-crawler-friendly robots.txt, the same philosophy that runs through what GEO is and why it matters.

The verdict on llms.txt

Build it if it takes twenty minutes and you will keep it current. Do not build it instead of fixing crawler access, rendering, or passage structure, and do not pay anyone a premium for it.

If you want to know which AI-facing changes would actually move your visibility, request an AI visibility audit and we will rank them by evidence rather than novelty.

What Is llms.txt (and Is It Worth Building)?