Restaurant Reservation Stack
Reservation pages with FoodEstablishmentReservation + Restaurant context, FAQs, and breadcrumb navigation.
When to use this stack
- Restaurant reservation pages with booking details
- Dining pages that need reservation confirmation context
- Pages where FAQs clarify policies and dining requirements
What is included
Captures the reservation details and booking context.
Represents the restaurant entity with location and contact details.
Answers questions about cancellations, seating, and dietary needs.
Provides navigation context to the reservation page.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- address.addressLocality
- address.addressRegion
- address.streetAddress
- itemListElement[].name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- partySize
- reservationFor.@id
- reservationId
- reservationStatus
- startTime
- telephone
- url
Recommended properties
- bookingTime
- endTime
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- modifiedTime
- priceRange
- servesCuisine
- underName.name
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "Restaurant",
"@id": "https://www.example.com/restaurants/lucent#restaurant",
"name": "Lucent Bistro",
"url": "https://www.example.com/restaurants/lucent",
"telephone": "+1-212-555-0179",
"image": "https://www.example.com/images/lucent-bistro.webp",
"servesCuisine": ["French", "Modern American"],
"priceRange": "$$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "250 Madison Ave",
"addressLocality": "New York",
"addressRegion": "NY",
"postalCode": "10016",
"addressCountry": "US"
}
},
{
"@context": "https://schema.org",
"@type": "FoodEstablishmentReservation",
"@id": "https://www.example.com/restaurants/lucent#reservation",
"reservationId": "RES-2025-0418-8821",
"reservationStatus": "https://schema.org/ReservationConfirmed",
"startTime": "2025-04-18T19:30:00-04:00",
"endTime": "2025-04-18T21:30:00-04:00",
"partySize": 4,
"reservationFor": { "@id": "https://www.example.com/restaurants/lucent#restaurant" },
"underName": {
"@type": "Person",
"name": "Taylor Brooks"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is your cancellation policy?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Cancellations are free up to 24 hours before your reservation."
}
},
{
"@type": "Question",
"name": "Do you accommodate dietary restrictions?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Please include dietary notes in your reservation or contact us directly."
}
},
{
"@type": "Question",
"name": "Is there a dress code?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Smart casual is recommended. Jackets are optional."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Restaurants", "item": "https://www.example.com/restaurants" },
{ "@type": "ListItem", "position": 3, "name": "Lucent Bistro", "item": "https://www.example.com/restaurants/lucent" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Can I include multiple reservation slots?
Yes. Use one FoodEstablishmentReservation per reservation if multiple are listed on the page.
What if a reservation is pending?
Use reservationStatus with ReservationPending and include bookingTime if shown.