> Key takeaways
> - llms.txt is a plain-text file at your site's root (/llms.txt) that gives AI assistants a clean, curated map of your most important pages.
> - It complements robots.txt and sitemap.xml — it does not replace either of them.
> - Include your company one-liner, main product/service pages, case studies and contact page. Leave out every SKU, changing prices and thin pages.
> - AI platforms are not obliged to read it, and it is no guarantee of traffic — but it costs almost nothing to add and makes your site easier for AI tools to understand.
Buyers are changing how they search for suppliers. Alongside Google, importers and purchasing managers now ask AI assistants questions like "which factories in Guangdong make frameless shower enclosures?" or "find me an aluminium profile exporter that ships to Europe." The assistant answers from what it can read and understand about your website. That raises a practical question for manufacturers and exporters: when an AI tool looks at your site, what does it actually see — and can you make that easier?
One small, increasingly discussed answer is a file called llms.txt. This post explains what it is, what it is not, what a manufacturer should put in it, and how to add it to a website step by step.
## What llms.txt is
llms.txt is a plain-text file, written in a simple format called markdown, that lives at the root of your website — so it is reachable at yourdomain.com/llms.txt, in the same way robots.txt is. It was proposed in 2024 by Jeremy Howard of Answer.AI, and the idea is straightforward: give AI assistants a short, human-written guide to your site. Instead of an AI crawler having to work out what your business does from hundreds of product pages, navigation menus and pop-ups, it can read one clean page that says: here is who we are, here are our most important pages, and here is what each one covers.
The file has a simple structure. It starts with the site or company name as a heading, then a one- or two-sentence summary of the business. Below that come sections — for example "Products", "Services" and "About" — each containing links to key pages with a short description of what the reader will find there. There can also be a final section usually labelled "Optional", for useful but less important pages that an AI can skip when it only needs the essentials.
Well-known AI tools such as ChatGPT, Claude and Perplexity are the intended audience. When these systems browse or index the web, a clear llms.txt file can help them understand what a business does and which pages are worth citing or linking to when a buyer asks for a supplier.
We should be honest about the limits, because there is a lot of hype around this file. Adoption by the AI platforms is voluntary and still developing. No AI company has promised to read every site's llms.txt, and having one guarantees nothing — no rankings, no citations, no traffic. It is best understood as a low-cost piece of clarity: it takes little effort to create, it does no harm, and it makes your site easier for both AI tools and technically minded humans to understand. Our own site runs an /llms.txt file as part of its wider AEO and GEO setup for exactly that reason.
## What AI tools see on a typical factory website today
To understand why the file helps, picture how an AI system meets your website today. Most manufacturer sites are built for human browsing: a homepage with sliding banners, category pages, and then very large numbers of product pages. Those product pages often carry long specification tables, related-product carousels, enquiry forms, footers full of links, and product names written in internal factory codes rather than the words buyers use.
An AI crawler reading that gets a noisy picture. It has to spend its effort separating the real content from menus, banners and repeated blocks, and it may still misunderstand what the company actually sells — especially if the strongest information is buried in PDFs, images or pages written in another language. A sitemap tells the crawler which pages exist; it says nothing about which pages matter or what they mean. llms.txt fills exactly that gap: it is the one-page briefing you would hand to someone and say, "Start here — this is the business in twenty lines."
For exporters there is a second benefit. Your most persuasive material — your main product ranges, your export markets, your case studies and certifications — may sit several clicks deep. In an llms.txt file you can put it in a short ordered list, in plain English, with descriptions written in the language buyers use. That is the version of your business you would want summarised back to a buyer.
## llms.txt vs robots.txt vs sitemap.xml
These three files sit side by side at the root of a website and are often confused. They do different jobs:
| File | Written for | What it does |
|---|---|---|
| robots.txt | Search engine and other crawlers | Tells bots which parts of the site they may or may not crawl. It controls access; it describes nothing. |
| sitemap.xml | Search engines | Lists the site's URLs so crawlers can find every page. A map of addresses, with no explanation of what each page is. |
| llms.txt | AI assistants (and human readers) | A short, curated guide: what the business does, which pages matter most, and what each page covers, in plain language. |
The short version: robots.txt is about permission, sitemap.xml is about discovery, and llms.txt is about understanding. You need the first two regardless; llms.txt is an addition, never a replacement.
## What to include in your llms.txt
Think of the file as a one-page brief for your business. For a manufacturer or exporter, a good llms.txt usually contains:
- A one-line description of the company. What you make, where you are, and who you sell to. For example: "Manufacturer of glass door hardware in Foshan, exporting to Europe, the Gulf and North America." This single sentence is the most valuable line in the file.
- Your main product or range pages. Not every product — the pages for your main product families, the ones you would show a serious buyer first.
- Your services and capabilities pages. OEM/ODM services, custom manufacturing, quality control, packaging and export/logistics information, where these exist as pages.
- Proof pages. Case studies, certifications, factory tour or about pages — the material that answers "is this company real and capable?"
- Your contact page. The page you want a buyer to land on. If you also maintain a Google Business Profile, make sure the company description in the file matches it — consistency helps every system that reads about you.
- An "Optional" section for secondary material: blog posts, guides, FAQs and glossaries that add depth but are not essential.
## What to leave out
Restraint is the point of the file. Leave out:
- Every individual SKU. Hundreds of product links turn the file into a second sitemap and bury the pages that matter. Link the range pages instead.
- Prices that change. Prices in the file will go stale and may be quoted back to a buyer. Keep pricing on your website, where you control it.
- Thin or duplicate pages. Landing pages with a paragraph of text, near-identical regional pages, and anything you would not proudly show a buyer.
- Internal or technical pages. Login pages, test pages, staging copies and tracking URLs have no place in a public guide to your business.
A useful test: if you printed the file and handed it to a new sales agent, would they understand the company and know which pages to send a buyer? If yes, the contents are about right.
## An example llms.txt for a hardware exporter
Here is a short, fictional example for an imaginary exporter of glass door hardware. Yours would use your real pages and descriptions — this is purely to show the shape of the file:
# Brightway Hardware Co., Ltd.
> Manufacturer of glass door hardware — patch fittings, floor springs, shower hinges
> and sliding door systems — based in Foshan, China. Exporting to Europe, the Gulf
> and North America since 2009. OEM and ODM welcome.
## Main product ranges
- [Patch fittings for glass doors](https://www.example-hardware.com/products/patch-fittings/): Upper, lower and lock patch fittings for 10–12mm tempered glass doors.
- [Floor springs](https://www.example-hardware.com/products/floor-springs/): Hydraulic floor springs for glass and framed doors, 80–150kg capacities.
- [Shower hinges and seals](https://www.example-hardware.com/products/shower-hinges/): Brass and stainless hinges, knobs and water seals for frameless shower enclosures.
## Services and proof
- [OEM and custom manufacturing](https://www.example-hardware.com/services/oem/): Custom finishes, sizes and private-label packaging for importers and brands.
- [Case studies](https://www.example-hardware.com/case-studies/): Recent export projects and what was supplied.
- [About the factory](https://www.example-hardware.com/about/): Factory size, equipment, quality control and export markets served.
## Optional
- [Choosing shower glass hinges: a buyer's guide](https://www.example-hardware.com/guides/shower-glass-hinges/): Sizes, materials and load ratings explained.
## Contact
- [Contact us](https://www.example-hardware.com/contact/): Enquiries, samples and quotation requests.Notice what it does: twenty lines tell an AI assistant what the company makes, its three main ranges, its proof pages and where to send a buyer. No prices, no SKU list, no noise.
## How to add llms.txt to your website, step by step
Adding the file is simple, and on most websites it is a one-time task of under an hour:
1. Draft the content first. In a plain document, write your company one-liner, then list your 6–12 most important pages with a one-sentence description of each. Reuse the wording from your homepage and About page where it is already clear.
2. Create the file. Save it as a plain-text file named exactly llms.txt, following the structure above: heading, summary, sections with links and descriptions, an Optional section if needed.
3. Host it at the root. Upload it so it loads at yourdomain.com/llms.txt — the same level as robots.txt, not inside a subfolder. On a content-management system this is usually a file upload to the root directory, or a setting your developer can add in minutes.
4. Check it loads. Visit the URL in your browser. You should see the plain text of the file. If you see a "page not found" error, the file is in the wrong place.
5. Tell the crawlers it exists (optional but tidy). Your developer can reference it from robots.txt with a line pointing to the file, so bots that look there first can find it. This is a nicety, not a requirement.
6. Keep it current. Whenever you add a major page, retire a range or change your markets, update the file. An llms.txt that describes last year's business is worse than none.
If your website is one we build or manage for you, this is included in the setup work alongside your sitemap and robots settings — and if you'd like the wider picture checked at the same time, our free audit covers how your site currently presents itself to both search engines and AI tools.
## Honest expectations
It is worth repeating the caveat plainly, because vendors are already overselling this file. llms.txt is a proposal, not a standard enforced by anyone. Some AI tools read these files today; others ignore them; the situation will keep changing. Adding one will not, by itself, bring enquiries, and any agency that promises rankings or AI citations from a text file is selling you something it cannot control. For the wider technical work around it — schema, speed, clean content — see our technical SEO services.
What it does do is cheap and sensible: it states, in one place and in plain language, what your business is and which pages prove it. That helps any system — AI assistant, search engine or human researcher — that tries to summarise your company. Combined with the unglamorous basics (a crawlable website, clear product pages, consistent business details across the web), it makes you easier to understand and easier to recommend. That is the whole claim, and it is enough to justify an hour's work.
Frequently asked questions
Does llms.txt replace robots.txt or my sitemap?
No. The three files do different jobs. robots.txt controls which parts of your site crawlers may access, sitemap.xml lists your pages so search engines can find them, and llms.txt explains your business and highlights your most important pages. Keep all three.
Will adding llms.txt improve my Google rankings?
There is no evidence that it affects Google rankings, and that is not what it is for. It is aimed at AI assistants that read and summarise websites. Think of it as clarity for AI tools, not as an SEO ranking lever.
Which AI tools read llms.txt?
The file was designed for AI assistants such as ChatGPT, Claude and Perplexity, and tools in the AI development world have adopted it most widely so far. Uptake by the major consumer AI platforms is voluntary and still developing, so treat it as a low-cost way to be ready rather than a guaranteed channel.
What should a manufacturer put in the file?
A one-line description of what you make and who you sell to, links to your main product range pages (not every SKU), services and capabilities pages, case studies and other proof, and your contact page. An Optional section can hold guides and blog posts. Leave out prices that change and thin pages.
How often should I update it?
Whenever your important pages change: a new product range, a retired line, new markets, a new case study. For most exporters, reviewing it every few months alongside your website content is enough. An out-of-date file that describes products you no longer sell can mislead, so keep it in step with the site. --- If you'd like an honest look at how AI tools and search engines currently see your website, start with our free audit. We check how your site presents itself to buyers, search engines and AI assistants, and send you the first fixes we would make, in order. If you'd rather have it handled for you, our SEO service ($499 setup, then $189/month) and catalogue websites (from $1,499) include this kind of groundwork as standard — and it starts with the same free audit.
