Log inGet Started

Free tools

Free llms.txt Generator

Paste your URL to generate a curated llms.txt — then edit, copy, or download and upload it to your site root on GetCited.me.

  • 100% Free
  • Instant
  • No sign-up
Live analysis
# Your Site Name

> A short summary of what your site is about, who it serves, and the main outcome visitors get from your product or content.

## Main
- [Home](https://example.com): What visitors find on the homepage and how to get started.
- [Pricing](https://example.com/pricing): Plans, limits, and what each tier includes.
- [Features](https://example.com/features): Core capabilities and how they map to common jobs-to-be-done.
- [Customers](https://example.com/customers): Proof points, logos, and short outcome stories.

## Documentation
- [Getting Started](https://example.com/docs): First-time setup, onboarding checklist, and required integrations.
- [API Reference](https://example.com/docs/api): Endpoints, auth, rate limits, and example requests.
- [Guides](https://example.com/docs/guides): Task-based walkthroughs for admins, developers, and end users.
- [Changelog](https://example.com/changelog): Release notes and breaking changes by version.

## Resources
- [Blog](https://example.com/blog): Product updates, how-tos, and industry explainers.
- [Case studies](https://example.com/case-studies): Deeper dives on customer workflows and measured results.
- [Webinars](https://example.com/webinars): Live and recorded sessions with Q&A.
- [Help center](https://example.com/help): Searchable articles for billing, security, and troubleshooting.

## Company
- [About](https://example.com/about): Mission, team, and how the product is built.
- [Careers](https://example.com/careers): Open roles and how we work.
- [Contact](https://example.com/contact): Sales, support, and partnership inquiries.

## Optional
- [Terms of Service](https://example.com/terms)
- [Privacy Policy](https://example.com/privacy)
- [Cookie settings](https://example.com/cookies)

How to generate your llms.txt in 3 steps

  1. Enter your URL

    Paste your site and select Generate. We scan your pages and draft titles and descriptions automatically.

  2. Review and edit the auto-generated file

    Rename sections, tighten descriptions, reorder or remove pages, and push low-priority links to Optional.

  3. Download it and upload to your root

    Copy or download the file, then upload it to the root of your domain so it lives at example.com/llms.txt.

The file

What actually goes in an llms.txt

Four parts, one of them required. The whole spec fits on a napkin — which is the point.

  1. A curated map, not a full index

    A sitemap lists everything you have. An llms.txt lists what you would point someone at if they asked what you do. The difference is editorial, and it is the entire value of the file.

  2. The H1 title (required)

    The file opens with a single `# Your Site Name`. It is the one element the spec requires, and it names the site everything below it describes.

  3. The summary blockquote

    A `>` line directly under the title, saying in plain language what the site is and who it is for. One or two sentences — this is the part a model is most likely to repeat back.

  4. Link sections, and Optional last

    Group links under `##` headings that match how your content is actually organised, each with a short description of what the page covers. An `## Optional` section, always last, holds the terms-and-privacy tier.

How it compares

llms.txt vs robots.txt vs sitemap.xml

Three files, same directory, three different jobs. Confusing them is why sites publish all three and still go unquoted.

  1. llms.txt

    Says which of your pages are worth reading and what each one covers. Written for models that need to pick a source. Its job is accurate citation.

  2. robots.txt

    Says which paths a crawler may fetch at all. Written for anything that crawls. Its job is access — it can only subtract, never recommend.

  3. sitemap.xml

    Says which URLs exist and when they changed. Written for search crawlers. Its job is discovery on sites too large or too deep to crawl by links alone.

Setup

How to install llms.txt by platform

One requirement everywhere: the file has to resolve at the root, so example.com/llms.txt returns plain text and not your 404 page.

  1. WordPress

    Upload llms.txt to your site root via FTP or a file manager plugin, or use a plugin that serves files from the root.

  2. Shopify

    Shopify restricts root files — host llms.txt on a subpath or use an app/redirect; many stores serve it from a linked page or app proxy.

  3. Webflow

    Add the file content under Project Settings, or host it externally and point a redirect at /llms.txt.

  4. Next.js / React

    Drop llms.txt into your public/ folder (or add an app route) so it is served at /llms.txt on deploy.

  5. cPanel / shared hosting

    Upload llms.txt into the public_html (web root) directory using the File Manager or FTP.

  6. Netlify / Vercel

    Place llms.txt in your publish/public directory so it ships at the root with your build.

Do & avoid

Six rules for a file worth publishing.

An llms.txt that lists everything is a sitemap with extra steps. These keep it useful.

  1. Describe each page specifically

    “Pricing: three plans, per-seat, with limits listed” tells a model something. “Learn more” tells it that you did not bother, and it will use the page it can actually understand instead.

  2. Pasting in every URL you have

    A wall of links buries the ten pages you cared about. If everything is in the file, nothing in it is a recommendation.

  3. Lead with the pages that answer questions

    Product, pricing, docs and comparison pages first. Order carries meaning here — a model reading top-down treats early entries as the ones you consider central.

  4. Letting it drift from the site

    A file pointing at renamed or retired URLs is worse than none: you have now personally vouched for pages that 404.

  5. Name sections the way your site is organised

    The `##` headings are structure a model can use to reason about your site. Invented categories that match nothing on the site just add noise.

  6. Blocking the agents you just invited

    An llms.txt is pointless if robots.txt refuses the crawlers it was written for — and the two files are almost never edited by the same person.

Check robots.txt for AI agents

Honest take

Does llms.txt actually matter?

No major AI provider has confirmed it reads llms.txt at scale. Anyone selling it as a ranking lever is selling something — it is a cheap signal with a real side effect, and worth exactly that.

  1. The curation is the payoff

    Writing one forces you to state, in a sentence each, what your best pages are for. Most sites discover in the process that they cannot — and that problem was costing them long before this file existed.

  2. Citations still come from the pages

    No root file rescues a page that does not answer anything. The file points; the content has to be worth pointing at.

Check AI agent readiness

Want the full visibility stack?

Tools are just the start — track visibility over time in GetCited.me.

Start free scan

llms.txt FAQ

No. llms.txt is a community proposal, not an official standard ratified by a body like the W3C, and major AI providers have not formally committed to reading it. Adding one is low-risk and low-cost, but treat it as a helpful signal rather than a guaranteed ranking factor.
Traditional search engines like Google rely on robots.txt and sitemap.xml, not llms.txt, for crawling and indexing. llms.txt is aimed at AI models and AI search experiences. It sits alongside your sitemap and robots.txt — it does not replace them.
Refresh it whenever your important pages change — for example when you launch, rename, or retire key content. For most sites a quick review every few months is enough. Avoid pointing at dead or outdated URLs.
The primary file should live at your domain root (example.com/llms.txt). You generally want one canonical file per site so models have a single source of truth. Large sites sometimes add supplementary files, but the root file matters most.
llms.txt is a concise index: titles, descriptions, and links to your key pages. llms-full.txt is a heavier variant that includes full page content in markdown. This generator produces the standard llms.txt.

More free tools

llms.txt Validator

Technical SEOForever free

Validate an existing llms.txt from URL or paste — structure, headings, links, and issues. Forever free on GetCited.me.

Open tool
ai.txt Generator

Technical SEOForever free

Generate a practical /ai.txt policy template for AI agents — identity, citation preference, and crawl signals. Forever free on GetCited.me.

Open tool
Robots.txt Checker

Technical SEOForever free

Fetch and review robots.txt for crawl control, sitemaps, and risky blocks — full result, no sign-up.

Open tool

Related glossary

Part of GetCited.me

Explore feature