Restaurant Catering Stack
Restaurant catering pages with LocalBusiness + Service context, FAQs, and breadcrumb navigation.
When to use this stack
- Restaurant catering service pages with menu packages
- Pages listing catering service areas and minimums
- Pages where FAQs clarify lead times and delivery setup
What is included
Identifies the restaurant offering catering with NAP details.
Describes the catering service, provider, and service area.
Answers questions about minimums, lead time, and setup.
Provides navigation context for the catering 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.addressCountry
- address.addressLocality
- address.addressRegion
- address.postalCode
- address.streetAddress
- areaServed.name
- itemListElement[].name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- provider.@id
- serviceType
- telephone
- url
Recommended properties
- description
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.availability
- offers.url
- priceRange
- servesCuisine
- serviceOutput
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": "LocalBusiness",
"@id": "https://www.example.com/catering#business",
"name": "Northwind Bistro",
"url": "https://www.example.com/catering",
"telephone": "+1-512-555-0176",
"image": "https://www.example.com/images/northwind-bistro.webp",
"priceRange": "$$",
"servesCuisine": ["Mediterranean", "Seafood"],
"address": {
"@type": "PostalAddress",
"streetAddress": "200 Market St",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
}
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/catering#service",
"name": "Corporate Catering",
"serviceType": "Restaurant Catering",
"description": "Full-service catering with buffet setup, servers, and dietary accommodations.",
"provider": { "@id": "https://www.example.com/catering#business" },
"areaServed": { "@type": "AdministrativeArea", "name": "Austin" },
"offers": {
"@type": "Offer",
"price": "18.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/catering/request-quote"
},
"serviceOutput": "Buffet setup and staffed service"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is the minimum order size?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Catering orders start at 20 guests with a $350 minimum spend."
}
},
{
"@type": "Question",
"name": "How far in advance should I book?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Please book at least 7 days in advance for weekday events and 14 days for weekends."
}
},
{
"@type": "Question",
"name": "Do you provide staff and setup?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Buffet setup and on-site staff are available for an additional fee."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Catering", "item": "https://www.example.com/catering" }
]
}
]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
Should I include multiple catering packages?
If you list multiple packages, add separate Offer entries with the correct price and URL for each.
How do I show delivery fees?
Include delivery fees in the Offer description or list a separate Offer for delivery-only pricing.