AI search and agents

What is llms.txt, and does my website need one?

llms.txt is a proposed Markdown file at the root of a website that gives AI tools a short summary of the site and links to its key pages. It is a proposal, not a standard that any search engine or AI tool is required to read.

Published . Last updated . By Hevaris.

What does an llms.txt file contain?

An llms.txt file is plain Markdown with a fixed order: a title, a short summary, optional notes, and lists of links. Only the title is required. Everything else is there to help a tool decide which page to read next.

PartRequiredWhat goes in it
H1YesThe name of the site or project
BlockquoteNoA short summary of what the site is
NotesNoAny Markdown except headings, for context an AI tool needs
H2 sectionsNoLists of links, each with a name, the URL and a short note
“Optional” sectionNoSecondary links a tool can skip when it needs less context

The order and parts above are as set out in the proposal on llmstxt.org.

Who proposed llms.txt, and is it a standard?

It was proposed by Jeremy Howard and first published on 3 September 2024. It is a proposal that sites can choose to adopt, not a standard that search engines or AI tools have agreed to follow.

That matters for how you spend time. Treat llms.txt as a low-cost tidy-up, not as a lever. Whether a search engine, an AI assistant or an AI agent reads your file depends on that tool, and Hevaris cannot promise any of them will.

Does my website need an llms.txt file?

Not needed, but cheap and useful if your site is generated from data. The file costs little to publish and doubles as a plain-language summary of what your business is, which is also useful for people who check it.

A site with a few pages gains little. A site with many services, pages or product types gains more, because a short curated map is easier to use than a full crawl.

How do I write a good llms.txt?

Write it as if briefing someone who has never heard of your business. Keep it factual and keep every statement checkable on the page it links to.

  1. Name and summary. One line that says what the business is and who it serves, using the same wording as your About page.
  2. Scope and limits. Say what you do not do. Hevaris lists what it declines, because a clear boundary is easier to quote correctly.
  3. Links with notes. One line per important page: a name, the URL and a sentence on what is there.
  4. Same facts as the site. Do not put anything in the file that is not on the pages. A file that contradicts the site is worse than no file.
  5. A date or version. Update it whenever the pages it summarises change.

What can llms.txt not do?

It cannot make a tool read your site, cite it or rank it. It does not replace clear titles, a sitemap, readable page openings or consistent facts across pages. Those are the work that most affects whether people and tools can use your site.

The proposal also asks sites to serve a clean Markdown copy of pages at a matching address. That is a bigger change than adding one file, and it is worth doing only if you have a reason to.

How does Hevaris handle llms.txt?

Hevaris generates its own llms.txt at build time from the same data as the pages, so names, links and limits cannot drift apart. On a build or audit, we check that the file exists, matches the pages and overstates nothing.

What sources does this guide use?

The primary sources are linked below, so each statement can be checked at its origin.

Frequently asked questions

Does llms.txt improve my Google rankings?

Hevaris does not claim that it does. llms.txt is a proposal for helping AI tools use a site on demand, and whether any particular search engine or AI tool reads it is up to that tool.

Is llms.txt the same as robots.txt?

No. robots.txt tells crawlers which URLs they may fetch. llms.txt is a Markdown summary with links, written for AI tools that want a compact way into the site.

Where does the file go?

At the root of the site, the same level as the home page address. The proposal also allows a file under a subpath, which then covers the pages beneath it.

Do I need to write it by hand?

No. It can be generated at build time from the same data as your pages, which keeps it from drifting out of date. Hevaris generates its own that way.

Request an AI visibility audit