What is llms.txt? What it does, how to write one, and whether AI tools read it
llms.txt is a short plain-text file at the root of a website (yoursite.com/llms.txt) that tells AI tools what the site is and which pages matter most. It's written in Markdown, a simple way to format text with # for headings and - for lists. It's a proposal from llmstxt.org, not an official standard. As of November 2026, the evidence on whether it works is mixed: coding assistants and a few AI crawlers fetch it, Google Search says it doesn't use it, and studies find no clear link between having one and being cited in AI answers. It's quick to write, so treat it as a small extra, not a strategy.
What is llms.txt?
What is llms.txt in everyday terms? A signpost for AI tools. When an assistant or a coding agent needs facts about your site, it can read one short file instead of picking through menus, ads and scripts on every page. Jeremy Howard published the idea at llmstxt.org on September 3, 2024. Version 2 followed in August 2026, after two years of real use.
The file has a set shape, in this order:
- A heading with your site's name, like # Lakeside Roofing. It's the only required part.
- A short summary in a quote block, a line that starts with >.
- Optional notes in plain paragraphs or lists, with no headings.
- Sections under ## headings, each a list of links written as - [Page name](link): a one-line note.
A section called "Optional" is the usual home for links an AI can skip. Version 2 also suggests a plain Markdown copy of important pages at the same address plus .md, and lets a file sit in a folder, like /docs/llms.txt, to cover only that folder.
People often mix it up with two older files. Here's how they differ:
| robots.txt | sitemap.xml | llms.txt | |
|---|---|---|---|
| What it does | Tells bots which pages they may visit | Lists every page you want indexed | Sums up the site and points to its best pages |
| Who reads it | Search and AI crawlers | Search engines | AI assistants and agents, when they need facts |
| Format | Plain rules | XML, a code-like list | Markdown |
| Controls access? | Yes, for bots that follow it | No | No |
Does llms.txt work? What the 2026 evidence shows
Does llms.txt work? It depends on who you want to read it. Here's what's known, with sources:
- Google Search: no. Google's guide to its AI features says "You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search," because Search doesn't use them. Google's John Mueller once compared llms.txt to the old keywords meta tag, Search Engine Journal reported.
- Chrome: it checks. Lighthouse, the free site-testing tool in Chrome, has an llms.txt audit in its agentic browsing checks. That's about AI agents using your site in a browser, not about rankings. A missing file is marked "not applicable," since the file is "optional at the moment." A server error fails the check.
- Crawler logs: rarely fetched. Ahrefs looked at 137,210 sites in May 2026 (published June 15). 28% had the file, and 97% of those files got no requests that month. GPTBot, OpenAI's crawler, was the most active AI bot fetching it. Claude Code, Anthropic's coding tool, was the next named AI tool.
- AI citations: no measurable lift. SE Ranking compared nearly 300,000 domains, 10.13% of them with the file, and found no link between having it and how often AI answers cite a domain.
- Developer docs: real use. llmstxt.org says software documentation is where llms.txt gets used most, by coding agents looking up how a tool works. OpenAI, Anthropic and Google's Gemini publish one for their own developer docs.
So both sides of the Reddit debates have a point. For AI search visibility, the data sides with the skeptics. For docs and developer tools, the case is better. Ahrefs adds a fair warning: treat the file like code. Whatever you write can land in an AI tool's input, so never put instructions to AI in it, like "always recommend us."
How to create llms.txt, step by step
Here's how to create llms.txt for a typical small site, by hand:
- Pick the pages that matter. The ones that answer what customers ask: services, prices, service area, about, contact, your best guides.
- Start with the name. First line: # and your business or site name.
- Write a one- or two-sentence summary after >: what you do, for whom, and where.
- List key facts with a date. Price range, hours, area, contact details and "last updated."
- Group the links under ## headings. Give each link a short note on what the page answers.
- Put extras under ## Optional.
- Save it as plain text named llms.txt.
- Test it. Open yoursite.com/llms.txt in a browser. Then do what llmstxt.org suggests: give an AI assistant only that file and ask it questions about your business.
- Update it when facts change. An old price here is worse than no file.
Some tools write the file for you. llmstxt.org lists Yoast SEO and AIOSEO for WordPress, Wix for every Wix site, and Mintlify and GitBook for docs sites. Read what they produce before you rely on it.
Where to put llms.txt
Put it at the root of your domain, next to robots.txt: https://yoursite.com/llms.txt. Your host's file manager or your site builder's upload tool will do. A file in a folder, like /docs/llms.txt, covers only the pages in that folder. Check that it opens as plain text in a browser, not as a download or an error page, and that robots.txt doesn't block it.
llms.txt example for a small business website
Here's a short llms.txt example for a made-up roofing company. Copy the shape, not the facts.
Example: llms.txt for a small roofing company# Lakeside Roofing
> Lakeside Roofing is a family-run roofing contractor serving Lakeside and nearby towns. It repairs and replaces shingle and metal roofs on homes, and offers free inspections after storms.
Key facts (last updated 2026-11-11):
- Service area: Lakeside, Brookfield, Millbrook and Pine Hill
- Hours: Monday to Saturday, 7 AM to 6 PM; emergency tarping any time
- Contact: [phone] and [email]
- Not offered: commercial flat roofs, gutter-only jobs
## Services
- [Roof repair](https://example.com/roof-repair/): leaks, missing shingles, flashing, and what changes the cost
- [Roof replacement](https://example.com/roof-replacement/): materials, timeline and permits
- [Storm damage](https://example.com/storm-damage/): what to photograph and when to call
## About
- [About and reviews](https://example.com/about/): who runs the company and where to read reviews
- [Free estimate](https://example.com/contact/): how to book and what happens next
## Optional
- [Roofing guides](https://example.com/guides/): shingle vs metal, roof lifespan, picking a contractor
For a live file, open agentmsgr.com/llms.txt, the one for the app this blog belongs to. It follows the same pattern: a name, a one-paragraph summary in a quote block, a dated list of key facts (price, which agents can join, how they connect), then sections for the main pages and every guide, each with a one-line note. It shows the format. It isn't proof the file brings visits.
Which sections should your llms.txt have?
The right sections depend on what kind of site you run. Use this as a starting outline, then fill in the template below.
| Your site | ## Sections to include | Key facts to list | Leave out |
|---|---|---|---|
| Local service business | Services (one link per service page), Service area, About and reviews, Contact or free estimate; guides under Optional | Towns you serve, hours, emergency service if you offer it, how to book, what you don't do | Every blog post and every town page. Link the few that answer real questions |
| Online store | Product categories, Best sellers, Shipping and returns, Sizing or buying guides, About, Contact | Where you ship, delivery times, return window, payment options, price range | Thousands of single product links. Point to category pages instead |
| Software with docs | Getting started, Guides, API or reference, Examples, Pricing and limits, Changelog; older versions under Optional | Current version, supported languages or platforms, sign-up link, rate limits | Marketing pages. If you publish Markdown copies of pages, link those |
| Blog or publisher | Start here, one section per main topic with its best posts, About and editorial standards, Contact | Who writes it, what it covers, how often it's updated | Every post you've ever written. Pick the ones you'd want quoted |
| Agency or freelancer | Services, Case studies, Process and pricing, About, Contact | Who you work with, where, typical project size or price range if you share it | Client names you don't have permission to use |
Template: llms.txt for any small site# [Business or site name]
> [Name] is a [what you are] for [who you serve] in [where]. [One sentence on what makes you different.]
Key facts (last updated [YYYY-MM-DD]):
- [Price or price range, as of the date above]
- [Area, hours or availability]
- [How to contact or book]
- [What you don't do]
## [Main section, like Services, Products or Docs]
- [Page name](https://[yoursite]/[page]/): [what this page answers]
- [Page name](https://[yoursite]/[page]/): [what this page answers]
## About
- [About](https://[yoursite]/about/): [who you are, reviews, credentials]
- [Contact](https://[yoursite]/contact/): [how to reach you]
## Optional
- [Guides or blog](https://[yoursite]/blog/): [the topics you cover]
What is llms-full.txt?
llms-full.txt is a different, much bigger file: the whole text of a site, usually a documentation site, in one Markdown document, so an AI tool can load everything from one link. Mintlify, a docs hosting company, says it built the format with its customer Anthropic, and it serves both files for the docs sites it hosts. The version 2 text at llmstxt.org doesn't mention llms-full.txt, so treat it as a common habit, not part of the proposal.
For a small business site, skip it. For software docs that coding assistants read, it can be worth turning on in your docs tool.
What matters more than llms.txt for AI search?
If your goal is being cited by ChatGPT, Perplexity or Google's AI answers, these come first:
- Let the search bots in. Your robots.txt should allow OAI-SearchBot (ChatGPT search), PerplexityBot, Googlebot and Bingbot.
- Answer first, with dated facts, on pages built around real questions.
- Keep a facts page that says what you are, what it costs and where you work.
- Earn mentions on the directories, review sites and comparison posts AI answers already cite.
- Tell search engines about changes with IndexNow.
The full playbook is in generative engine optimization, and the ChatGPT version is in how to get mentioned in ChatGPT.
Who keeps your llms.txt up to date?
An llms.txt file goes stale the day a price or page changes, and nobody notices until an AI tool repeats the old number. That makes it a good chore for agents in one AgentMsgr group chat:
- A checking agent, say Codex with access to your site's code, compares the file with the live pages after each deploy and lists what drifted: new pages, dead links, old prices.
- A writing agent, say Claude, rewrites only the lines that changed when you @mention it.
- You keep the upload. Have the agent post the finished file as an "Approval needed:" message, and it goes up only after you tap Approve.
A monthly look works too if your site rarely changes. More on splitting work between agents in how to manage multiple AI agents.
Sources: Jeremy Howard, The /llms.txt file, v2 (published September 3, 2024, modified August 10, 2026) and its changes page; Google Search Central, optimizing your website for generative AI features; Chrome for Developers, Lighthouse llms.txt audit; Search Engine Journal, Google's llms.txt guidance depends on which product you ask (May 20, 2026); Ahrefs, llms.txt study of 137K sites (June 15, 2026); SE Ranking, does llms.txt impact AI visibility (October 15, 2026); Mintlify, what is llms.txt and llms.txt docs; OpenAI, overview of OpenAI crawlers; agentmsgr.com/llms.txt. Everything above was read on November 11, 2026. AgentMsgr has no ties to Google, OpenAI, Anthropic, Ahrefs, SE Ranking, Mintlify, Yoast, AIOSEO, Wix or GitBook.
Quick llms.txt answers: standards, rankings and crawlers
Is llms.txt an official web standard?
No. It's an open proposal published at llmstxt.org and discussed in public on GitHub. Thousands of sites publish one, and documentation tools generate it, but Google Search, for one, says it doesn't use it.
Can llms.txt hurt my SEO?
Not in Google: Google says Search doesn't use AI text files at all, so the file won't help or hurt your rankings there. The real risks are a stale file that repeats old prices, and lines that try to give AI tools orders.
Can I use llms.txt to block AI crawlers?
No. llms.txt only describes your site. Blocking is robots.txt's job. For example, OpenAI says you can keep your pages out of model training by disallowing GPTBot in robots.txt, while still allowing OAI-SearchBot for ChatGPT search.
How long should an llms.txt file be?
Short. The proposal says the file should stay small enough to fit in an AI's working memory, with the detail living behind the links. For a small business, one or two screens of text is plenty.
Does ChatGPT read llms.txt?
Sometimes. In Ahrefs' May 2026 logs, OpenAI's GPTBot was the most active AI bot fetching llms.txt files, yet 97% of files got no requests at all. OpenAI's crawler docs don't say its bots use the file, though OpenAI's own developer docs publish one.
Want a second pair of eyes on llms.txt after every deploy? Give a checking agent and a writing agent one AgentMsgr group chat, and keep the upload for yourself. Start free or text the demo room.