G
GEO Toolbox

Free llms.txt tool

Free llms.txt Generator

Paste your domain and get a spec-correct llms.txt built from your own sitemap — real titles, real descriptions, grouped into sections, with the pages that don't belong in an AI index left out. Free, no sign-up, and honest about what llms.txt does and doesn't do.

We read your sitemap, respect your robots.txt, and fetch up to 50 pages for titles and descriptions. Free, no sign-up.

Straight answer

Read this before you spend an afternoon on llms.txt

It is not a ranking or citation signal.Google's Search Central docs say you don't need to create any AI-specific file or markup to appear in AI features, and Googlers have said llms.txt specifically isn't used — John Mueller, June 2025: "FWIW no AI system currently uses llms.txt."Worth being precise: that's an informal comment, not a documented policy, and Google's official pages never name the file. Either way, anyone selling it as a shortcut to getting cited is guessing.

It is a real convention with real readers.Chrome's Lighthouse 13.3 added an agentic-browsing audit that validates your llms.txt's format — it wants an H1 and at least one markdown link, and fails the audit outright if the file returns a 5xx. Not having one at all is marked not-applicable rather than failed. Some IDE assistants and custom agents read it too.

There's a genuine tension there worth noticing: Search says you don't need the file, while Chrome ships an audit that grades it.

So: cheap hygiene, not a growth lever.A clean, curated file with working links costs you ten minutes and can't hurt. That's the honest case for it, and it's why this tool is free and takes one input — spending an afternoon hand-writing one would be the actual mistake.

From a domain to a publishable file in three steps

  1. 01Paste

    Just your domain

    No need to know where anything lives. We read your robots.txt, find your sitemap, and use it as the source of what your site considers important — falling back to a homepage link harvest if there's no sitemap.

  2. 02Curate

    The pages worth pointing at

    We fetch up to 50 pages for their real titles and descriptions, skip the pages an AI index has no business listing (login, cart, tag archives, pagination), drop localized duplicates, and spread the selection across sections instead of letting one blog fill the file.

  3. 03Publish

    A file you can edit and ship

    You get a spec-correct llms.txt to copy or download, optionally with a companion llms-full.txt containing page text. Edit it down before publishing — a short, sharp index beats a complete one.

The format

What a good llms.txt looks like

One H1 with your site name (the only part the spec requires), an optional one-line summary as a blockquote, then section headers with curated links:

# Acme Docs

> Everything you need to build on Acme.

## Getting started

- [Quickstart](https://acme.com/docs/quickstart): Ship your first integration in ten minutes.
- [Authentication](https://acme.com/docs/auth): API keys, OAuth, and rotation.

## Reference

- [API reference](https://acme.com/docs/api): Every endpoint, with examples.

The most common mistake is treating it as a second sitemap. It isn't one — a 4,000-link llms.txt is worse than a 30-link one, because the whole value is in having chosen. That's why this generator caps what it indexes and hands you editable text rather than publishing for you.

For the full background, adoption data and whether it's worth your time, read llms.txt: what it is and whether it's actually worth it. When you've published, validate it with the llms.txt checker — it resolves every link and scores the result.

FAQ

llms.txt, answered honestly

  • 01What is an llms.txt file?
    A plain-markdown file at your site root (yourdomain.com/llms.txt) that gives AI systems a curated index of your most useful pages. The spec is small: one H1 with your site name (the only required part), an optional one-line "> summary", then "## Section" headers listing links as - [Page](url): note. A companion /llms-full.txt can hold full page text.
  • 02Does llms.txt actually help me get cited by AI?
    There's no evidence that it does, and we'd rather say so than sell you something. Google's docs say you don't need any AI-specific file to appear in AI features, and John Mueller said in June 2025 that "no AI system currently uses llms.txt" — an informal comment rather than documented policy, but nobody has since documented the opposite. What it is: a recognized convention that some IDE assistants and custom agents read, and Chrome's Lighthouse 13.3 ships an agentic-browsing audit that validates its format. Treat it as cheap hygiene, not a growth lever. If you want the thing that genuinely affects whether AI can use your site, that's crawler access and rendering — our AI Crawler Checker covers it.
  • 03How does this differ from typing the file by hand?
    Speed and accuracy on the boring part. Hand-writing means finding every URL, copying titles, and keeping it current. This reads your sitemap, pulls the real titles and meta descriptions from the live pages, and groups them into sections automatically. The curation judgment is still yours — that's why the output is editable text rather than something we publish for you. If you'd rather build it link by link, the manual builder on the checker page does exactly that.
  • 04Why did it leave out some of my pages?
    By design, and it tells you what it dropped. llms.txt is meant to be a curated index, not a sitemap dump, so we cap at 50 pages and spread them across sections rather than letting one section dominate. We also skip pages that don't belong in an AI index — login and account flows, carts and checkouts, tag and category archives, pagination stubs — and skip localized duplicates like /fr/ and /de/, since they're translations of pages already listed. Anything a site disallows in robots.txt is skipped too.
  • 05Do you respect robots.txt when fetching my pages?
    Yes, and it would be indefensible not to — we also publish a tool that audits crawler access. We parse your robots.txt with Google's precedence rules and skip any URL it disallows, then report how many we skipped. Our fetcher identifies itself as GeoToolboxLlmsTxtGenerator with a link back to this page.
  • 06What is llms-full.txt, and should I publish one?
    It's the companion file holding actual page text rather than just links, so an agent can read your content without fetching every page. Tick the box and we'll build one, at a lower page count since it's much heavier. Whether to publish it is a judgment call: it's useful for documentation sites where you want assistants working from your real text, and mostly pointless for a marketing site whose pages are already fast to fetch.
  • 07Is there a page limit, and is it really free?
    50 pages for llms.txt, 20 for llms-full.txt, and there's a 45-second time budget on very large sites. Free with no sign-up and no email wall. There's no LLM or paid API behind this — it's your sitemap plus some page fetches — so there's nothing for us to meter.

llms.txt is one optional file. Can AI agents reach the rest of your site?

The AI Crawler Checker shows which of 34 AI crawlers — GPTBot, ClaudeBot, PerplexityBot — your robots.txt allows or blocks, with the exact line to fix. That one actually moves the needle. Free.

Check your AI crawler access