Log in Get started free

LLMs TXT Generator (Free)

This free llms txt generator creates a clean llms.txt file you can publish at /llms.txt to point AI systems to your most authoritative pages. No signup. Copy or download instantly.

Generate llms.txt How to install

What is llms.txt?

llms.txt is a simple text file you host on your domain (usually at /llms.txt). It points AI systems to the pages you consider most authoritative, so they can find the right context faster.

It's not a magic ranking lever, and it doesn't replace robots.txt. Think of it as a curated "start here" map for AI consumption, not an access control file.

What it does

  • Highlights your best pages (docs, pricing, security, support, key guides).
  • Reduces ambiguity by steering AI systems to canonical sources.
  • Improves "extractability" when the linked pages are clear and structured.

What it doesn't do

  • It does not force any AI system to use it.
  • It does not guarantee citations or mentions.
  • It does not block or allow crawlers (robots.txt does that).

Generate your llms.txt

Basic Info

Trust & support URLs (optional)

Add URLs that establish credibility. AI systems use these for context, not as citation targets.

Key pages to prioritize (recommended)

Pages you want AI systems to cite. Pick from presets or add your own.

Pro tip
Start with 10–20 URLs. Keep it curated. If you add 50+ links, the signal gets diluted and it starts looking like a sitemap. For large documentation sites, keep llms.txt tight and use an optional llms-full.txt for a deeper index.

Options

Checklist

○Valid website URL
ℹ0 priority pages added (recommended: 3–8)
ℹRecommended total: 10–20 URLs

llms.txt Preview

// Enter your website URL to generate llms.txt

How to use this llms txt generator

  1. Add your website and key URLs (docs, pricing, support, security).
  2. Copy or download your llms.txt file.
  3. Publish it at https://yourdomain.com/llms.txt and keep it updated when your site changes.

How to add llms.txt to your website

Netlify serves static files from the public/ folder automatically.

Steps

  1. Save your llms.txt file to public/llms.txt in your repo.
  2. Commit and push. Netlify will deploy it automatically.
  3. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Placing the file in src/ instead of public/.
  • Forgetting to commit and push the file.
  • Using a subdirectory like public/files/llms.txt instead of root.

Webflow doesn't have a file system, so you'll need to use a custom code embed or hosting workaround.

Steps

  1. Go to Project Settings → Custom Code → Head Code.
  2. Add a redirect rule or use Webflow's asset hosting (upload as a downloadable file).
  3. Alternatively, use Cloudflare Workers or a subdomain to serve the file.
  4. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Expecting Webflow to serve plain text files at custom paths natively.
  • Using the CMS instead of static file hosting.
  • Not testing the final URL after publishing.

WordPress can serve static files from the root if you have FTP/SFTP access or use a plugin.

Steps

  1. Connect to your server via FTP/SFTP.
  2. Upload llms.txt to the root directory (same level as wp-config.php).
  3. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Uploading to wp-content/ instead of the site root.
  • Caching plugins blocking the new file from appearing.
  • Permissions issues preventing the file from being served.

Next.js serves static files from the public/ directory at the root URL.

Steps

  1. Save your llms.txt file to public/llms.txt.
  2. Deploy your app (Vercel, Netlify, or self-hosted).
  3. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Placing the file in src/ or app/ instead of public/.
  • Using pages/llms.txt.js (creates a route, not a static file).
  • Forgetting that public/ files are served without the /public prefix.

Astro serves static assets from the public/ directory at the root URL.

Steps

  1. Save your llms.txt file to public/llms.txt.
  2. Build and deploy your site.
  3. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Placing the file in src/ instead of public/.
  • Using src/pages/llms.txt.astro (generates HTML, not plain text).
  • Forgetting to rebuild after adding the file.

Cloudflare Pages serves files from your build output or public/ directory.

Steps

  1. Add llms.txt to your public/ folder (or build output root).
  2. Commit and push. Cloudflare Pages will deploy automatically.
  3. Verify at https://yourdomain.com/llms.txt.

Common mistakes

  • Placing the file outside the build output directory.
  • Using a framework that doesn't copy public/ to the build output.
  • Caching issues delaying the file from appearing.

GitHub Pages serves files from your repo root or docs/ folder.

Steps

  1. Add llms.txt to the root of your GitHub Pages source (usually / or /docs).
  2. Commit and push. GitHub Pages will deploy automatically.
  3. Verify at https://yourusername.github.io/llms.txt.

Common mistakes

  • Using a Jekyll site without adding llms.txt to the include list in _config.yml.
  • Placing the file in a subdirectory.
  • Branch mismatch between source and GitHub Pages settings.

llms.txt examples (templates)

SaaS Product

Typical B2B SaaS with docs, pricing, and security pages.

# llms.txt
# Site: Acme Inc (https://acme.com)

## Key URLs
- Homepage: https://acme.com
- Documentation: https://docs.acme.com
- Pricing: https://acme.com/pricing
- Security / Trust: https://acme.com/security
- Support / Help: https://help.acme.com
- API Reference: https://api.acme.com/docs

## Notes
- Use canonical URLs.
- This file is advisory.

Documentation Site

