Standard Brand Definition
A single clear sentence defining what the company is, who it serves, and what primary problem it solves. Skip hyperbolic marketing claims.
Create a clean, human-reviewed llms.txt draft from your public homepage metadata. The file acts as a machine-readable discovery index for generative AI engines.
An llms.txt file is designed for automated parsers that need quick, reliable context about your brand without crawling thousands of promotional pages.
A single clear sentence defining what the company is, who it serves, and what primary problem it solves. Skip hyperbolic marketing claims.
Links to the home, documentation, pricing, comparison, and technical FAQ pages so language models prioritize canonical URLs.
Explicit statements of what your product does not do, avoiding AI hallucination and incorrect feature attribution in customer answers.
Keep your root file below 5 KB (~1,500 tokens). Massive documentation dumps should go into an optional /llms-full.txt to avoid exceeding agent context limits.
Test your robots.txt against GPTBot, PerplexityBot, and ClaudeBot.
Inspect JSON-LD structured data and entity declarations.
Detailed editorial standard for drafting your brand's facts manifest.
How GEO sampling, audit scoring, and verification loop work together.
An llms.txt file is a markdown-formatted plain text file deployed at your site root or /.well-known/llms.txt that provides AI crawlers with concise entity definitions, key facts, and curated links to essential documentation.
No. The file is a discovery aid that reduces extraction ambiguity, not a ranking guarantee. Answer engines evaluate full page content, third-party corroboration, and user context.
Host it at https://yourdomain.com/llms.txt or https://yourdomain.com/.well-known/llms.txt with content-type text/plain; charset=utf-8, and reference it in your robots.txt or HTML link headers.
Keep your root /llms.txt under 5 KB (roughly 1,000–1,500 tokens). Automated retrieval agents use this file as a concise index to discover relevant canonical paths. If you have extensive documentation, publish an optional /llms-full.txt, but ensure individual sections do not overflow the typical retrieval chunk window (typically 2,000–4,000 tokens).