What Is llms.txt, and Does It Help You Get Cited by AI

That is the honest version. The rest of this explains what the file is, how it differs from the files you already know, what the evidence actually says, and how to write one that earns its place.

What llms.txt actually is

The idea comes from a 2024 proposal. The web is full of pages built for browsers, wrapped in navigation, ads, and markup that an AI model has to wade through to find the substance. llms.txt is a curated shortcut. You write a single markdown file that says, in plain terms, what your site is and which pages matter, so a model reading your site does not have to guess.

The format is deliberately simple. An H1 with your name. A blockquote with a one-line summary. An optional paragraph of context. Then sections of links, each with a short description.

# Vikrama

> A studio that builds revenue systems for D2C, real estate, and manufacturing teams. Gurugram, India.

## Pillar guides
- [Answer Engine Optimisation Guide](https://vikrama.studio/writing/answer-engine-optimization-guide): How to structure content so AI engines cite your brand.
- [The D2C Revenue Engine](https://vikrama.studio/writing/d2c-revenue-engine-guide): How one system replaces three or four agencies.

## Work
- [CutePotatoIndia](https://vikrama.studio/case-studies/cutepotatoindia): Babywear D2C, Shopify rebuild.

## Contact
hello@vikrama.studio

That is the whole format. Readable by a person, trivial for a machine.

llms.txt is not robots.txt, and not a sitemap

These get confused, so here is the clean distinction:

• robots.txt tells crawlers what they are allowed to access. It is about permission.
• sitemap.xml lists every URL on your site so crawlers can discover all of them. It is about completeness.
• llms.txt hands AI engines a curated short list of what matters and why. It is about priority and meaning.

A sitemap says "here is everything." llms.txt says "here is what is worth reading, and here is what each thing is." The two are complementary. One is exhaustive, the other is editorial.

There is also llms-full.txt, a companion file meant to hold the full text of your key pages in one place, so a model can ingest everything in a single fetch rather than crawling page by page. If you publish llms.txt, generate llms-full.txt from your content at build time so it never goes stale.

Does it actually work in 2026

Here is where most articles oversell. The honest position:

• The format has real adoption on the publishing side. Many documentation sites and a growing number of brands now serve an llms.txt file.
• The consumption side is unsettled. There is no public confirmation that the largest AI engines read llms.txt and weight it when deciding what to cite. Some search figures have been openly skeptical that it influences ranking at all. No one has produced clean, repeatable evidence that adding the file moves citations on its own.
• What is true is that it costs almost nothing to publish, it cannot hurt you, and if and when more engines adopt it, you are already covered. That is a reasonable forward bet, not a tactic that earns citations by itself.

So treat llms.txt as a small, cheap layer on top of the work that actually moves citations, not as the work itself.

Where it sits in an honest AEO plan

If your goal is to be cited by ChatGPT, Perplexity, and Google AI Overviews, spend your effort in this order:

1. Answer-first content. Every page opens with a direct answer to its primary question. This is what an AI engine extracts. No file changes this if your content buries the answer.
2. Schema markup. JSON-LD that tells engines what your content is, who wrote it, and how to read it. FAQPage nested in Article, Organisation with knowsAbout, and Speakable do real work here. We cover the specifics in our schema markup guide.
3. Entity clarity. Consistent naming, complete profiles, and sameAs links so engines can confirm who you are. An engine that cannot identify your brand will not cite it.
4. Topical depth. Clusters of connected articles, not single posts, so engines see authority on a subject.
5. llms.txt and llms-full.txt. The curated map, last, once the above is in place.

The order matters. Publishing llms.txt while your content has no schema and buries its answers is decorating a house with no foundation. The full method is in our AEO guide and the broader AI systems guide.

How to write one that earns its place

If you are going to publish it, do it properly:

• Curate, do not dump. The value is editorial. List your pillar pages and your most citable articles, not every URL. The sitemap already holds everything.
• Write real descriptions. One specific line per link that says what the page is and who it helps. "Our blog" is useless. "ROAS benchmarks by category for Indian D2C in 2026" is a description an engine and a person can both use.
• Group by intent. Pillar guides, articles, work, about, contact. Clear sections help a model understand your structure.
• Match your site. Names and descriptions should agree with what is actually on the pages and in your schema. Contradictions hurt more than the file helps.
• Keep it current. Update it when you publish a new pillar, and regenerate llms-full.txt on every deploy so it reflects the live site.

How we do it at Vikrama

We publish a curated /llms.txt and a generated /llms-full.txt. The curated file lists our pillar guides, our most citable articles, our live work, and how to reach us, each with a one-line description. The full file is built from our writing at deploy time, so it never drifts from what is actually published.

We treat it the way this article describes. It is the last layer, sitting on top of answer-first content, validated schema, and consistent entity signals. Those three do the heavy lifting. The file is the cheap, sensible bet on top. For an example of a build where this stack is in place from the foundation, see the Heritage Prime NCR work.

Want your site structured so AI engines cite you, with the schema and content that actually move the needle? Start with our audit. We will review your schema, content structure, and AI visibility, then give you a prioritised plan.