Organizations › Local Business › Restaurant

Team Page Blueprint — Restaurant

Your team page structures your executive chef, sous chef, sommelier, and general manager with their credentials so AI knows who runs your restaurant. When someone asks "find a restaurant with a classically trained chef" or "restaurants with a certified sommelier," this blueprint makes sure your team shows up.

View Prompt View JSON

What this page needs

The team page is where AI learns about the people behind your restaurant. Culinary credentials matter — when AI needs to recommend a restaurant with a James Beard-nominated chef or a master sommelier, it pulls from structured employee data.

Restaurant with employee array. The main business node should include an employee array listing each team member as a Person node with their role and qualifications.
Person nodes with jobTitle and credential. Each chef, sommelier, or manager gets their own Person node with jobTitle, description, and hasCredential to capture their specific expertise.
Culinary certifications and training per team member. Use hasCredential on each Person node to list individual certifications — culinary school degrees, sommelier certifications, ServSafe credentials — so AI can match team members to expertise queries.
worksFor linking back to restaurant. Each Person node should include a worksFor reference back to the Restaurant node, creating a two-way connection between your team and your business.

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.

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 Team 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. Certification name
2. Certification type
3. Domain
4. Employee description
5. Employee job title
6. Employee name
7. Faq answer
8. Faq question
9. Restaurant name
10. Team page description
11. Team 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 Restaurant Team"
- 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 employee entries to match your actual team.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Restaurant",
      "@id": "https://YOUR_DOMAIN.com/#business",
      "name": "YOUR_RESTAURANT_NAME",
      "url": "https://YOUR_DOMAIN.com",
      "employee": [
        {
          "@type": "Person",
          "name": "YOUR_EMPLOYEE_NAME_1",
          "jobTitle": "YOUR_EMPLOYEE_JOB_TITLE_1",
          "description": "YOUR_EMPLOYEE_DESCRIPTION_1",
          "hasCredential": [
            {
              "@type": "EducationalOccupationalCredential",
              "name": "YOUR_CERTIFICATION_NAME_1A",
              "credentialCategory": "YOUR_CERTIFICATION_TYPE_1A"
            },
            {
              "@type": "EducationalOccupationalCredential",
              "name": "YOUR_CERTIFICATION_NAME_1B",
              "credentialCategory": "YOUR_CERTIFICATION_TYPE_1B"
            }
          ],
          "worksFor": {
            "@id": "https://YOUR_DOMAIN.com/#business"
          }
        },
        {
          "@type": "Person",
          "name": "YOUR_EMPLOYEE_NAME_2",
          "jobTitle": "YOUR_EMPLOYEE_JOB_TITLE_2",
          "description": "YOUR_EMPLOYEE_DESCRIPTION_2",
          "hasCredential": [
            {
              "@type": "EducationalOccupationalCredential",
              "name": "YOUR_CERTIFICATION_NAME_2A",
              "credentialCategory": "YOUR_CERTIFICATION_TYPE_2A"
            }
          ],
          "worksFor": {
            "@id": "https://YOUR_DOMAIN.com/#business"
          }
        },
        {
          "@type": "Person",
          "name": "YOUR_EMPLOYEE_NAME_3",
          "jobTitle": "YOUR_EMPLOYEE_JOB_TITLE_3",
          "description": "YOUR_EMPLOYEE_DESCRIPTION_3",
          "hasCredential": [
            {
              "@type": "EducationalOccupationalCredential",
              "name": "YOUR_CERTIFICATION_NAME_3A",
              "credentialCategory": "YOUR_CERTIFICATION_TYPE_3A"
            }
          ],
          "worksFor": {
            "@id": "https://YOUR_DOMAIN.com/#business"
          }
        }
      ]
    },
    {
      "@type": "WebPage",
      "@id": "https://YOUR_DOMAIN.com/team/",
      "name": "YOUR_TEAM_PAGE_TITLE",
      "description": "YOUR_TEAM_PAGE_DESCRIPTION",
      "isPartOf": {
        "@id": "https://YOUR_DOMAIN.com/#website"
      },
      "breadcrumb": {
        "@id": "https://YOUR_DOMAIN.com/team/#breadcrumb"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://YOUR_DOMAIN.com/team/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://YOUR_DOMAIN.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Team",
          "item": "https://YOUR_DOMAIN.com/team/"
        }
      ]
    },
    {
      "@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"
          }
        }
      ]
    }
  ]
}

Frequently asked questions

Should I include every staff member or just key team members?

Focus on team members whose credentials matter to guests — the executive chef, sous chef, sommelier, pastry chef, and general manager. Front-of-house staff or new hires without notable culinary credentials don't need structured schema unless they hold certifications. Quality of data beats quantity.

Why are individual culinary certifications important for AI?

AI systems increasingly match queries to specific credentials. When someone asks "find a restaurant with a certified sommelier," AI looks for hasCredential data on individual Person nodes — not just the business level. Listing certifications per team member gives AI precise data to work with.

What is the difference between the team page and the about page for a restaurant?

The about page covers your restaurant's overall story — founding history, culinary philosophy, and sourcing values. The team page zooms into individual people: each chef's name, title, specialties, and personal certifications. Think of the about page as your restaurant's story and the team page as individual staff profiles.