What Is llms.txt? Format, Example and Whether It Helps

Author: Lucky Oleg | Published Updated

llms.txt is a Markdown file, usually at the root of a website, that gives AI tools and readers a short summary of the site and curated links to its most useful pages. It is a community proposal, now in its second version, not an access-control standard, and there is no general evidence that publishing the file increases citations across AI platforms. Google Search ignores it.

That boundary makes the implementation decision straightforward: publish a small, accurate file if maintaining it is cheap, but do not treat it as a substitute for robots.txt, a sitemap, internal links, or good pages.

What the proposal defines

The llms.txt proposal is now at v2 (modified 10 August 2026). It describes a Markdown file with:

  • an H1 containing the project or site name, the only required section;
  • a short summary;
  • optional explanatory text;
  • H2 sections containing curated Markdown links;
  • an Optional H2 section for secondary links that a reader can skip.

The file can sit at the site root or at any path within it, and then covers the pages under that path: /docs/llms.txt describes /docs/. The proposal also suggests offering a Markdown version of each page at the same URL with .md added, such as page.html.md or index.html.md.

llms.txt example

A minimal file for a service business:

# Example Company

Example Company provides commercial energy audits in New Zealand.

## Services

- [Commercial energy audits](https://example.com/audits/): Scope, process, and deliverables.
- [Monitoring](https://example.com/monitoring/): Ongoing energy-use reporting.

## Guides

- [Preparing for an audit](https://example.com/audit-preparation/): Information to collect before the site visit.

This is a curated guide, not a sitemap dump. Descriptions should state what a reader will find rather than repeat keywords.

llms.txt vs llms-full.txt

llms.txt is an index: a summary and a short list of links. llms-full.txt is a single file with the full Markdown text of the key pages, so a tool can load the content in one request instead of following links. Use the index for a business site; the full file mainly suits documentation, where a coding assistant may want every page at once.

llms-full.txt is not part of the llmstxt.org proposal. It comes from tooling: Mintlify generates both files for hosted docs, and All in One SEO has a separate llms-full.txt switch. The same caveat applies to both files: no major search platform documents using them to rank or cite pages. Our llms.txt checker reports whether a root llms-full.txt is present.

What Google and Lighthouse say

Google’s current guide to generative AI features explicitly addresses the format: Google Search ignores AI text files such as llms.txt, and maintaining one neither helps nor harms visibility or rankings in Google Search.

Google also says there is no new machine-readable AI file required for AI Overviews or AI Mode. Normal Search requirements still apply: crawl access, indexing eligibility, useful text, internal discoverability, and compliance with Search policies.

Therefore, do not sell llms.txt as a Google AI Overview tactic.

Chrome’s Lighthouse does check the file. Its llms.txt audit, in the Agentic browsing category (updated 5 May 2026), flags a page when fetching /llms.txt returns a server error. A missing file (404) is marked not applicable, because the file is optional. So a broken llms.txt route is worth fixing; a missing one is not a Lighthouse failure.

What other platforms document

Some developer documentation sites publish their own llms.txt files, and some tools may consume them. Publication is not the same as a platform-wide commitment to use the file for public search selection.

OpenAI’s public publisher guidance tells sites that want inclusion in ChatGPT summaries and snippets not to block OAI-SearchBot. Perplexity’s crawler documentation gives corresponding guidance for PerplexityBot. Neither document makes llms.txt a prerequisite for inclusion.

When support matters, look for current platform documentation or controlled server-log evidence. Do not infer crawler use from the mere existence of a file.

llms.txt, robots.txt, and sitemap.xml

FilePrimary jobIs it a permission control?Documented Google Search role
robots.txtcrawler access rulesYesControls Googlebot crawling
sitemap.xmlcanonical URL discovery and metadataNoSupported discovery mechanism
llms.txtproposed curated site guideNoIgnored by Google Search

Use robots.txt for access choices. Use a sitemap for canonical discovery. Treat llms.txt as an optional editorial layer.

How to add llms.txt on WordPress and other platforms

  • Yoast SEO: generates the file for free; turn it on in the site features settings, then let Yoast pick key content or choose pages manually (Yoast).
  • Rank Math: enable the LLMS Txt module on the Rank Math dashboard, then edit it under General Settings (Rank Math).
  • All in One SEO: enabled by default under Sitemaps, LLMs.txt tab, with a separate llms-full.txt switch (AIOSEO).
  • Documentation platforms: Mintlify generates llms.txt and llms-full.txt automatically for hosted docs.
  • Any other site: write the file by hand, or start from our llms.txt generator, and upload it to the web root (on Astro, Next.js and most static builds, the public/ folder).

Whichever route you choose, open the generated file and remove pages you would not send a new customer to. We checked these plugin options on 30 October 2026.

How to create a useful file

1. Define the audience and purpose

Write one sentence that states what the organization does, who it serves, and where it operates when location matters.

2. Select canonical pages

Include only pages that help a reader understand the business or project:

  • primary services or products;
  • authoritative documentation;
  • strong guides or case studies;
  • useful tools;
  • essential identity or contact pages.

Exclude login, cart, filter, duplicate, thin, staging, and non-canonical URLs.

3. Write factual descriptions

Each description should explain scope. Avoid claims such as “best,” “leading,” or “AI optimized” unless the page proves them.

4. Validate the response

Check that:

  • /llms.txt returns 200;
  • the response is readable plain text or Markdown;
  • every linked URL is absolute, canonical, and live;
  • redirects do not point to retired hosts;
  • the file contains no secrets or private URLs;
  • changes to key routes update the file.

Our llms.txt generator can create the initial structure, and the llms.txt checker can inspect a published file. Human review is still necessary because a syntactically valid list can be stale or badly curated.

Measuring whether it is used

Do not measure success by the file’s existence. If a system claims support, test it:

  1. record the platform, version or mode, date, and query;
  2. publish a unique but non-sensitive change in the file;
  3. inspect verified crawler logs where possible;
  4. compare repeated results while holding other variables steady;
  5. avoid claiming causation when the same pages are discoverable elsewhere.

Even a verified fetch proves that the system requested the file, not that the file changed citation selection.

When the file is worth maintaining

Publish llms.txt when your site already has strong technical foundations and the file can be generated or curated without drift. Skip or postpone it when the site still has blocked pages, broken canonicals, orphaned content, an inaccurate sitemap, or weak primary pages.

The right priority order is usually:

  1. crawl and indexing controls;
  2. accurate, useful content;
  3. canonical URLs and internal links;
  4. structured data that matches visible content;
  5. measurement;
  6. optional experimental discovery files.

For the surrounding work, see the GEO guide and the article on measuring AI visibility. The evidence-aware conclusion is modest: llms.txt can be a clean, low-cost site guide, but platform support and business impact must be demonstrated rather than assumed.

Recommended tools

Recommended tools for this guide

Use these free tools to apply the ideas from this guide to your own website.

Useful info? Spread the Aloha:

Lucky Oleg

Lucky Oleg is the founder of Web Aloha, a web design & SEO agency helping businesses ride the digital wave. With years of experience in WordPress, technical SEO, and web performance, he writes about what actually works in the real world.