Create an llms.txt draft from the site description and resource links you choose. Screpy's llms.txt Generator formats those inputs as Markdown, ready to review, copy or download. It does not discover pages, check their contents or publish the file on your website.
What an llms.txt file contains
An llms.txt file introduces a site and points to selected resources. The llms.txt proposal describes a Markdown structure: a site-name H1, an optional summary blockquote and H2 sections containing links with optional notes. It is a proposed reference format; a file being available does not prove an agent uses it.
Use it to direct readers toward material that explains your site accurately. A sitemap supports URL discovery, while robots.txt describes crawler access rules. Keep those files for their own purposes.
Fill the generator with useful references
Enter the site name and base URL, then add a group title and at least one link label and URL. The summary and each link's description are optional. Names, group titles and labels accept up to 120 characters; summaries and descriptions accept up to 500. Write these as plain text rather than Markdown instructions.
Choose pages that answer distinct questions: what the product does, how to start, how an important feature works or which policy applies. For a documentation site, getting-started and reference pages may be more useful than every dated release note. Prefer a clean Markdown version when one actually exists; this generator does not create page versions.
Replace a vague label such as "Learn more" with "Getting started" and a factual note such as "Installation and first project setup." Open the destination yourself before describing it. Avoid claims that the linked page cannot support.
Use full HTTP or HTTPS URLs. The base URL sets the suggested publication path; it does not turn relative links into complete addresses. The form removes URL fragments, so a reference to https://example.com/docs/#setup becomes the page URL without #setup.
Choose main and Optional groups
Group essential references under clear titles, such as Documentation or Product. Use the Optional checkbox for secondary reading. In the proposal, the literal Optional section identifies material an agent may skip when using a shorter context; it does not hide links or restrict access.
Screpy prints ordinary groups first. All groups marked optional are combined into one final ## Optional section, without their original group titles. A title is still required in the form. If two optional groups contain three links each, the output has one Optional heading and six links.
You can enter up to 10 groups, 10 links per group and 50 links overall. These are input limits, not a recommended file size. Remove repetitive references rather than filling every available row.
Review a generated llms.txt example
For this fictional example, enter Atlas Guides as the site name and "Setup guides for a sample analytics product" as the summary. Create a Documentation group with a Getting started link and note. Add a Background group containing Release history, then mark that group optional. Using the example URLs below produces this structure:
# Atlas Guides
> Setup guides for a sample analytics product
## Documentation
- [Getting started](<https://example.com/docs/start/>): Installation and first project setup
## Optional
- [Release history](<https://example.com/releases/>): Earlier product changes
The generator escapes Markdown punctuation in text fields to preserve it as text. Line breaks inside descriptions become spaces. Check the final labels, notes and URLs in the preview rather than treating your inputs as custom formatting commands.
The result shows entered group and link counts, a suggested path and the generated text. A successful result confirms generation, not working destinations or AI adoption. The JSON report is separate from the publishable Markdown file.
Publish the file and check its links
Use Copy to move the generated text into your editor, or Download to save llms.txt. Review it before uploading it through your own website's publishing workflow. The generator does not install the file.
For a site-wide file, enter https://example.com/ as the base URL; the suggested path is /llms.txt. For https://example.com/docs/, it is /docs/llms.txt. The current proposal permits subpath files covering that part of a site. Choose a path that matches the resources you intend to describe.
After publishing, open the exact file URL without signing in. Confirm that it returns the intended Markdown text, rather than a login screen, an error page or your homepage. Check a subpath file at its own URL. A locally downloaded file is not evidence that the public endpoint exists.
Check selected destinations separately with the Bulk HTTP Status Checker. A successful HTTP response only confirms retrieval in that check; inspect the page to confirm its content matches the label. Replace obsolete URLs and descriptions after releases, moves or policy changes. Generation does not automatically maintain your published copy.
Does llms.txt improve SEO or AI visibility?
Publishing an llms.txt file does not guarantee indexing, rankings, citations or recommendations. Google's AI search guidance says special AI text files are not required for AI Overviews or AI Mode. Pages still need to be indexed and eligible for a Search snippet; meeting those conditions does not guarantee inclusion.
Use the file as an accurate reference map. If your question concerns crawler permissions, inspect that separately with the AI Bot Access Tester. A generated reference list does not grant access, change robots.txt rules or verify that any assistant follows the links.