Free tool · No signup
llms.txt generator — for AI search visibility
Build a llmstxt.org-compliant file for your site in 60 seconds. Everything runs in your browser — no signup, no email gate, no API call. Built and maintained by GEO Tracker AI, who measure whether ChatGPT, Perplexity, and Google AI Mode actually cite your brand.
Use this tool if
- • You're on WordPress, Webflow, Framer, plain static HTML, or any site where you write content by hand.
- • Your site has ~10–30 pages worth listing — you'll write descriptions yourself.
- • You don't have an auto-generated
llms.txtpipeline yet and want a quick first version.
Skip this tool if
- • You already auto-generate
llms.txtfrom a CMS, content collection, or build step (Next.js dynamic route, Sanity / Contentful pipeline, Hugo / Astro build). - • Your docs change weekly and you have 50+ pages worth listing — manual will drift fast.
- • See the dynamic-route pattern in the guide instead.
Inputs
First time? Read this 30-second guide
What is llms.txt? A plain-text file you host at the root of your site (yourdomain.com/llms.txt) that gives AI agents a Markdown map of which pages matter. Like a sitemap, but for AI. Not a ranking signal — a courtesy that helps the AI agents that do read it cite you accurately.
- Fill the basics — brand name, homepage URL, one-sentence tagline.
- Add 5–15 key pages — the ones you want AI to know about. For a SaaS that's docs, pricing, top blog posts. For a recipe site that's category hubs and your best recipes. For an agency that's services and case studies.
- Copy or download — drop the file at
yourdomain.com/llms.txt.
Need more detail? The full setup guide covers WordPress / Webflow / Next.js setup, common mistakes, and how to verify it works.
Stuck? Click Load example above to see how a SaaS, content site, or agency would fill this out.
The name of your site or business as you want it cited in AI answers. Plain text, no marketing tagline — just the name.
The root URL of your site. We use it to turn relative paths like /docs or /about into full URLs in the output. Paste with or without https:// — we add it.
AI uses this as the canonical summary of your brand. Avoid marketing words — write like a librarian, not a press release. Concrete numbers and categories beat adjectives.
Reference content — concepts, methodology, how things work. For a content / media site this is also where category hubs go (e.g. /category/main-courses).
Examples — SaaS: /docs/getting-started, /docs/api · Recipe blog: /category/main-courses, /category/soups · Agency: /services/brand, /services/web
- Resource 1
URL or path on your site. Relative paths get prefixed with your homepage URL above.
Short title of the page. What an AI agent sees as the link text.
Concrete beats vague — "5,000+ tested recipes" beats "great content".
Pages about what you sell or offer — features, pricing, comparison pages, plans.
Examples — SaaS: /pricing, /features/x · Content site: top-performing collections or seasonal hubs · Agency: /work, case studies
- Resource 1
URL or path on your site. Relative paths get prefixed with your homepage URL above.
Short title of the page. What an AI agent sees as the link text.
Concrete beats vague — "5,000+ tested recipes" beats "great content".
Long-form content — blog posts, tutorials, guides, case studies. Pick your 5–10 most useful, not all of them.
Examples — SaaS: top blog posts · Content site: most-loved articles or recipes · Agency: a few signature case studies
- Resource 1
URL or path on your site. Relative paths get prefixed with your homepage URL above.
Short title of the page. What an AI agent sees as the link text.
Concrete beats vague — "5,000+ tested recipes" beats "great content".
Less-critical but useful pages — sitemap, About, contact, robots.
Examples — /sitemap.xml, /about, /contact, /robots.txt
- Resource 1
URL or path on your site. Relative paths get prefixed with your homepage URL above.
Short title of the page. What an AI agent sees as the link text.
Concrete beats vague — "5,000+ tested recipes" beats "great content".
Generated llms.txt
Drop in your site root as /llms.txt
Output follows the llmstxt.org spec — a single H1 brand name, an optional blockquote summary, then H2 sections of bulleted resources. No backend call; everything is generated in your browser. Your inputs auto-save to this browser's local storage so an accidental refresh won't lose your work — use Reset to clear.
The honest part — what llms.txt does and does not do
llms.txt is a useful courtesy. It is not a ranking signal in Google AI Overviews or Google AI Mode, and shipping a perfect file does not guarantee citations in ChatGPT or Perplexity. The piece that does move the needle is whether AI engines actually cite your brand for the buyer-questions your prospects ask — and that requires measurement, not a static file.
What is llms.txt?
yourdomain.com/llms.txt) that gives AI agents a Markdown map of the resources on your site. It is the AI-era equivalent of a sitemap: a one-page summary of who you are and which pages matter, designed for single-fetch ingestion. The convention was proposed in 2024 at llmstxt.org.Does Google or Bing use llms.txt for ranking?
Where do I put the file?
text/plain at yourdomain.com/llms.txt. On Next.js / Vercel you can either drop it in public/llms.txt for a fully static file, or build a dynamic version via an app/llms.txt/route.ts handler if you want contents to update automatically from your CMS or content collection.llms.txt vs llms-full.txt — which one?
How do I verify it actually works?
Disclaimer & limits
This is a free helper that produces an llmstxt.org-compliant file at the time of our most recent review (2026-05-13). A few honest notes so expectations are right from day one:
- Publishing an llms.txt does not guarantee citations in AI engines. Google has stated it is not a ranking signal for AI Mode or AI Overviews, and there is no public confirmation it influences ChatGPT, Perplexity, Copilot, or Gemini rankings. Citations depend on dozens of factors — domain authority, entity clarity, structured data, content quality, citation footprint in third-party sources — none of which a static file directly controls.
- Spec changes faster than tools. The llms.txt convention is informal and unversioned. Vendors (Anthropic, Perplexity, OpenAI, Google) occasionally tweak how they consume related files such as
llms-full.txtorrobots.txtrules for AI crawlers. We monitor these changes and update the tool when they happen, but cannot promise the tool always reflects the absolute latest practice — verify vendor docs for anything mission-critical. - Output is not validated. We don't check the URLs, titles, or descriptions you enter. Typos, broken links, or inaccurate descriptions in your output are your responsibility to catch before publishing. Run a manual fetch of
yourdomain.com/llms.txtafter deploy to confirm the file is reachable. - Provided as-is. The tool is provided free of charge without warranty, express or implied. We accept no liability for outcomes related to AI search visibility, organic ranking, or business results that follow from using or not using this file.
The reliable way to know whether AI engines actually cite your brand is controlled measurement — not a static file.
Next step
You shipped llms.txt. Does AI cite you now?
Most teams ship GEO work and never verify it. A perfect llms.txtdoes not guarantee ChatGPT cites you for "best X for Y" — the only way to know is to ask the engines on a fixed prompt panel and measure Share of Voice over time. Free 60-second audit, no card required: