llms-txt-builder
Create llms.txt files that help AI systems navigate and understand your site structure for better citations.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
llms.txt Builder
Audience: Site owners wanting AI visibility Goal: Generate llms.txt file for AI system navigation
What is llms.txt?
A file at https://yoursite.com/llms.txt that helps AI systems understand site structure.
Format
# Site Name
> Brief description of the site and its purpose
## Main Sections
- [Section Name](URL): Description of this section
- [Products](URL): Description of products/services
- [Blog](URL): Description of blog content
## Key Resources
- [Getting Started Guide](URL): Description
- [API Documentation](URL): Description
- [Pricing](URL): Description
## Contact
- Email: contact@example.com
- Support: support@example.com
Best Practices
- Keep descriptions concise (1 sentence each)
- Prioritize most important pages (top 10-15)
- Update when site structure changes
- Include key landing pages for each persona
- Use consistent formatting
Content Priority
Must Include:
- Homepage
- Core product/service pages
- Main category pages
- Contact/support
Should Include:
- Popular blog posts
- Key documentation
- Pricing page
- About/team page
Consider:
- Case studies
- Integration pages
- API docs
- Changelog
Workflow
- Scan site structure (glob for main pages)
- Identify priority pages per section
- Write concise descriptions
- Format as llms.txt
- Validate links work
- Recommend placement in root
Output
# [Site Name]
> [One-line site purpose]
## Main Sections
[3-5 core sections with links]
## Key Resources
[5-10 important pages]
## Contact
[Support channels]
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-02-04
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!