--- title: "llms.txt examples: real files, explained" url: https://hostmy.blog/docs/rankready/llms-txt-examples/ date: 2026-08-25 modified: 2026-08-25 lang: en author: "Aditya Sharma" description: "Real llms.txt examples, from a minimal file to a fuller one with sections, plus what RankReady generates and what publishing it actually achieves." word_count: 767 --- # llms.txt examples: real files, explained ## What an llms.txt file actually looks like An llms.txt file is a plain Markdown document at the root of your site. It opens with your site name as an H1, then a one-line summary inside a blockquote, then headed sections that list your key pages as Markdown links. Each link carries a short note saying what that page covers. That is the whole format. The point is a clean, predictable map of your site that a machine can read without parsing your theme, your scripts or your cookie banner. RankReady serves it at `/llms.txt`, so once the feature is on, any client can request `yourdomain.com/llms.txt` and get exactly this structure back. ## A minimal example The smallest useful file is a title, a summary and a short list of pages. This is enough to describe a small brochure site: `# Acme Coffee Roasters > Small-batch coffee roaster in Bristol, shipping fresh beans across the UK. ## Pages - [Shop](https://acmecoffee.co.uk/shop): current single-origin lots and house blends - [About](https://acmecoffee.co.uk/about): the roastery, our sourcing and the team - [Contact](https://acmecoffee.co.uk/contact): wholesale enquiries and support ` Notice there is no marketing copy and no long prose. The summary is one sentence. Every link does one job: it names a destination and says, in a few words, what is there. ## A fuller example with sections On a real content site you group pages under headed sections so the structure carries meaning. Common headings are `## Docs`, `## Blog`, `## Shop`, but you choose whatever matches your site: `# Acme Coffee Roasters > Small-batch coffee roaster in Bristol, shipping fresh beans across the UK since 2014. ## Docs - [Brewing guide](https://acmecoffee.co.uk/brew): ratios and methods for pour-over, French press and espresso - [Grind chart](https://acmecoffee.co.uk/grind): matching grind size to your brewer - [Subscription FAQ](https://acmecoffee.co.uk/faq): billing, pausing and delivery windows ## Blog - [How we score a new origin](https://acmecoffee.co.uk/blog/cupping): our cupping process, explained - [Water and taste](https://acmecoffee.co.uk/blog/water): why your tap water changes the cup ## Shop - [Single origin](https://acmecoffee.co.uk/shop/single-origin): current lots with tasting notes - [Blends](https://acmecoffee.co.uk/shop/blends): house blends for espresso and filter ` The sections do the heavy lifting. A reader, human or machine, can tell at a glance that you have reference material under Docs, opinion under Blog and products under Shop, before following a single link. ## What RankReady generates for you You do not hand-write these files in RankReady. Under **AI Visibility, llms subtab**, RankReady builds `/llms.txt` from your published content and your [Brand Identity](https://hostmy.blog/docs/rankready/brand-terms-setup/). The H1 is your site or brand name, the blockquote is your one-line summary, and the sections are drawn from your pages and posts. It stays current as you publish. There is also `/llms-full.txt`, an optional second file. Where `/llms.txt` is an index of links, `/llms-full.txt` inlines the actual Markdown of your content into one file, so a client can read the corpus without following every link. It is off by default because it is larger. Turn it on when you want the full text available at a single address. ## What a good example does that a bad one does not A good llms.txt is short, specific and honest. Each summary describes the page in plain terms. A weak file makes three mistakes: it stuffs the summary with keywords instead of describing the page, it lists dozens of thin or duplicate URLs so the signal drowns, or it lets the link notes rot until they no longer match what is on the page. A file that lies about its own pages is worse than no file, because anything reading it now has to distrust all of it. Keep the list to pages you would actually point a person at. Write each note the way you would describe the page to a colleague. That is the entire discipline. ## An honest note on what publishing this achieves Publishing llms.txt makes your content available at a predictable address, and it lets clients that look for the file discover your structure without crawling your HTML. That is what it does. It does not guarantee any AI reads the file or quotes your pages. In an Ahrefs study of 137,000 domains, 97% of llms.txt files received zero requests. A file being served is not the same as a file being read. Treat llms.txt as a clean front door you have chosen to open, not as a promise that anyone walks through it. ## Next steps If you have not switched the file on yet, see **How to [add llms.txt](https://hostmy.blog/docs/rankready/how-to-add-llms-txt-wordpress/) to WordPress** for the exact toggle and how to confirm the file is live. To understand the second, heavier file and when it earns its place, read **What is [llms-full.txt](https://hostmy.blog/docs/rankready/what-is-llms-full-txt/)**.