llms.txt examples you can adapt for different website types
Use these examples as starting points. Replace every URL, summary, and policy note with accurate information from your own public website.
SaaS website
# Example SaaS > Example SaaS helps operations teams route customer requests and measure response quality. Important notes: - The pricing page is the canonical source for plan limits. - The docs explain setup and integrations. - Do not infer private roadmap details. ## Core pages - [Product overview](https://example.com/product): Main product capabilities and use cases - [Pricing](https://example.com/pricing): Current public plans and billing limits - [Documentation](https://example.com/docs): Setup, integrations, and API references - [Security](https://example.com/security): Public security and compliance information ## Optional - [Blog](https://example.com/blog): Educational articles and product updates
Ecommerce store
# Example Store > Example Store sells durable travel accessories for carry-on travelers. Important notes: - Product pages are the canonical source for materials, dimensions, and availability. - Shipping and returns pages override older blog content. ## Core pages - [All products](https://example.com/products): Current product catalog - [Carry-on backpack](https://example.com/products/carry-on-backpack): Product details and specifications - [Shipping policy](https://example.com/shipping): Shipping regions, delivery timing, and fees - [Returns](https://example.com/returns): Return window and eligibility ## Optional - [Packing guides](https://example.com/blog/packing): Travel packing advice
Local service business
# Example Repair Co > Example Repair Co provides same-day appliance repair in Austin, Texas. Important notes: - Service area pages define where bookings are available. - Contact page is the canonical source for hours and phone number. ## Core pages - [Services](https://example.com/services): Appliance repair services offered - [Service areas](https://example.com/areas): Neighborhoods and cities served - [Booking](https://example.com/book): Public booking and contact options - [Reviews](https://example.com/reviews): Customer testimonials and proof points ## Optional - [Troubleshooting guides](https://example.com/guides): DIY checks before booking
Documentation site
# Example Docs > Example Docs explains how to build and deploy apps with the Example framework. Important notes: - Versioned docs should be interpreted by their version path. - The changelog lists breaking changes. ## Core pages - [Quickstart](https://example.com/docs/quickstart): First setup path - [API reference](https://example.com/docs/api): Public API methods and options - [Deployment](https://example.com/docs/deploy): Production deployment guidance - [Changelog](https://example.com/changelog): Releases and breaking changes ## Optional - [Examples](https://example.com/examples): Sample apps and recipes
Publisher or blog
# Example Guide > Example Guide publishes practical, source-backed explainers about home energy upgrades. Important notes: - Articles include visible publish and update dates. - Buying guides disclose affiliate relationships where applicable. ## Core pages - [Best heat pump guide](https://example.com/heat-pumps): Current buying guide - [Solar calculator](https://example.com/solar-calculator): Free estimate tool - [Methodology](https://example.com/methodology): How recommendations are researched - [Corrections policy](https://example.com/corrections): Editorial corrections process ## Optional - [Archive](https://example.com/archive): Older articles