Industry template

Local services llms.txt template

For local services, users ask about coverage, price ranges, and availability. Include pages that set clear expectations before booking.

What to include for a real booking decision

Coverage: city/zone pages with service windows and dispatch limits.
Estimate logic: base fee, after-hours fee, travel fee, and what changes the quote.
Scheduling rules: same-day availability, reschedule/cancel terms, and no-show handling.
Guarantee terms: warranty duration, exclusions, and follow-up response time.

Concrete example: emergency plumbing site

Keep one canonical page for each service type (drain cleaning, leak repair, water heater).
Map service-area pages by city, not duplicate near-identical neighborhood pages.
Publish one estimate policy page with plain-language price variables.
Add booking and guarantee pages as separate sources so assistants can quote policy accurately.

# Service Brand

> Service Brand provides [service type] across [service region].

## Summary

Service Brand publishes service descriptions, location coverage, estimate policy, booking rules, guarantees, and support channels.

## Service Sources

- [Services](https://example.com/services): What is offered and scope limits.
- [Service areas](https://example.com/areas): Coverage by city or zone.
- [Estimates](https://example.com/estimates): Pricing logic and variables.
- [Booking policy](https://example.com/booking): Scheduling, reschedule, and cancellation terms.
- [Guarantee](https://example.com/guarantee): Warranty and follow-up process.

First-week verification

# key entry files
for p in /llms.txt /robots.txt /sitemap.xml; do
  curl -s -o /dev/null -w "%{http_code} %{url_effective}\n" "https://yourdomain.com$p"
done

# local-service page coverage in crawler fetches
grep -Ei 'OAI-SearchBot|PerplexityBot' /var/lib/caddy/logs/llmsfile-access.log \
| grep -Ei '/services/|/areas/|/pricing/|/booking/|/guarantee/' \
| tail -n 80