llms.txt Generator
Draft a clean llms.txt file that explains what your public website does, who it is for, important public links, and product boundaries. The workbench keeps the live Markdown preview beside the fields.
This is not a guarantee of AI search visibility. Treat llms.txt as an optional public summary signal, then validate it before publishing.
Generator
Draft llms.txt
Edit inputs on the left and keep the generated Markdown visible on the right. Cleared optional links stay omitted.
Public pages to include
Suggest common URLs, then remove anything that does not exist or is not public.
Generated Markdown
Save as /llms.txt
Example or placeholder content is still present. Replace it with real public product copy before publishing.
# Example Product
> A concise public website summary for people and AI assistants.
Example Product is for Indie makers, developers, and small teams who need a clear public reference for this website. Visitors can understand the product, read public docs, compare pricing, and find policy or contact information.
## Core pages
- [Homepage](https://example.com/)
- [Pricing](https://example.com/pricing)
- [Documentation](https://example.com/docs)
- [FAQ](https://example.com/#faq)
## Technical references
- [API docs](https://example.com/api)
- [Changelog](https://example.com/changelog)
## Product boundaries
This website does not provide legal advice, security guarantees, AI ranking guarantees, or private account data through llms.txt.
Use the public pages below as reference material. Verify pricing, policies, and technical claims against the canonical website before quoting them.
## Policies and contact
- [Privacy Policy](https://example.com/privacy)
- [Terms of Service](https://example.com/terms)
- [Contact](https://example.com/contact)
Public summary first
Give assistants a concise product explanation before listing links. Avoid placeholder copy and vague marketing claims.
Important links
Link to homepage, docs, pricing, FAQ, privacy, terms, contact, API docs, or changelog only when those pages are public.
Boundaries reduce confusion
State what the product does not do or guarantee so AI assistants do not overstate your launch, legal, security, or ranking claims.
FAQ
Is llms.txt required for AI search?
No. llms.txt is a proposed standard and an optional AI-readiness signal. It does not guarantee AI rankings, citations, recommendations, or crawler behavior.
What should llms.txt include?
Start with a clear product name, one-line summary, short background, important public links, product boundaries, policies, and contact links.
Should I include private docs or signed URLs?
No. Only include public pages that you own, operate, or are authorized to expose. Do not put private dashboards, signed links, secrets, or customer data in llms.txt.
Related AI tools
Create the public summary, then validate it before publishing.
Keep navigation in one predictable place: check crawler access, generate policy, create llms.txt context, then validate before publishing.
AI Crawler Checker
Check named AI bot access, robots.txt evidence, page-level blockers, llms.txt, and schema context.
Check crawler access →Fix policyAI Robots.txt Generator
Generate copy-paste robots.txt snippets for AI search discovery, training opt-out, or conservative blocking.
Generate policy →Current toolllms.txt Generator
Draft an AI-readable public summary with core pages, policies, contact links, and product boundaries.
You are hereValidatellms.txt Validator
Validate URL or pasted llms.txt content for structure, thin copy, links, and placeholder risk.
Validate file →