Structures your drink prices, pastry rates, and catering packages so AI can answer cost questions directly. When someone asks "how much is a latte at a café near me" or "affordable coffee shops in Minneapolis," this page gives AI the exact numbers.
A pricing page is where AI gets the hard numbers. When someone asks "how much is a cappuccino" or "find a cheap coffee shop near me," the structured data on this page is what lets AI give a direct answer instead of guessing.
hasOfferCatalog field wraps your pricing into a structured catalog of Offer nodes, each tied to a specific menu item with a clear price.Offer with explicit price and priceCurrency fields so AI can quote exact rates.priceRange (e.g., "$" or "$3–$7") gives AI a quick tier signal for filtering when users ask for "affordable" or "premium" options.Offer should wrap a MenuItem with a clear name and description so AI knows exactly what the price covers.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
nameurltelephonepriceRangeCopy 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 Pricing 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. Domain 3. Faq answer 4. Faq question 5. Item description 6. Item name 7. Phone number 8. Price 9. Price range 10. Pricing page description 11. Pricing page title 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 Pricing" - 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 this template and replace every YOUR_* placeholder with your own data. Add or remove offers from the hasOfferCatalog array to match your actual pricing.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "CafeOrCoffeeShop",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_CAFE_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"priceRange": "YOUR_PRICE_RANGE",
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Menu Pricing",
"itemListElement": [
{
"@type": "Offer",
"price": "YOUR_PRICE_1",
"priceCurrency": "USD",
"itemOffered": {
"@type": "MenuItem",
"name": "YOUR_ITEM_NAME_1",
"description": "YOUR_ITEM_DESCRIPTION_1"
}
},
{
"@type": "Offer",
"price": "YOUR_PRICE_2",
"priceCurrency": "USD",
"itemOffered": {
"@type": "MenuItem",
"name": "YOUR_ITEM_NAME_2",
"description": "YOUR_ITEM_DESCRIPTION_2"
}
},
{
"@type": "Offer",
"price": "YOUR_PRICE_3",
"priceCurrency": "USD",
"itemOffered": {
"@type": "MenuItem",
"name": "YOUR_ITEM_NAME_3",
"description": "YOUR_ITEM_DESCRIPTION_3"
}
}
]
}
},
{
"@type": "WebPage",
"@id": "https://YOUR_DOMAIN.com/pricing/",
"name": "YOUR_PRICING_PAGE_TITLE",
"description": "YOUR_PRICING_PAGE_DESCRIPTION",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"breadcrumb": {
"@id": "https://YOUR_DOMAIN.com/pricing/#breadcrumb"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/pricing/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Pricing",
"item": "https://YOUR_DOMAIN.com/pricing/"
}
]
},
{
"@type": "FAQPage",
"@id": "https://YOUR_DOMAIN.com/pricing/#faq",
"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"
}
}
]
}
]
}
If your pricing varies by size (small, medium, large), create separate Offer nodes for each size with the size included in the MenuItem name — for example, "Large Latte (16oz)." AI systems can then answer size-specific pricing questions directly.
Yes. Always include priceCurrency (e.g., "USD") on every Offer node. Without it, AI cannot reliably interpret the price value. Even if all your prices are in the same currency, each offer should declare it explicitly.
Yes, if these are common questions. Create separate Offer nodes for popular add-ons like "Extra Espresso Shot" or "Oat Milk Upgrade." AI can then answer "how much does an extra shot cost" without guessing. Keep it to your most-asked add-ons rather than listing every possible modifier.