llms.txt generator
Create a concise Markdown source map from your core pages.
Open generatorAI search visibility toolkit
Make your website easier for AI answers to cite.
Create a clean /llms.txt, align crawler access, and publish source pages that search engines and AI answer engines can understand without guessing.
Static firstFast pages that crawlers can read.
No dark patternsBuilt around search engine guidelines.
GEO readyClear sources for AI-generated results.
Free tool
llms.txt generator
Generated locally in your browser.
Toolbox
Free tools for source maps and crawler policy.
Generate, validate, convert, and audit the files that help crawlers and AI assistants understand your strongest source pages.
Sitemap to llms.txt
Paste sitemap XML or URLs and draft a source map to refine.
Open converterllms.txt validator
Check headings, summary, source links, and concise structure.
Open validatorAI robots.txt builder
Draft crawler rules for search, user retrieval, and training bots.
Open builderAI robots.txt checker
Review whether your policy supports AI search visibility.
Open checkerGEO checklist
Check whether your pages are crawlable, factual, and citeable.
Open checklistWhat to build first
GEO is still grounded in crawlable, useful pages.
Google's public guidance for AI search emphasizes unique, valuable content, crawlability, page experience, and structured data that matches visible content. Bing's webmaster guidance says the same SEO foundation supports AI grounding and Copilot visibility.
Publish source pages
Answer exact questions with first-hand, specific information. AI systems need sources they can quote, not vague category pages.
Learn the source-page patternAdd an AI map
A concise llms.txt file can point assistants to your strongest docs, pricing, policies, and factual reference pages.
Generate the fileAlign robots policy
Decide which bots can crawl your site and keep that policy consistent with your search and AI visibility goals.
Build robots.txtExamples and decisions
See what belongs in the file, and what does not.
Use examples and comparisons to avoid treating llms.txt like a replacement for sitemap.xml, robots.txt, or useful source pages.
llms.txt examples
Compare concise examples for SaaS, ecommerce, publisher, documentation, and local sites.
Open examplesllms.txt vs sitemap.xml
Learn why sitemap.xml is for URL discovery while llms.txt is a curated source map.
Read comparisonllms.txt vs robots.txt
Separate crawler permissions from AI-readable guidance for your strongest pages.
Read comparisonPlatform recipes
Build an llms.txt file for the stack you already use.
Each recipe focuses on what source pages to include and how to keep the file useful for AI assistants without promising unsupported platform magic.
Blogs and content sites
Map cornerstone pages, category hubs, editorial policy, authors, and evergreen explainers.
Open WordPress recipeStores and catalogs
Highlight buying guides, collections, shipping, returns, warranty, and customer support pages.
Open Shopify recipeModern web apps
Keep static source pages discoverable and align canonical URLs with generated files.
Open Next.js recipeDeveloper docs
Expose quickstarts, API references, SDK guides, versioned docs, and changelogs.
Open Docusaurus recipeProject docs
Point assistants to README, docs, examples, releases, license, and contribution pages.
Open GitHub Pages recipeMarketing sites
Connect product pages, comparisons, case studies, pricing, and trust pages.
Open Webflow recipeBot guides
Separate search visibility from model training.
Several AI companies now document different crawlers for search, user-triggered retrieval, and training. Treat them separately when you write robots.txt rules.
OAI-SearchBot vs GPTBot
Allow search discovery while deciding separately whether training crawls fit your policy.
Read OpenAI bot guideClaudeBot and Claude-SearchBot
Map Anthropic's three documented agents to search, user retrieval, and training choices.
Read Claude guidePerplexityBot policy
Understand what Perplexity says it indexes when pages are allowed or disallowed.
Read Perplexity guideLong-tail library
Templates for common site types.
Start with a template, then rewrite it with real details from your website. Thin generic files do not create durable search value.
Product and docs sites
Prioritize docs, pricing, integrations, security, changelog, and support policy pages.
Open SaaS templateProduct catalogs
Highlight category hubs, buying guides, shipping policy, returns, warranty, and product data feeds.
Open ecommerce templateBlogs and media
Expose evergreen explainers, editorial policy, author pages, corrections, and topic archives.
Open publisher templateDeveloper documentation
Point AI assistants to quickstarts, API reference, examples, SDKs, and changelogs.
Open docs templateLocal business sites
Clarify service areas, booking, pricing, policies, location pages, and trust signals.
Open local template