What is llms.txt, and when is it useful?

An llms.txt file gives an agent a short guide to your website. It can help a tool find useful documentation, but publishing one does not guarantee search visibility or AI recommendations. Here is how to use it without letting it distract from more important work.

Reviewed October 1, 2026 · 8 min read

llms.txt is a text file that helps an agent understand a website and find useful resources. It is optional. If you publish one, treat it as another document to maintain, with accurate descriptions and links to the pages you want people and tools to use.

The file is often discussed as a way to improve AI visibility. That is a separate claim from making information easier to retrieve. A useful reference document does not automatically become a ranking signal.

This guide explains the format, its practical uses and the evidence about adoption. It also shows where llms.txt fits alongside readable pages, structured data and supported integrations.

What an llms.txt file contains#

Jeremy Howard proposed llms.txt in September 2024. The current proposal describes a root-level file that helps agents use a website. A common approach is a short site description followed by annotated links to useful pages.

Use clear headings and concise descriptions. For example, a clinic could link to its services and cancellation policy. The prices and business below are illustrative:

# Riverside Physio
> Sports physiotherapy clinic in Austin, TX. Initial assessments,
> follow-up treatments, and dry needling. Online booking available.

## Services
- [Initial Assessment](https://physio.example/assessment): 60 min, $140
- [Follow-up Treatment](https://physio.example/follow-up): 30 min, $85

## Policies
- [Cancellations](https://physio.example/policies): 24-hour notice required

Some documentation sites also publish llms-full.txt, which combines a larger collection of content in one file. A compact index is easier to maintain for many business sites; a larger export can be useful when a tool needs substantial documentation at once.

Where the file can help#

An llms.txt file is most useful when you know how a person or tool will use it:

• Provide a short starting point. Link to the pages that answer common questions instead of making a reader navigate the entire site.
• Explain what belongs where. A brief note can distinguish a pricing page from a service description or an API reference.
• Support an integration you can test. If your customers use a tool that retrieves llms.txt, check that the file leads it to current information.
• Keep maintenance manageable. Link to changing prices and availability instead of copying values you may forget to update.

These are practical uses for a reference file. Whether it changes discovery or recommendations depends on the service consuming it, and requires separate evidence.

What adoption data tells us#

Ahrefs examined 137,210 domains in its analytics population for May 2026. Among domains with a valid llms.txt file, 97% received no requests for it that month. The sample does not represent every website, and a fetch does not prove that a tool used the contents. It does show why publishing the file should not be treated as a visibility guarantee.

Google’s guidance for AI features in Search says no special AI text file is required for inclusion. Focus first on accessible, useful pages and accurate business information. That guidance concerns Google Search; it should not be stretched into a claim about every AI product.

For other services, check their documented ways to discover and retrieve information. The crawler guide explains why search crawlers, training crawlers and user-triggered fetchers need to be considered separately.

The decision is easier when you start with a real use case. A maintained guide for a known tool can be valuable. An unattended file full of old prices can create another source of confusion.

What to prioritize alongside llms.txt#

Different services use different sources. These are the main things to check when making your business information easier to find and use:

Readable HTML gives many fetchers access to your content without extra rendering. Structured data can describe prices, hours and offers explicitly, but it must match the visible page. Markup makes facts easier to interpret; it does not establish that they are true.

Shopping platforms have their own product-data and enrollment requirements. A feed can support discovery, while a documented API or MCP tool can support actions such as checking availability. The UCP, ACP and MCP comparison explains those differences, and the ChatGPT checkout guide separates product discovery from checkout support.

Choose the resource that solves the problem you have. If a product page cannot be retrieved, start with access. If customers need live appointment times, a static text file will not replace an availability integration.

How to create and maintain llms.txt#

For a small site, start with a short file you can review whenever the website changes:

1. Open a text editor. Start with an H1 (# Your Business Name) and a two-sentence blockquote describing what you do, where, and for whom.
2. Add one H2 section per topic (Services, Pricing, Policies, Contact) containing markdown links to your canonical pages, each with a one-line note.
3. Keep it short. Curation is the entire point; pasting your sitemap into it defeats the purpose.
4. Publish the file at example.com/llms.txt and check that it returns the intended text with a successful HTTP response.
5. Review the file when services, policies or URLs change. Prefer links to current pricing over a second price list that could become stale.

You can write the file yourself or use a generator, then review the output. Nexez’s Agent-Ready Kit includes an llms.txt file alongside other resources. Check the generated descriptions and links before publishing, just as you would any other website content.

A practical order of work#

If time is limited, address problems that prevent a real customer question from being answered:

1. Check that important pages can be retrieved and read. Review search and training preferences separately when configuring crawler access.
2. Make business, service and offer details clear on the page. Add appropriate structured data and keep it consistent.
3. Maintain the listings and feeds used by your target platforms. The ACP guide explains why a protocol and platform enrollment are separate.
4. Add supported actions when customers need them. For example, an appointment integration can provide current times and an authorized booking flow.
5. Publish llms.txt when it provides a useful route to those resources, then check its accuracy and usage.

Nexez brings several of these resources together in a business listing, including structured data and documented agent interfaces. Review plan details and the requirements of any external service you intend to connect.

How to decide whether to publish one#

Use llms.txt when a short guide would help a tool or customer find the right material. Do not expect the file alone to change your search visibility.

If your pages are incomplete, inaccessible or out of date, fix those first. Once the underlying information is sound, a concise, maintained llms.txt file can make it easier to navigate.