What llms.txt is, what it is not, and how to write one
llms.txt is a markdown summary of your site for language models to read in one go. What belongs in it, what to leave out, and why ours has no prices in it.
llms.txt is a proposal for a small markdown file at the root of a site: one heading, a one-paragraph summary, then lists of links to the pages that matter, each with a line saying what is there. The idea is that a model can read the whole site's shape in one request instead of scraping twenty pages of markup.
What it is not
- Not a ranking signal for Google, and not a sitemap replacement.
- Not guaranteed to be read; support across assistants varies.
- Not a place for anything that changes faster than you rebuild.
A shape that works
# AI Skill Up
> Claude Code skills built to one standard...
## Skills
- [Glass Instrument UI](https://aiskillup.online/skills/glass-instrument-ui/): ...
## Guides
- [Why your Claude Code skill does not fire](...): ...Ours is generated in the same build step as the sitemap, from the same data, so it cannot list a page that does not exist or miss one that does.
Why ours has no prices and no scores
A price exists in one place on our site, and every other surface reads it from there. A static text file that an assistant may have fetched last month is not one of those places. The same goes for any measured number: if a model quotes it after it changes, we published something false. So each line links to the page that holds the current figure. Write your llms.txt as a map, not a copy.
It works best alongside a robots.txt that actually lets assistants in, covered in robots.txt for AI crawlers.
Questions
What is llms.txt?
A proposed convention: a plain markdown file at /llms.txt that summarises a site and links to its key pages, so a language model can understand it without crawling and parsing every page of HTML.
Does llms.txt improve Google rankings?
No. It is not a Google ranking signal and not a replacement for a sitemap. It is aimed at assistants and tools that choose to read it, and support for it varies.
Should llms.txt include prices?
Only if you can guarantee it updates the moment a price does. An assistant repeating a stale price is worse than one that links to the product page, which is why ours links instead.