What Is llms.txt? A Plain-English Guide for Business Owners

An llms.txt file is a short text document written in Markdown, the same simple formatting language people use for notes and documentation. It lives in the root of your website, so anyone (or any bot) can find it at a predictable address like yoursite.co.nz/llms.txt.

Inside, you describe your business in a sentence or two, then list the pages that matter most, each with a link and a short note about what's on it. Think of it as the cheat sheet you'd hand a new staff member on day one. Here's what we do, here's who we do it for, and here are the five pages that explain everything else.

The idea came from Jeremy Howard of Answer.AI, who published the proposal at llmstxt.org in September 2024. It's a community proposal, not an official web standard from a body like the W3C, and nobody is forced to read it. That detail matters, and we'll come back to it.

Modern web pages are noisy. A single service page might carry a cookie banner, a navigation menu with forty links, tracking scripts, pop-ups, a chat widget, and a footer the size of a small novel. Humans skim past all that without thinking. A language model trying to pull out the useful bits has to wade through it.

AI tools also work within limited context windows, meaning there's only so much text they can consider at once. Feeding a model your entire website is like asking someone to understand your business by handing them every invoice you've ever sent.

llms.txt is meant to solve that. Instead of making the AI guess which pages matter, you tell it. Clean text, clear priorities, no clutter. It's especially handy for software documentation, where developers point AI coding assistants at docs sites.

For a local plumber or accountant, the benefit is less obvious. Which brings us to the comparison most people actually want.

Three files, three very different jobs. People mix them up constantly, and some quotes we've seen treat llms.txt as a replacement for the other two. It isn't.

The key difference is control versus guidance. robots.txt controls access. If you want to block a particular AI crawler, that's where you do it. llms.txt controls nothing. It's a polite suggestion about what to read first.

A sitemap is also a different animal. It tries to list everything indexable. llms.txt is deliberately short and selective. A good one leaves most of your site out on purpose.

Honest answer: a little, in narrow cases, and nothing you can measure for most small businesses.

Google has been openly sceptical. John Mueller of Google's Search team compared it to the old keywords meta tag, the one site owners stuffed for years while search engines quietly ignored it. Google's position is that its AI features, including AI Overviews, draw on the normal Search index, so the same fundamentals in its SEO starter guide still apply. No special file required.

Other AI companies haven't publicly committed to treating llms.txt as a ranking or citation signal either. Where the file does get used today is mostly on demand: a developer pastes the URL into an assistant, or a tool built for documentation fetches it to load context.

An llms.txt file is a well-labelled filing cabinet. Useful if someone opens it. Completely invisible if nobody does. It won't make a weak website persuasive, and it won't make an invisible website findable.

This could change. AI search moves fast, and a file that's ignored today might be read routinely next year. That's the real argument for having one: it costs almost nothing, does no harm, and positions you well if adoption grows. Just don't let anyone sell it to you as the thing that gets you into ChatGPT answers.

Not every business needs to rush this. Here's a practical way to decide.

If your site falls in the second group, llms.txt is rearranging the shelves while the shop door is locked. Fix the fundamentals first. If Google can't find you, start with our guide on why your website isn't showing up on Google.

The proposal keeps the format deliberately simple. Sections appear in a set order, and only the first one is strictly required.

1. An H1 title. The name of your business or site, written as a Markdown heading with a single hash. This is the only required part.
2. A blockquote summary. One or two sentences covering what you do, who for, and where. This is the line most likely to be quoted, so make it count.
3. Optional detail. A few short paragraphs or bullet points with key facts, such as service areas, opening hours, or what makes you different. No extra headings here.
4. H2 sections with link lists. Groups like Services, About, or Pricing, each holding Markdown links in the format of a name in square brackets, the URL in round brackets, then an optional colon and a short note.
5. An Optional section. A final H2 titled Optional for secondary links that a tool can skip if it needs to keep things short.

Here's a sample structure for a made-up plumbing business. The name and URLs are placeholders, so swap in your own details.

# Example Plumbing Co.

> Licensed plumbers serving homes and small businesses across Napier and Hastings, New Zealand. Emergency callouts seven days a week, free quotes for planned work.

- Service area: Napier, Hastings, Havelock North, Taradale
- Hours: Mon to Fri 7am to 5pm, emergency line 24/7
- Licensed and certified, fully insured

