1. Publish a root llms.txt
The file belongs at yourdomain.com/llms.txt. If it only exists as an asset URL or hidden attachment, agents are still missing the stable root-level signal.
2. Make the key pages stronger than the summaries around them
Your product, pricing, docs, support, and contact pages should be current and explicit. A root file should point toward the best version of the truth on your site.
3. Remove naming ambiguity
Use the same product names, plan names, and service labels across the homepage, docs, pricing, and metadata. Models struggle when the same thing is described three different ways.
4. Back up claims with durable pages
If you mention compliance, security, SLAs, or support coverage, there should be a page on the site that can actually support that claim.
5. Keep the file current
When URLs move, product names change, or new canonical resources go live, update llms.txt. Otherwise the file becomes another stale layer the model has to work around.
A simple operating rhythm
- Generate the file.
- Publish it at the root.
- Check the linked pages for accuracy.
- Revisit it whenever the site structure changes.
If you want a fast starting point, use the builder, then move straight into the publishing guide and the directory for comparison.