The catering page tells AI that your café offers coffee service for events, offices, and group orders. Without structured data here, AI may know you are a coffee shop but have no signal that you cater. This blueprint structures your catering offerings so AI can surface your café when someone asks for coffee catering.
Catering is a distinct service that needs its own structured data. AI systems treat it differently from your walk-in menu — it answers queries like "coffee catering for office meetings" or "who caters coffee in my area?" The catering page must declare what you offer, how much it costs, and how to book it.
Offer with name, description, and price lets AI compare your packages and recommend the right one for a query.areaServed property tells AI where you deliver catering, which is critical for location-based catering queries.CafeOrCoffeeShop entity ensures AI knows which business provides the catering service.potentialAction of type OrderAction tells AI that catering can be ordered from this page.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
nameurlCopy 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 Cafe or Coffee Shop Catering 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. Cafe name 2. Catering package 3. City 4. Domain 5. Faq answer 6. Faq question 7. Package 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 Cafe or Coffee Shop Catering" - 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 belongs in a <script type="application/ld+json"> tag in the <head> of your catering page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CafeOrCoffeeShop",
"@id": "https://YOUR_DOMAIN.com/#cafe",
"name": "YOUR_CAFE_NAME",
"url": "https://YOUR_DOMAIN.com",
"makesOffer": [
{
"@type": "Offer",
"name": "YOUR_CATERING_PACKAGE_1",
"description": "YOUR_PACKAGE_1_DESCRIPTION",
"price": "YOUR_PACKAGE_1_PRICE",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
{
"@type": "Offer",
"name": "YOUR_CATERING_PACKAGE_2",
"description": "YOUR_PACKAGE_2_DESCRIPTION",
"price": "YOUR_PACKAGE_2_PRICE",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
],
"areaServed": {
"@type": "City",
"name": "YOUR_CITY"
},
"potentialAction": {
"@type": "OrderAction",
"target": "https://YOUR_DOMAIN.com/catering/",
"name": "Order Catering"
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/catering/#webpage",
"url": "https://YOUR_DOMAIN.com/catering/",
"name": "Catering — YOUR_CAFE_NAME",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#cafe"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/catering/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Catering",
"item": "https://YOUR_DOMAIN.com/catering/"
}
]
},
{
"@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"
}
}
]
}
]
}
Offer works well for catering packages with defined prices. If your catering is more of a custom service with variable pricing, you could use Service with an offers property. For most cafés with set packages, Offer attached via makesOffer is the simplest and most effective approach.
Very important. Unlike your walk-in business where location is implied by your address, catering has a delivery radius. The areaServed property tells AI exactly where you deliver, so it can match you to queries like "coffee catering in downtown Minneapolis."
Yes, and you should. Using the same @id tells AI that the catering offers belong to the same business entity declared on the homepage. AI merges data from nodes with matching IDs, so your catering details enrich your overall business profile.