# llms.txt Generator — Examples

> Hands-on walkthroughs with the llms.txt Generator: build an llms.txt for a company site, adapt a template, and validate and fix an existing file.

Source: https://www.jpkc.com/db/en/tools/llms/examples/

Back to the overview: [llms.txt Generator](https://www.jpkc.com/db/en/tools/llms/) · Open the tool: [www.jpkc.com/tools/llms/](https://www.jpkc.com/tools/llms/)

The [manual](https://www.jpkc.com/db/en/tools/llms/manual/) explains every field, every tab, and every validator rule in detail. This page complements it with **concrete workflows**: typical tasks played out step by step. The tool's interface is in English, so tab and button names appear here exactly as you'll see them in the live tool.

## Example 1: Build an llms.txt for a company site from scratch

You want to give your company website an `llms.txt` so AI systems capture your product, help, and contact cleanly.

1. Open the [generator](https://www.jpkc.com/tools/llms/). You land in the **Generator** tab.
2. Put the company or product name into **Project / Site Name** — it becomes the H1: `# My Company`.
3. Write a single, precise sentence in **Tagline** stating what you do: "Accounting software for small trade businesses." In the output it appears as a blockquote `> …` right under the title. This is the most important field — it's where the AI reads first.
4. Optionally add one or two sentences in the **Intro Paragraph** field (audience, what sets you apart).
5. Build the **sections**: click **Add Section**, name the first one "Product", and add the key pages via **Add Link** — each with a *Link title*, *URL*, and a short *Description*. For example `Features`, `Pricing`, `Changelog`. Add more sections, such as "Help" (Getting started, FAQ) and "About" (Team, Contact).
6. Read along in the output editor on the right as the Markdown grows. When it's right, click **Download** — you get the finished `llms.txt` file.
7. Upload it to your web root so it's reachable publicly (without a login) at `https://yourcompany.com/llms.txt`.

The result is a curated, valid file — not a sitemap dump, but exactly the pages you want an AI to know about you.

## Example 2: Start faster with a template

Instead of starting from zero, grab a matching structure as scaffolding.

1. Switch to the **Examples** tab. Four templates live there: **Open-Source Library**, **SaaS Product**, **Blog / Personal Site**, and **Documentation Site**.
2. Pick the one closest to your project — for a product website, say **SaaS Product** with its *Product*, *Help Center*, and *Developers* sections.
3. Click **Load into Generator**. The tool jumps to the Generator tab and fills the form with the example structure.
4. **Now replace the example data** with yours: name, tagline, real URLs, and descriptions. Delete what you don't need, add what's missing — you can reorder sections by drag and drop via the grip handle.
5. **Copy** or **Download**, done.

The **Documentation Site** template is especially instructive: its *Guides* section shows **H3 subsections** (Frontend, Backend) — so you can see how to subgroup links within a section.

## Example 3: Validate an existing llms.txt

You've published (or someone else has) an `llms.txt` and want to know whether it matches the specification.

1. Go to the **Check** tab.
2. Type the domain into the field — `example.com` is enough, the tool appends `/llms.txt` itself. Alternatively, a full URL.
3. Click **Check**. The server-side proxy fetches the file, your browser validates it.
4. **Read the coloured status banner first.** Green ("Structure looks valid.") means no errors, no warnings. Yellow gives the number of warnings, red the number of errors.
5. Look at the **Summary** table: detected title, tagline, number of sections and links, file size. If something's already off there (e.g. "— missing —" for the tagline), you know where it hurts.
6. Work through the **Errors** and **Warnings** lists — each message cites the line number. What each message means is in the [manual under "What the validator checks"](https://www.jpkc.com/db/en/tools/llms/manual/#what-the-validator-checks).

Important: the checker validates **structure and format**, not the reachability of the linked pages — a green file can still point to dead links.

## Example 4: Fix a third-party file — Check, Load, Fix

The elegant workflow when a check shows errors: keep working right in the tool.

1. Check the file as in Example 3 in the **Check** tab.
2. Expand the **Raw content** block to see the original content with line numbers.
3. Click **Load into Generator**. The tool parses the fetched file and fills the form with it — you're now in the generator.
4. **Fix the reported items:** if the tagline was missing (a common error), enter it in the **Tagline** field. If everything was in one section, break it up into thematic blocks via **Add Section**. If links had no description, fill in the *Description* fields.
5. **Download** the corrected file and replace the old one in the web root.
6. To verify, check the domain once more in the **Check** tab — the banner should now be green.

That turns "third-party file with issues" into a clean, valid `llms.txt` in a few minutes.

## Example 5: Maintain an editable file over time

Your site has grown, the `llms.txt` is out of date.

1. In the **Generator** tab, click **Open File** and open the current `llms.txt` from disk. The tool parses it and fills the form — title, tagline, intro, all sections, links, and subsections.
2. Add new pages, remove retired ones, refresh descriptions. (The generator remembers your state locally in the browser anyway, in case you close the tab in between.)
3. **Download** the updated file and deploy it.

The `Open File` → edit → `Download` loop is the maintenance cycle: the `llms.txt` stays a living document, not a one-off artifact.

## Example 6: Point to an llms-full.txt

You have (or generate) a combined full-content file and want to link to it correctly.

1. In the generator, enter the address in the **llms-full.txt URL** field at the bottom, e.g. `https://yourdomain.com/llms-full.txt`.
2. The generator automatically appends a `## Optional` section with the line `- [llms-full.txt](…): Complete documentation combined into a single file` — exactly the convention the specification calls for.
3. **Download** and upload.

What `llms-full.txt` is and when it's worth it is in the [manual under "llms-full.txt"](https://www.jpkc.com/db/en/tools/llms/manual/#llms-full-txt-the-combined-content-file).

---

Going deeper: the [manual](https://www.jpkc.com/db/en/tools/llms/manual/) for every field and rule, the [tips & tricks](https://www.jpkc.com/db/en/tools/llms/tips/) for strategy and pitfalls. You can try all of it directly in the [tool](https://www.jpkc.com/tools/llms/).