GEO

How to Set Up llms.txt for AI Discovery

Learn how to set up llms.txt for AI discovery and make your B2B SaaS site machine-readable to AI crawlers like GPTBot and PerplexityBot.

llms-txtai-discoveryai-crawlersmachine-readablegeo-implementation

llms.txt is a plain-text markdown file placed at your site root that gives AI crawlers and language models a structured map of your key content before they crawl individual pages. It acts as an AI-native navigation layer — telling ChatGPT, Perplexity, and other models which pages matter most, what your site is about, and how your content is organized. Setting it up is a foundational GEO implementation step that most B2B SaaS companies have not taken yet.

What Information Does an llms.txt File Provide to AI Crawlers?

An llms.txt file provides AI crawlers with exactly the information they need to build an accurate internal representation of your site. The file should open with a one-line site description: what your SaaS does and who it serves. It then lists key pages organized by logical section — product, documentation, blog, case studies, resources, pricing — with each entry containing the page title and URL.

The structure works because it front-loads what AI models need before they spend crawl budget on individual pages. When ChatGPT's web browsing mode encounters a site with a well-structured llms.txt, the model already knows the architecture before it starts reading pages. This context improves the accuracy of citations because the model understands where specific information lives within your site hierarchy.

Jeremy Howard's original proposal for llms.txt outlined the specification in late 2024, and the standard has been adopted by major AI platforms. The specification recommends using markdown format for readability, listing key pages with descriptive labels, and keeping the file under 50KB so AI crawlers can process it efficiently.

How Does llms.txt Differ from Robots.txt for AI Crawlers?

Robots.txt controls access — it tells crawlers which pages they can and cannot crawl. llms.txt provides context — it tells AI models which pages matter most and how they relate to each other. Both files work together in a GEO implementation stack, but they serve fundamentally different purposes.

Google's crawler documentation explains that while robots.txt manages crawl permissions, AI crawlers like Google-Extended also benefit from structured content maps that help them prioritize which pages to process. A site with robots.txt allowing AI crawlers but no llms.txt is accessible but unstructured. A site with both is accessible and organized from the AI's perspective.

You should include both files. Configure robots.txt to allow GPTBot, PerplexityBot, Google-Extended, and ClaudeBot. Then build llms.txt to give those allowed crawlers a prioritized map of your content. The combination ensures your content is both accessible and efficiently discoverable.

How Do I Structure an llms.txt File for Maximum AI Crawler Value?

Start with your H1-level description: one sentence explaining what your SaaS does and for whom. Follow with a section for each major content area. For each section, list the 3-8 most important pages with their relative paths. Add a notes section at the bottom for any information AI models should know that is not captured in page lists — your target ICP, your primary competitors, your content update frequency.

The formatting should be clean markdown. Use # for the site title and ## for section headings. Use bullet points for individual page entries with the format [Page Title](path): a brief description. AI models process markdown natively, so this format provides maximum extractability with minimal overhead.

Keep the file under 50KB. If your site has hundreds of pages, list only the most authoritative ones — About, product, pricing, top 10-15 blog posts, top 5-10 case studies. AI crawlers will still crawl your full site through normal page-to-page navigation. The llms.txt serves as a quality-weighted index, not a full sitemap replacement.

How Conbersa Solves This

Conbersa's GEO service configures the full crawler-accessibility stack for B2B SaaS companies. llms.txt files are built with optimized content maps that prioritize the pages most likely to earn AI citations. robots.txt directives are configured to allow GPTBot, PerplexityBot, Google-Extended, and ClaudeBot while managing crawl budget efficiently.

Content architecture and crawler configuration work together. When Conbersa publishes GEO-optimized content for your SaaS, the llms.txt file provides AI crawlers with a pre-structured map of that content, improving the speed and accuracy with which AI models build their internal representation of your brand. The result is faster citation capture and more accurate citation quality across ChatGPT, Perplexity, and Google AI Overviews.

Neil Ruaro
Founder, Conbersa

We run agentic distribution on a fleet of real phones — and write up what we learn helping founders escape the cold start. Got a topic you want covered? Tell us.

FAQ

Frequently asked questions

llms.txt is a markdown file placed at the root of a website that provides AI crawlers and language models with a structured overview of site content. Think of it as robots.txt for AI agents. It lists key pages, content sections, and notes about what the site contains, helping AI models understand your content architecture before crawling individual pages.
Place llms.txt at your site's root directory so it is accessible at yourdomain.com/llms.txt. This is the standard location AI crawlers check first. The file should be served as plain text with UTF-8 encoding. Most static site generators and content management systems support serving root-level text files directly.
A good llms.txt includes a brief site description, a list of key pages organized by section, important navigation links, and optional notes for AI agents. Include your About page, product documentation, pricing page, blog index, case studies, and any content series AI models should prioritize when building their representation of your site.
The Conbersa Blog

New guides, straight to your inbox.

Tactics on organic distribution and the cold-start problem. What's actually working, no fluff.