# llms.txt generator

Write the one file that tells an assistant what your site is: from the site itself, read page by page from its sitemap, or from a name, a line and a list of pages in sections. Then check the one a site already has against the proposal, link by link. A courtesy, not a ranking factor, and a cheap one.

Updated 2026-09-14 · Source: https://porteur.ai/tools/llms-txt-generator

## What an llms.txt is

A plain text file at the root of a site, /llms.txt, written in Markdown, that tells a language model what the site is and which pages to read. The proposal is simple on purpose: an H1 with the name, a blockquote with one sentence, optional paragraphs, then sections of links with a line each. A companion file, /llms-full.txt, can carry the full text of the pages for a reader that wants everything at once.

It exists because an assistant reading a site does not get a home page the way a person does. It gets HTML, often built by scripts it does not run, with a menu and a footer repeated on every page. A short file in its own format is easier to read than the site, and it is where you say what you would say to a new hire in ten lines.

## How to write one

1. **Read the site** Paste the address and the tool reads the home page for the name and the summary, then up to forty pages from the sitemap, spread across the site's folders, with the title and the description of each. They arrive grouped by folder as sections.
2. **Cut, then order** An assistant with thirty seconds does not need the privacy policy first. Keep the pages that say what the product is, what it costs, how it works and what it is for; move the rest to Optional or delete the line.
3. **Write the summary** The blockquote is the sentence most readers take first: what it is, for whom, and what makes it different, in one line. The description of the home page is a start, rarely the finish.
4. **Name the sections** A line that starts with two hashes opens a section: Docs, Pricing, Guides. Each page line is label, address, and one line on what the page holds, separated by vertical bars.
5. **Serve it and check it** Copy or download the file, serve it at /llms.txt as plain text, then paste the site into the checker below: it reads the file back, fetches its links, and says what is missing.

> Write the file for a reader who has never seen your site and has thirty seconds. Every line that would not help that reader is a line to cut.

## How to read the check

- **Found and in shape** means an H1 first, a blockquote summary, sections of links, and every link fetched answers 200. Nothing to do but keep it current.
- **Things to fix** are listed in sentences: no H1 first, two H1 lines, no summary, links outside any section, bare URLs without a label, links without a description, links that answer 404 or redirect, HTML where Markdown should be.
- **Sections** shows each H2 with the number of links under it, and whether an Optional section exists (it is optional in itself: it marks what a reader short on room may skip).
- **Links checked** fetches up to thirty of the links; the table lists the ones that do not answer 200 directly, with the section each sits in.
- **llms-full.txt** says whether the companion file exists. It is optional: the full text of the pages as Markdown, for a reader that wants it all in one fetch.

## What it changes, and what it does not

Nothing about your Google rankings. Google has said nothing about llms.txt, and there is no evidence it reads the file. What it changes is how well an assistant that does read it understands your site, and which of your pages it opens first. Several assistants and crawlers fetch it today; more will.

It also does not open a door that robots.txt has closed. An assistant's crawler blocked in robots.txt does not read llms.txt either. Check the crawler access tool below before you spend time on the file.

## Limits

The generator reads titles and descriptions; the words are yours, and the words are what matters. It reads up to forty pages from the sitemap and the home page; a site without a sitemap gets the home page alone, and the rest is typed. The check reads the shape of the file and fetches thirty of its links, not all; a file of three hundred links is judged on its first thirty. Neither says whether any assistant reads the file: adoption is on the vendors, and as of 2026 none has committed to it.

## Questions

### Where does llms.txt go?

At the root of the site: https://yoursite.com/llms.txt, served as plain text. Not in a subfolder, and not behind a redirect.

### What is the difference between llms.txt and llms-full.txt?

llms.txt is the short map: the name, a sentence, the pages worth reading. llms-full.txt is optional and carries the full text of those pages, for a reader that wants everything in one file.

### Does llms.txt help SEO?

Not with Google, as far as anyone can show. It helps assistants that read it understand the site and pick the right pages, which is a different thing and, increasingly, a source of visits.

### Is there an llms.txt example?

Yes: the generator above shows one as you type, and porteur.ai/llms.txt is the one this site serves.

### What does the check flag?

The shape the proposal describes: an H1 as the first line and only one, a blockquote summary, H2 sections holding links in the form of a label, an address and one line, an Optional section for what a reader may skip. Then the links: it fetches up to thirty and lists the ones that answer an error or redirect. A file that fails the shape is still read by a model; it is just harder to use.

## Read next

- [llms.txt: what it is, examples, and how to write yours](https://porteur.ai/guides/llms-txt): llms.txt is a Markdown file at /llms.txt that maps your site for language models. See the format, a worked example, and write yours in twenty minutes.
- [Generative engine optimization (GEO): how to be named by AI answers](https://porteur.ai/guides/generative-engine-optimization): How to get your site named in AI answers: sources, crawlers, lists, structure, llms.txt, comparisons, and how to measure by asking assistants.
- [robots.txt for AI crawlers: GPTBot, ClaudeBot, PerplexityBot and what to allow](https://porteur.ai/guides/robots-txt-for-ai-crawlers): Decide which AI crawlers to allow in robots.txt, why it matters, and copy‑paste examples for GPTBot, ClaudeBot, PerplexityBot, Google‑Extended and more.
- [AI crawler access checker](https://porteur.ai/tools/ai-crawler-access-checker): Paste a site or a page and see, crawler by crawler, whether it may read it: root and page, the rule that decides, the text without JavaScript, llms.txt.
- [llms.txt](https://porteur.ai/glossary/llms-txt): llms.txt is a Markdown file at /llms.txt that maps your site for AI agents. See what to put in it, how to publish it, and the traps to avoid.
- [AI crawler](https://porteur.ai/glossary/ai-crawler): An AI crawler is a bot that fetches your pages for an AI. See the main bots, how to spot them in logs, and how to allow or block them well.
- [Social preview checker](https://porteur.ai/tools/social-preview-checker): Paste a URL and see the card a share produces on X, LinkedIn and Slack: the Open Graph tags read, the image fetched and measured, and what to fix first.

The file tells an assistant what you are. The free check tells you whether the assistants name you at all: the AI answers on your searches, and who they quote instead. Free check: https://porteur.ai/