The menu page is where AI systems learn what your café actually serves. Structured menu data lets AI answer specific drink and food queries, compare prices, and surface your offerings when someone asks for a latte, a pastry, or a breakfast spot. This blueprint gives you the complete JSON-LD graph for a machine-readable café menu.
A menu page without structured data is just a list of text that AI has to guess about. With proper schema markup, AI can parse your menu into drink categories, food items, prices, and dietary flags, making your café far more useful in coffee and food queries.
Menu node with hasMenuSection organizes your offerings into logical categories like espresso drinks, drip coffee, pastries, and breakfast items that AI can navigate.MenuItem inside a section includes a name, description, price, and optional dietary restriction flags so AI can answer specific queries about your offerings.CafeOrCoffeeShop node with hasMenu connects the menu to your business identity, ensuring AI knows which café this menu belongs to.offers with price and priceCurrency on each item lets AI compare your prices and answer budget-related queries.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 Menu 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. Diet type 3. Domain 4. Drink description 5. Drink name 6. Drink price 7. Faq answer 8. Faq question 9. Food description 10. Food name 11. Food price 12. Menu description 13. Menu name 14. Menu page title 15. Section description 16. Section name 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 Menu" - 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 menu page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CafeOrCoffeeShop",
"@id": "https://YOUR_DOMAIN.com/#cafe",
"name": "YOUR_CAFE_NAME",
"url": "https://YOUR_DOMAIN.com",
"hasMenu": {
"@type": "Menu",
"@id": "https://YOUR_DOMAIN.com/menu/#menu",
"name": "YOUR_MENU_NAME",
"description": "YOUR_MENU_DESCRIPTION",
"hasMenuSection": [
{
"@type": "MenuSection",
"name": "YOUR_SECTION_NAME_1",
"description": "YOUR_SECTION_DESCRIPTION_1",
"hasMenuItem": [
{
"@type": "MenuItem",
"name": "YOUR_DRINK_NAME_1",
"description": "YOUR_DRINK_DESCRIPTION_1",
"offers": {
"@type": "Offer",
"price": "YOUR_DRINK_PRICE_1",
"priceCurrency": "USD"
}
},
{
"@type": "MenuItem",
"name": "YOUR_DRINK_NAME_2",
"description": "YOUR_DRINK_DESCRIPTION_2",
"offers": {
"@type": "Offer",
"price": "YOUR_DRINK_PRICE_2",
"priceCurrency": "USD"
}
}
]
},
{
"@type": "MenuSection",
"name": "YOUR_SECTION_NAME_2",
"description": "YOUR_SECTION_DESCRIPTION_2",
"hasMenuItem": [
{
"@type": "MenuItem",
"name": "YOUR_FOOD_NAME_1",
"description": "YOUR_FOOD_DESCRIPTION_1",
"offers": {
"@type": "Offer",
"price": "YOUR_FOOD_PRICE_1",
"priceCurrency": "USD"
},
"suitableForDiet": "YOUR_DIET_TYPE"
}
]
}
]
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/menu/#webpage",
"url": "https://YOUR_DOMAIN.com/menu/",
"name": "YOUR_MENU_PAGE_TITLE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/menu/#menu"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/menu/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Menu",
"item": "https://YOUR_DOMAIN.com/menu/"
}
]
},
{
"@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"
}
}
]
}
]
}
No. List each drink once and use the description field to note available sizes. If prices differ by size, you can add multiple Offer objects inside an offers array, each with a name like "Small" or "Large" and its corresponding price.
Use logical groupings that match how customers think about your menu. Common café sections include "Espresso Drinks," "Drip Coffee & Tea," "Pastries & Baked Goods," and "Breakfast." Each MenuSection should have a clear name and description.
Yes, but keep the data current. Add seasonal items when they launch and remove them when the season ends. Stale menu data is worse than no menu data — AI may recommend a drink you no longer serve, damaging trust.