Add your highest-value pages by hand, or import a starting list straight from your sitemap.xml. Review the output, fix what the checklist flags, then copy or download a clean, spec-compliant llms.txt file.
Paste a single sitemap.xml URL to pull in its page list, then edit titles and descriptions yourself. Review before publishing; this only reads public XML.
# Untitled Site
Resolve the errors above before publishing; warnings are judgment calls.
llms.txt at your site's root (e.g. /llms.txt). If your robots.txt blocks AI crawlers, they can't reach this file either; allow the crawlers you want citing you.Llms.txt is a proposed Markdown convention for giving agents a concise route into useful website information. It can summarize your site and organize links.
Treat it as a maintained reading guide. It does not replace accessible pages, internal navigation, or a clear explanation of your products and expertise.
Publishing the file does not guarantee rankings or citations. Google states that special AI text files are unnecessary for its Search AI features.
Enter your site name and a short summary. Explain who the site serves and what visitors can learn, using plain language.
Add sections for distinct needs, such as getting started, tutorials, product documentation, and policies. Place your most useful resources first.
You can import candidate links from a sitemap, then curate them. Imported titles and URLs are starting points, not finished editorial descriptions.
Include pages that explain your core topic, resolve common problems, or provide original reference material. Remove duplicate and outdated destinations.
A focused selection is easier to maintain than a full website dump. There is no universal required link count, so choose by usefulness.
Use descriptive link names. Where available, link to accurate Markdown versions that represent the same information as their public pages.
Replace generic notes such as useful guide with a specific description. Tell readers what task the destination helps them complete.
For example, describe a title guide as a walkthrough of title length, search intent, and editing examples. Avoid unsupported best-tool claims.
Missing-description notices are editing prompts. Add meaningful summaries before publishing rather than repeating the page title in every description field.
The proposal starts with a site or project heading. A short summary, background notes, and grouped Markdown links can follow.
Publish at /llms.txt for a site overview. The current proposal also supports scoped files, such as /docs/llms.txt, covering their own path.
Robots.txt expresses crawler rules. A sitemap lists discoverable URLs. Llms.txt supplies a curated overview, so keep these files consistent without treating them as interchangeable.
Copy or download the output, then open the published address in a browser. Check that the response contains the intended Markdown.
Test each destination and remove broken links. Review the overview after changing product names, moving guides, or retiring old material.
Keep the summary factual and concise. Improve the underlying pages first when information is missing, unclear, or unsupported by evidence.
Common questions
Use the supplied controls to prepare your file, review its contents, and download it when ready.
Save it as llms.txt at your site's root, for example https://yoursite.com/llms.txt, the same way robots.txt and sitemap.xml live at the root.
No. llms.txt is a proposed convention, not a confirmed ranking or citation signal for any AI search engine. Treat it as a cheap, reviewable addition alongside real content quality, not a substitute for it.
To keep the fetch fast, safe, and predictable, the importer reads a single urlset sitemap. If you paste a sitemap index (a list of other sitemaps), it will ask you to paste one of the child sitemap URLs instead.
No. Keep llms.txt to your highest-value, most representative pages. A long, unfiltered list is harder for a model to use well than a short, curated one.