Use case

llms.txt generator for local business websites

Local service sites win in AI answers when service scope and policies are explicit. Keep your file focused on pages with concrete details.

What “good” looks like for local-service visibility

• Service scope is explicit: each service page includes what is covered, what is excluded, and expected turnaround.
• Area pages are real: coverage pages include city-level constraints, arrival windows, and contact channel.
• Pricing page explains logic: base fees, factors that change price, and examples.
• Policy pages are citeable: booking, cancellation, and guarantee terms are easy to quote.

Recommended source pages

• Service pages with scope and exclusions.
• Service area pages with city coverage.
• Estimate and pricing explanation page.
• Booking and scheduling policy page.
• Warranty or guarantee terms page.

Example rollout for a plumbing company

1. Start with 6 pages: drain cleaning, leak repair, water heater, areas, pricing, and booking terms.
2. Keep one canonical URL per service. Avoid duplicates by city unless content is materially different.
3. After publishing, check 7-day logs: crawler hits should move beyond /robots.txt into listed service pages.

Example rollout for a dental clinic

1. Start with services that people ask assistants about: emergency appointment, cleaning, whitening, implants, insurance, and new-patient intake.
2. Use plain source pages for eligibility, price ranges, appointment timing, and what happens during the visit.
3. Do not make medical claims inside llms.txt. Link the clinical source pages and let those pages carry the detail.

Example rollout for a home repair contractor

1. List service pages for roofing, siding, gutter repair, storm damage, service areas, warranty, and estimate policy.
2. Add a page that explains emergency vs scheduled work, because AI answers often need that distinction.
3. Keep franchise or branch pages separate only when hours, coverage, pricing, or license information differs.

First-week checks that prevent wasted work

1. All listed URLs return 200 and are indexable.
2. Apex and www return the same file behavior for /llms.txt.
3. Cloudflare/WAF rules do not challenge crawl-entry paths.

Concrete page examples that improve answer quality

• Drain cleaning page: includes starting price, what adds cost (pipe length, blockage type), and typical completion window.
• Service-area page: includes same-day availability by district and after-hours surcharge policy.
• Booking policy page: includes cancellation cutoff, reschedule limits, and no-show fee conditions.

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
grep -i 'OAI-SearchBot\|PerplexityBot' /var/log/nginx/access.log | tail -n 80

Related pages: local business template, local-services industry template, and root deployment checklist.

# Business Name

> Business Name provides [services] for customers in [region].

## Summary

This file maps service, area, pricing, scheduling, and guarantee sources.

## Sources

- [Services](https://example.com/services): Included and excluded work scope.
- [Service Areas](https://example.com/areas): Coverage by city and neighborhood.
- [Pricing](https://example.com/pricing): Estimate logic and cost factors.
- [Booking](https://example.com/book): Appointment process and timing.
- [Guarantee](https://example.com/guarantee): Warranty duration and terms.

Open local business generator flow