Your booking page is the conversion point for your business. This blueprint uses a ReserveAction inside potentialAction so AI systems know that appointments can be scheduled directly through your site, enabling AI to guide users straight to your booking flow.
The booking page is where intent becomes action. When someone asks AI "book a haircut near me" or "schedule a facial," the AI needs to know which businesses accept online reservations and where to send the user. Without a structured ReserveAction, your booking page is invisible to this workflow.
potentialAction of type ReserveAction tells AI that your business accepts online appointments. The target URL points directly to your booking page or scheduling widget.HealthAndBeautyBusiness node ties the reservation action to your specific business, including name, address, and contact details.openingHoursSpecification tells AI your operating window so it does not send users to book at times you are closed.paymentAccepted tells AI whether you take cards, cash, or online payment, which helps filter recommendations for users with specific preferences.Each field in the template below serves a specific role in how AI systems discover, classify, and recommend your business.
Researched and tested by Minnesota AI
nameurltelephoneaddressopeningHoursSpecificationCopy this prompt and paste it into Claude, ChatGPT, Cursor, or any AI coding tool. It will ask for your business details and generate ready-to-use JSON-LD schema for your page.
You are implementing AIFDS-compliant JSON-LD structured data for a Health and Beauty Booking page. AIFDS (AI-Friendly Data Structure) is a schema framework built on research into which structured data fields AI systems actually read, parse, and use when deciding whether to cite a page. Documentation at aifds.org. Before generating any code, ask me for the following information in a single numbered list. Do not generate schema until I have answered every required field. REQUIRED — do not proceed without these: 1. Business name 2. City 3. Domain 4. Faq answer 5. Faq question 6. Payment methods 7. Phone number 8. Reservation name 9. Saturday close 10. Saturday open 11. State 12. Street address 13. Weekday close 14. Weekday open 15. Zip OPTIONAL — ask for these but proceed if I skip them: 1. Any additional details not covered above Once I provide the information, output a complete JSON-LD script block ready to paste into the <head> of my HTML page. Output requirements: - Valid JSON-LD wrapped in <script type="application/ld+json"> tags - schema.org vocabulary only - Every AIFDS-required field for this industry and page type included - Include this data attribute on the script tag: data-aifds="aifds.org Health and Beauty Booking" - No placeholder text — omit missing optional fields rather than fill with examples - After the code block, list any optional fields skipped that would strengthen AI citation
Generated schema follows the AIFDS framework. Fields were selected based on research into AI crawler behavior. View the research at minnesota.ai
Copy the template below and replace every YOUR_* value with your own data. This block goes in the <head> of your booking or appointment page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "HealthAndBeautyBusiness",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_BUSINESS_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "YOUR_WEEKDAY_OPEN",
"closes": "YOUR_WEEKDAY_CLOSE"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Saturday"],
"opens": "YOUR_SATURDAY_OPEN",
"closes": "YOUR_SATURDAY_CLOSE"
}
],
"paymentAccepted": "YOUR_PAYMENT_METHODS",
"potentialAction": {
"@type": "ReserveAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://YOUR_DOMAIN.com/book/",
"actionPlatform": [
"http://schema.org/DesktopWebPlatform",
"http://schema.org/MobileWebPlatform"
]
},
"result": {
"@type": "Reservation",
"name": "YOUR_RESERVATION_NAME"
}
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/book/",
"name": "Book an Appointment — YOUR_BUSINESS_NAME",
"url": "https://YOUR_DOMAIN.com/book/",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/book/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/book/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Book",
"item": "https://YOUR_DOMAIN.com/book/"
}
]
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_1",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_1"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_2",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_2"
}
},
{
"@type": "Question",
"name": "YOUR_FAQ_QUESTION_3",
"acceptedAnswer": {
"@type": "Answer",
"text": "YOUR_FAQ_ANSWER_3"
}
}
]
}
]
}
Use your own domain URL as the target if the booking widget is embedded on your site. If reservations redirect to a third-party URL, use that URL as the urlTemplate instead. The key is that the URL must actually lead to a working booking flow.
Include it on both. The homepage potentialAction tells AI that your business supports reservations at the site level. The booking page version reinforces this on the specific page where the action happens. AI may land on either page, so both should carry the signal.
Not on the booking page itself. The ReserveAction tells AI that appointments can be made. Your services page (with hasOfferCatalog) handles the individual service listings. Together, the two pages give AI the complete picture: what you offer and how to book it.