## Services
- [Emergency plumbing](https://example.co.nz/emergency): callout areas, response times, callout fee
- [Hot water cylinders](https://example.co.nz/hot-water): repair, replacement, heat pump systems
- [Blocked drains](https://example.co.nz/drains): drain clearing and camera inspections

## About and trust
- [About us](https://example.co.nz/about): team, licensing, years operating
- [Reviews](https://example.co.nz/reviews): customer reviews and ratings

## Pricing and booking
- [Pricing guide](https://example.co.nz/pricing): typical price ranges and callout fees
- [Book a job](https://example.co.nz/contact): booking form, phone, and email

## Optional
- [Blog](https://example.co.nz/blog): maintenance tips and seasonal guides

Notice what's missing. No privacy policy, no tag archives, no thank-you page, no twelve near-identical location pages. The file points at the pages that answer real customer questions, which is exactly what an AI tool would need to describe the business accurately.

This is the practical bit. Most small business owners can get through it in under an hour, and a good chunk of that is deciding which pages actually matter.

1. Pick your priority pages. Choose five to fifteen pages that explain your offer: homepage, core services, pricing, about, reviews, and contact. If a page wouldn't help a stranger understand your business, leave it out.
2. Write the summary line. One or two plain sentences covering what you do, who it's for, and where you operate. Avoid slogans. AI tools are about as moved by taglines as your accountant is.
3. Add short notes to each link. A few words after each URL saying what the page covers. These notes are the main value of the file, so be specific.
4. Save it as a plain text file. Use any basic text editor, name it exactly llms.txt, and save it with UTF-8 encoding. Don't use a word processor, which can add hidden formatting.
5. Upload it to your site root. On WordPress or a custom build, this usually means uploading to the main folder by FTP or your host's file manager, and some WordPress SEO plugins can now generate the file for you. On hosted builders like Wix, Squarespace, Shopify, or Webflow, support varies and changes, so check your platform's current help docs.
6. Test it and set a reminder. Visit yoursite.com/llms.txt in a browser and check it loads as plain text. Then put a calendar reminder in for every few months, or whenever you add or remove a service.

You'll see two related ideas mentioned alongside llms.txt.

The first is llms-full.txt, a convention where the full text content of your key pages is bundled into one large Markdown file. Documentation platforms popularised it, because developers like loading an entire docs set into an AI assistant in one go. For a ten-page service business website, it's usually overkill.

The second comes from the original proposal itself: offering a clean Markdown version of individual pages, at the same URL with .md added on the end. Most local businesses can skip it without losing anything.

The bigger lesson is that both ideas try to fix the same problem. AI tools struggle with cluttered pages. The more durable fix is building pages that are clean in the first place, with real headings, real text in the HTML, and the important information near the top.

Because the format is so simple, most mistakes are about judgement rather than syntax.

• Listing every page. The file is meant to be curated. Dumping your whole sitemap into it defeats the point.
• Writing marketing copy. Phrases like industry-leading solutions tell an AI nothing. Plain facts about services, areas, and prices tell it plenty.
• Linking to broken or redirected pages. Check every URL works. A cheat sheet full of dead ends is worse than no cheat sheet.
• Contradicting your actual site. If the file says you serve three towns and your site says five, you've created confusion where you wanted clarity.
• Forgetting to update it. Prices change, services get dropped, pages move. A stale file quietly spreads outdated information.
• Treating it as access control. llms.txt can't block anything. If you want to stop a crawler, that job belongs to robots.txt.
• Paying a premium for it. Writing the file is a small task. If it's quoted as a major project, ask what else is included.

If you actually want AI tools to mention your business, the file is maybe the tenth most important job on the list. The first nine look a lot like good SEO and clear writing.

Our guide to getting your business cited by ChatGPT covers the trust and consistency side in detail. If Google's AI answers are your main concern, read how to rank in Google AI Overviews, and for the bigger picture, our explainer on what answer engine optimization actually is ties it all together.

A website that explains itself clearly will get more out of AI search than a vague website with a perfect llms.txt. Every time.

We add an llms.txt file to new builds as standard, because it takes minutes and costs nothing extra. We don't charge for it separately and we don't pretend it's a growth strategy. The real AI visibility work happens in the structure, copy, and technical setup of the pages themselves.

Being honest: we're a young studio, so we lead with clear scope and careful work rather than a wall of case studies. If you'd like to know whether your current site is readable by AI tools and Google, request a free website audit and we'll point out what to fix first. If you're already planning a new site, compare our website packages and pricing to see what's included at each level.

So, what is llms.txt? A short, sensible Markdown file that tells AI tools which of your pages matter. It's worth having, it's easy to make, and it's nowhere near as powerful as some people selling it suggest.

Write one in under an hour, keep it honest, and update it when your business changes. Then put your real energy into pages that answer customer questions clearly, because that's what humans, Google, and AI tools all reward.

Not sure whether your site is ready for AI search? Start with a free audit and get a plain-English list of what's working, what's missing, and what to fix first.