Developer docs with getting started guides and API reference.

# llms.txt
# Site: DevTools Docs (https://docs.devtools.io)

## Key URLs
- Homepage: https://docs.devtools.io
- Getting Started: https://docs.devtools.io/quickstart
- API Reference: https://docs.devtools.io/api
- Configuration: https://docs.devtools.io/config
- Troubleshooting: https://docs.devtools.io/troubleshooting
- Changelog: https://docs.devtools.io/changelog

## Notes
- Prefer stable URLs.
- Update when docs structure changes.

Publisher / Blog

Content site with editorial guidelines and topic hubs.

# llms.txt
# Site: Tech Insights (https://techinsights.com)

## Key URLs
- Homepage: https://techinsights.com
- About / Editorial: https://techinsights.com/about
- AI Topic Hub: https://techinsights.com/topics/ai
- Cloud Topic Hub: https://techinsights.com/topics/cloud
- Contact: https://techinsights.com/contact

## Notes
- Point to evergreen hubs, not individual articles.
- Update when adding new topic areas.

Use these as starting points. Customize the URLs and labels for your site, then publish at /llms.txt.

FAQ: llms.txt and AI visibility

What is llms.txt?

llms.txt is a simple text file you host at the root of your domain (e.g., yourdomain.com/llms.txt). It lists URLs you consider most authoritative, helping AI systems find the right context faster. It's not a ranking signal or access control file—it's a curated map for AI consumption.

Does llms.txt improve my AI search rankings?

Not directly. llms.txt doesn't guarantee rankings, citations, or mentions. It helps AI systems understand which pages you consider canonical and authoritative. Whether they use it depends on the AI system. Think of it as reducing ambiguity, not boosting rankings.

Is llms.txt the same as robots.txt?

No. robots.txt controls crawler access (allow/disallow). llms.txt is advisory—it suggests which pages to prioritize for context, but doesn't block or allow anything. You need both: robots.txt for access control, llms.txt for content prioritization.

Do AI systems actually use llms.txt?

Some do, some don't. As of early 2025, llms.txt is an emerging convention, not a universal standard. Early adopters like ChatGPT plugins and some RAG systems may check for it. The file is lightweight, so there's little downside to adding it.

Where should I host my llms.txt file?

Host it at the root of your domain: https://yourdomain.com/llms.txt. Don't put it in a subdirectory like /files/llms.txt or /public/llms.txt (the URL path, not folder structure). The file should be accessible directly at /llms.txt.

What URLs should I include in llms.txt?

Include your most authoritative pages: homepage, documentation, pricing, security/trust, support, API reference, and contact. Focus on evergreen pages that define your product or service. Avoid ephemeral content like blog posts or campaign landing pages.

How many URLs should llms.txt contain?

Start with 10–20 URLs and keep it curated. If you add 50+ links, the signal gets diluted and it becomes a sitemap. For documentation-heavy sites, keep llms.txt short and use llms-full.txt for a deeper index.

What is llms-full.txt?

llms-full.txt is an optional extended version for documentation-heavy sites. While llms.txt points to top-level entry points, llms-full.txt can include deeper pages like specific guides, API endpoints, or reference docs. It's useful for developer documentation sites.

Should I include descriptions for each URL?

Optional but helpful. Brief descriptions (5–15 words) help AI systems understand each page's purpose without fetching it. Example: '- Pricing: https://example.com/pricing - Plans, packaging, and pricing details.' Keep them factual, not promotional.

How often should I update llms.txt?

Update it when your site structure changes significantly: new key pages, removed pages, or URL changes. For most sites, reviewing it quarterly is sufficient. Don't update it for every blog post—it's for stable, authoritative pages.

Will llms.txt help me get cited by ChatGPT or Perplexity?

It might help, but there's no guarantee. AI systems decide citations based on many factors: content quality, source authority, freshness, and relevance to the query. llms.txt can help them find your best pages faster, but citation decisions remain opaque.

Can llms.txt hurt my site?

Unlikely. It's a passive, advisory file. The worst case is AI systems ignore it. There's no mechanism for llms.txt to negatively affect rankings or visibility. It's low-risk, potentially helpful.

Do I need llms.txt if I already have good SEO?

SEO and AI visibility overlap but aren't identical. Good SEO helps crawlers find and index your pages. llms.txt helps AI systems prioritize which pages to use for context. Both are useful, and llms.txt takes minutes to set up.

Should I include my sitemap URL in llms.txt?

You can, but it's not the primary purpose. llms.txt is for curated, high-value pages—not a complete index. If you want AI systems to discover all pages, your sitemap.xml handles that. llms.txt says 'start here' rather than 'here's everything.'

Is there a standard format for llms.txt?

There's an emerging convention but no formal standard yet. Common elements include: header comments with site name, a Purpose section, a Key URLs section with labeled links, and optional Notes. Keep it readable and scannable.

Can I use llms.txt for multiple domains or subdomains?

Each domain or subdomain should have its own llms.txt at its root. If you have docs.example.com and www.example.com, each needs its own file. You can reference the other domain's llms.txt in your notes if helpful.

More free AI search tools

Explore more free tools and guides to improve your AI search visibility: