Free browser tool

Free llms.txt generator

Create a concise AI-readable map for your website. The output is generated in your browser and can be published at https://yourdomain.com/llms.txt. Use the generator for a first draft, then edit the file so it reflects real source pages rather than a generic site description.

How to use the file

1. Review the generated text and replace generic claims with factual details from your website.
2. Save the file as llms.txt and publish it at the root of your domain.
3. Add links only to pages that are useful, crawlable, and accurate.
4. Keep the file short enough for an AI assistant to scan quickly.

What to include by site type

• SaaS product: docs, pricing, integrations, security, changelog, support policy, and one or two product overview pages.
• Documentation site: quickstart, API reference, SDK guides, examples, limits, version policy, and migration notes.
• Local business: service pages, service areas, pricing logic, booking policy, guarantees, and contact/location pages.
• Ecommerce store: category hubs, buying guides, shipping, returns, warranty, product data, and support policy.
• Publisher or blog: evergreen explainers, author pages, corrections policy, topic hubs, and editorial standards.

What to leave out

Do not list tag archives, thin campaign pages, duplicate filters, outdated release notes, or internal search pages. A short file with ten strong source pages is usually more useful than a long file with a hundred weak URLs. If a page would not help a human answer a factual question, it probably does not belong in the file.

Example output shape

# Example Product

> Example Product helps support teams route and resolve customer requests.

## Primary Sources

- [Product overview](https://example.com/product): What the product does and who it serves.
- [Docs](https://example.com/docs): Setup, configuration, and API details.
- [Pricing](https://example.com/pricing): Plans, limits, billing rules, and add-ons.
- [Security](https://example.com/security): Data handling, compliance, and access controls.
- [Changelog](https://example.com/changelog): Product changes and release notes.

Publish and test

curl -I https://yourdomain.com/llms.txt
curl -s https://yourdomain.com/llms.txt | sed -n '1,80p'
curl -I https://yourdomain.com/robots.txt
curl -I https://yourdomain.com/sitemap.xml

The file should return 200, be readable as plain text or Markdown, and link to canonical pages that also return 200. If you use both apex and www hosts, keep /llms.txt behavior consistent.

What makes a good llms.txt?

A good file names the site, explains who it serves, lists the strongest source pages, and tells AI assistants how to use the linked material. It should not contain hidden claims, keyword stuffing, or instructions that try to manipulate answer engines.

Generator limits

This generator does not crawl your site or decide what is true. It helps you write a clean first draft. The durable SEO/GEO value comes from the pages behind the links: clear documentation, accurate policies, first-hand examples, and source pages that answer real user questions.

Related next steps: review llms.txt examples, publish at the correct path, and validate the finished file.