Organizations › Local Business › Restaurant

Pricing Page Blueprint — Restaurant

Structures your prix fixe menus, tasting menus, and private dining packages so AI can answer cost questions directly. When someone asks "how much is the tasting menu at a restaurant downtown" or "affordable private dining options in Minneapolis," this page gives AI the exact numbers.

View Prompt View JSON

What this page needs

A pricing page is where AI gets the hard numbers. When someone asks "how much is dinner for two" or "find a restaurant with a prix fixe under $100," the structured data on this page is what lets AI give a direct answer instead of guessing from your menu.

Restaurant with hasOfferCatalog. The hasOfferCatalog field wraps your pricing into a structured catalog of Offer nodes, each tied to a specific dining experience with a clear price.
Offer nodes with price and priceCurrency. Each prix fixe menu, tasting menu, or private dining package should have its own Offer with explicit price and priceCurrency fields so AI can quote exact rates.
priceRange on the business node. A general priceRange (e.g., "$$" or "$25–$75") gives AI a quick tier signal for filtering when users ask for "affordable" or "fine dining" options.
MenuItem descriptions inside each offer. Each Offer should wrap a MenuItem with a clear name and description so AI knows exactly what the price covers — how many courses, wine pairings, and any included extras.

Why these fields matter to AI

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

Restaurant

name: Non-negotiable. AI cannot cite or recommend an unnamed entity.
url: AI needs a stable URL to route users and attribute recommendations.
telephone: AI won't recommend a local business it can't confirm is reachable. Phone is the primary trust signal for location-based queries.
priceRange: AI filters local recommendations by budget. One of the most common qualifiers in location-based queries.

Use This Prompt to Implement Your Schema

Copy 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 Restaurant 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. Domain
2. Faq answer
3. Faq question
4. Item description
5. Item name
6. Phone number
7. Price
8. Price range
9. Pricing page description
10. Pricing page title
11. Restaurant 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 Restaurant 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

Template — fill in your values

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": "Restaurant",
      "@id": "https://YOUR_DOMAIN.com/#business",
      "name": "YOUR_RESTAURANT_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "telephone": "YOUR_PHONE_NUMBER",
      "priceRange": "YOUR_PRICE_RANGE",
      "hasOfferCatalog": {
        "@type": "OfferCatalog",
        "name": "Dining Packages",
        "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"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Should I list every menu item or just highlight dining packages?

Use the pricing page for structured dining experiences — prix fixe menus, tasting menus, private dining packages, and wine pairings. Individual dish prices belong on the menu page. The pricing page gives AI the high-level cost picture for special dining experiences that go beyond ordering a la carte.

How should I handle private dining pricing that varies by group size?

Create separate Offer nodes for each tier or package — for example, "Private Dining for 10–20 guests" and "Private Dining for 20–40 guests" with their respective per-person prices. AI can then answer "how much is a private dinner for 25 people" by matching the right tier.

Should the pricing page duplicate prices that are already on the menu page?

No. The menu page should cover individual dish pricing. The pricing page focuses on experiences and packages — tasting menus, prix fixe dinners, wine pairings, and private event rates. Keep each page's pricing distinct so AI has clear, non-overlapping data to work with.