A free tool
Generate your Open Service Profile.
It also writes your llms.txt. Enter your website. The tool reads your own pages, and your Google listing if you choose it, and drafts the files an AI assistant reads to learn who you are, where you work, when you are open, and how to request a booking.
One rule governs every line: a fact your pages do not state becomes a TODO line, never a plausible default. No price, hour, service, or certification is invented. Ratings and review counts are never copied; the standard forbids them.
What the files are
- open-service-profile.json goes at /.well-known/open-service-profile. It is the Open Service Profile manifest: your identity, locations and hours, services, coverage, and booking rules, in the shape the standard defines.
- llms.txt and llms-full.txt are the plain-text guides assistants read first. The short one summarizes; the long one carries every fact with its source and says how each derived value was produced.
- The robots.txt section names the AI crawlers and writes only the access you chose in the two robots.txt questions. Merge it into your existing robots.txt; until you answer, it is a commented template.
- jsonld.html is the Level 1 JSON-LD for your home page: a LocalBusiness node with a ScheduleAction, built from the same facts. Paste it inside <head>.
The standard makes no claim about search results or where an assistant places you. These files organize business information for assistants to read. The interoperability results are still pending. Every booking is a request; you confirm. The standard itself: Open Service Profile.
From the command line
The same generator runs locally with Node 20 or newer and no dependencies. It writes the five files into a folder and prints the TODO list: npx open-service-profile init <url>