CrowlyCrowly
GEO

llms.txt — what it is, how to implement it, and whether it's worth it for your company

llms.txt is an emerging standard for helping AIs understand your site. But adoption is still limited and the real impact is uncertain. Here's what it is, how to implement it, and an honest assessment of when it's worth it.

Crowly4 min read
Programming code displayed on a screen

In September 2024, Jeremy Howard — co-founder of fast.ai and an AI researcher — proposed a new standard for the web: llms.txt. The idea is simple and inspired by robots.txt: a text file at the root of the site that tells language models what the site is, what's important, and how the content is organized.

The concept gained traction quickly in the developer and AI-SEO communities. Anthropic adopted the standard for Claude's own site. Other technology companies followed. And the question that inevitably reached marketing and content teams was: "do we need to implement this?"

The honest answer, in mid-2026, is: probably yes, but with calibrated expectations.

What llms.txt is and what it's for

llms.txt is a Markdown file (not plain text, despite the name) placed at the root of the site (yoursite.com/llms.txt). It contains:

  1. The site's name and description — what the company does, in direct language
  2. Links to the most important content — with descriptions of each section or document
  3. Context that helps the model understand how the content is organized

The goal is to give a language model that's "reading" the site a clear map of what's most relevant — similar to how a sitemap (sitemap.xml) helps search bots, but in a format readable by humans and language models.

How to implement llms.txt

The implementation is technically simple — simpler than any other AI-visibility infrastructure element:

Basic structure:

# Company Name

> A 2-3 sentence description of what the company does and for whom.

## Documentation

- [Quick-start guide](/docs/start) — How to start using the product in 10 minutes
- [API reference](/docs/api) — Complete technical API documentation
- [Use cases](/cases) — Examples of how customers use the product

## Blog

- [Latest articles](/blog) — Educational content about [main topic]

## About

- [About us](/about) — History, mission, and team
- [Contact](/contact) — How to reach the company

For sites with a lot of content, there's also the llms-full.txt convention — a version that includes the full content of the most important documents, not just links.

Which AI platforms recognize llms.txt in 2026

The current state of adoption, honestly: llms.txt isn't an official standard of any web-standardization organization — it's an emerging convention with growing but still limited adoption.

Platforms that have documented recognition or use of llms.txt: Claude/Anthropic (uses it for its own site), and some AI-search implementations that process sites in real time (like Perplexity, to a lesser degree). Training versions of models like GPT-4 didn't "read" your site's llms.txt for training purposes — but versions with active search may benefit from the file when they process the site.

The honest assessment: when it's worth it and when it isn't

It's worth it if:

  • Your site has complex technical content or extensive documentation that can be hard to navigate
  • You have a software product or API with documentation that AI agents actively use
  • You want to proactively signal authority on the topics you cover

It's probably not a priority if:

  • You don't yet have enough quality content for the links llms.txt would point to
  • You're resource-constrained — the relative ROI of producing good content is much higher than implementing llms.txt on a site with weak content
  • The direct impact on training models is minimal — llms.txt won't make GPT "learn" your company in the next cycle

Conclusion: implementing it is simple enough that not implementing it is an unnecessary oversight — but don't treat llms.txt as a solution for AI presence. Quality content remains the most decisive factor.

How Crowly can help measure the impact of technical changes

Implementations like llms.txt are hard to isolate in terms of impact. Crowly, with weekly monitoring before and after implementation, provides the closest available data to "this made a difference" — even if the signal is small.

Implement the technical optimizations and measure the impact with Crowly. Free diagnostic. Analyze my brand →

Sources:

Keep reading