Skip to content
tregix

// free tool

Give AI assistants a map of your site.

Check whether your llms.txt is valid and complete, and get a generated one built from your title, description and sitemap either way.

Checks any existing llms.txt against the format, and generates a replacement from your title, description and sitemap either way.

Questions

What is llms.txt?

A markdown file at your domain root that gives AI assistants a curated map of your site: an H1 name, a one-line summary, then sections of links. It's a short editorial index, not an exhaustive URL list like sitemap.xml.

Is it an actual standard?

It's a convention, not a ratified standard, and adoption is uneven: no major AI vendor has committed to reading it on every request. It costs one static file to publish, which is what makes it worth doing: near-zero cost, real upside if the convention holds.

What does the generated file use?

Your page title, meta description and sitemap URLs, grouped by first path segment. It's deterministic and templated, with no LLM involved, so the same site always produces the same file and it costs nothing to run.

Should I edit it before publishing?

Yes. The generated file is a solid starting point built from what we can see, but the discipline is editorial: link the pages you want cited, not every page you have. Trim it.

What about llms-full.txt?

That's the expanded companion: the actual content flattened to markdown, so an assistant can read once instead of crawling many pages. llms.txt stays navigational; llms-full.txt carries the substance.

// ready_when_you_are

Let's build your agentic advantage

Tell us what should be automated, connected or sold. We'll map the fastest path from idea to a production system.