Best /llms.txt generators in 2026: which one for Shopify, WordPress, or your custom site?
/llms.txt is the emerging standard for telling LLMs how to read your site. We compare the seven most-used generators — what they emit, what they miss, and which one fits your stack.
Quick comparison
| Tool | Pricing | Best for |
|---|---|---|
| ClickFrom.AI This is us | From $19/mo · 14-day free trial | Shopify stores — auto-maintained /llms.txt + /llms-full.txt |
| llms-txt for WordPress | Free | WordPress sites with active content publishing |
| astro-llms-txt | Free, open source | Astro static sites |
| next-sitemap-llms | Free, open source | Next.js sites generating from sitemap |
| llms.txt CLI | Free, open source | Build-time generation, CMS-agnostic |
| Hand-authored | Free (your time) | Sites with under 50 pages and stable content |
| Mintlify llms.txt | Bundled with Mintlify ($120/mo+) | Documentation sites already on Mintlify |
What /llms.txt actually is
/llms.txt is a markdown file at your domain root that gives LLMs a curated table of contents for your site — the URLs that matter, what they’re about, and how they relate. Think of it as robots.txt for the AI age, except more verbose and aimed at understanding rather than crawl gating.
There are usually two files:
/llms.txt— small, just URLs + titles + descriptions in markdown/llms-full.txt— the full content of those pages, concatenated, so an LLM can ingest your entire site in one fetch
The format was proposed by Answer.AI in late 2024 and adoption has been steady — ChatGPT, Claude (via web search), and Perplexity all check for these files. Google’s AI Overviews don’t yet, but they index your site through Googlebot anyway.
The roundup
1. ClickFrom.AI (Shopify, auto-maintained)
Pricing. From $19/mo. 14-day free trial.
Generates. Both /llms.txt and /llms-full.txt automatically from your Shopify catalog + blog. Re-emits on every catalog or content change — never goes stale.
Wins on. Zero maintenance. Two-click install from the Shopify App Store. Includes the rest of the AI Visibility stack (schema, citation monitoring, content suggestions) — /llms.txt is one feature among several.
Loses on. Shopify-only. If you’re not on Shopify, this isn’t the right tool.
Pick if: You sell on Shopify and want /llms.txt without thinking about it ever again.
2. llms-txt for WordPress (the official-ish plugin)
Pricing. Free.
Generates. Both /llms.txt and /llms-full.txt from your WordPress posts, pages, and custom post types. Configurable inclusion rules (which content types to include, which to exclude).
Wins on. Free. Native WordPress integration. Sensible defaults that work for most sites without configuration.
Loses on. No real dashboard — a plain settings page. Doesn’t extend into broader AI-Visibility features the way ClickFrom.AI does on Shopify.
Pick if: You’re on WordPress and want a free, set-and-forget /llms.txt source.
3. astro-llms-txt (Astro static sites)
Pricing. Free, open source (MIT).
Generates. Both files from your Astro content collections. Hooks into Astro’s build pipeline, regenerates on every astro build.
Wins on. Tight Astro integration. Emits clean output that matches Astro’s content model. Active maintenance.
Loses on. Astro-only (won’t help if you’re on Next.js, Gatsby, etc.). Manual configuration for non-trivial inclusion rules.
Pick if: You build with Astro (this very site uses it) and want first-class /llms.txt support.
4. next-sitemap-llms (Next.js)
Pricing. Free, open source.
Generates. /llms.txt derived from the sitemap that next-sitemap already produces. Reuses the existing sitemap entries with optional title/description enhancement.
Wins on. Free. Reuses existing next-sitemap configuration. Minimal new setup.
Loses on. /llms-full.txt support is patchier; you may need a custom postbuild script. Less mature than the WordPress plugin or Astro generator.
Pick if: You’re on Next.js and already using next-sitemap.
5. llms.txt CLI (CMS-agnostic build-time generator)
Pricing. Free, open source (Answer.AI’s reference implementation).
Generates. Both files from a config file you author + a content directory. CMS-agnostic — works with any source you can point at.
Wins on. Maximum flexibility. The reference implementation, so output matches the spec exactly. Good for static sites or build pipelines that don’t fit a framework-specific generator.
Loses on. Requires you to manage the config file. Not ideal if your site is dynamic or your content updates frequently outside the build cycle.
Pick if: You want maximum control and your stack doesn’t have a framework-specific generator.
6. Hand-authored (the simplest option)
Pricing. Free (your time).
Generates. What you write. Just a markdown file you create at public/llms.txt.
Wins on. Zero dependencies. Total control over the contents. Sensible for a 10–20-page site that updates monthly.
Loses on. Goes stale every time you publish. Above 50 pages it’s impractical to maintain.
Pick if: Your site is small (under 50 pages), updates infrequently, and you want maximum control with minimum tooling.
7. Mintlify (bundled if you already use Mintlify for docs)
Pricing. Free if you’re on Mintlify ($120/mo+ for the docs platform itself).
Generates. Both files from your Mintlify documentation pages.
Wins on. If you’re already paying for Mintlify for docs hosting, /llms.txt is bundled — no extra step. Output is well-structured for documentation sites.
Loses on. Only generates from your Mintlify-hosted docs, not your full site. Mintlify’s pricing is high if /llms.txt is your only need.
Pick if: You’re already on Mintlify for documentation hosting.
Quick comparison
| Generator | Stack | Pricing | Auto-update | /llms-full.txt |
|---|---|---|---|---|
| ClickFrom.AI | Shopify | $19/mo | On every catalog change | Yes |
| llms-txt for WordPress | WordPress | Free | On every post publish | Yes |
| astro-llms-txt | Astro | Free | On every build | Yes |
| next-sitemap-llms | Next.js | Free | On every build | Partial |
| llms.txt CLI | Any | Free | Build-time | Yes |
| Hand-authored | Any | Your time | Manual | If you write it |
| Mintlify | Mintlify docs | Bundled | Auto | Yes |
Recommendation by stack
- Shopify: ClickFrom.AI — auto-maintained, no config, plus the rest of the AI Visibility stack
- WordPress: llms-txt for WordPress (free, official-ish)
- Astro: astro-llms-txt (free, native build integration) — or follow our llms.txt approach if you want a Shopify-style implementation pattern
- Next.js: next-sitemap-llms (if you already use next-sitemap), or the llms.txt CLI as a postbuild step
- Hugo / Eleventy / Jekyll: llms.txt CLI as a build step, or hand-author for under-50-page sites
- Custom backend: llms.txt CLI as a periodic cron job, or roll your own — the spec is short
- Documentation site on Mintlify: Mintlify’s bundled support
- Anything under 50 pages: Hand-author it. The whole spec is short enough to write in 30 minutes.
The mistake to avoid: a stale /llms.txt that points LLMs at deleted or outdated pages. If you can’t auto-regenerate, pick the hand-authored route and put a calendar reminder on the file.
Frequently asked questions
What is /llms.txt and why does it matter?
/llms.txt is a markdown file at your domain root (analogous to robots.txt) that tells LLMs how to read your site — what's important, how it's structured, and where to find canonical content. The /llms-full.txt variant includes the full content of those important pages so an LLM can ingest your site without crawling. Both are emerging standards proposed by jeremyhowzz at Answer.AI. ChatGPT, Claude, and Perplexity all reference these files when crawling.
Is /llms.txt actually being read by AI engines?
ChatGPT, Claude (via search), Perplexity, and several smaller LLMs check for /llms.txt as part of their crawl. Google's AI Overviews don't use it (they use Googlebot's index). Adoption is uneven and growing — the safe bet is to ship it; the cost is near-zero if generated automatically.
Do I really need /llms-full.txt or just /llms.txt?
/llms.txt is the link-list table-of-contents (small file, just URLs + titles + descriptions). /llms-full.txt is the full content of all those pages concatenated — a much bigger file but lets LLMs ingest your entire site in one fetch. Most generators produce both; for a Shopify store with 1,000 products /llms-full.txt can be 10–50MB, which is fine — LLMs are designed to handle that scale.
Can I just hand-author it?
Yes for under-50-page sites. Above that, hand-authoring is impractical because the file goes stale every time you publish. Use a generator that re-emits on every build (or, on Shopify, on every catalog change).
Does a /llms.txt file leak my full site to AI training?
It doesn't grant any access you weren't already granting. AI crawlers that ignore robots.txt would crawl you anyway; AI crawlers that respect robots.txt only fetch what you allow. /llms.txt is a courtesy to the well-behaved crawlers, not a security boundary. If you don't want to be in AI training data, your robots.txt + a noindex strategy is the right control, not /llms.txt.
How often should /llms.txt regenerate?
On every build for static sites. On every catalog or content change for dynamic sites (Shopify, WordPress). The file should reflect your live content — a stale /llms.txt is worse than none, because LLMs may cite outdated pages.
See ClickFrom.AI on your store
14-day free trial. Two-click install from the Shopify App Store. No theme edits required.
Install free from Shopify