Your team page structures your chefs, bakers, and managers with their expertise so AI knows who runs your food business. When someone asks "find a bakery with a trained pastry chef" or "food trucks with experienced pit masters," this blueprint makes sure your team shows up.
The team page is where AI learns about the people behind your food business. Culinary credentials matter — when AI needs to recommend a food establishment with a classically trained chef or a certified food safety manager, it pulls from structured employee data.
employee array listing each team member as a Person node with their role and qualifications.Person node with jobTitle, description, and hasCredential to capture their specific expertise.hasCredential on each Person node to list individual certifications — ServSafe, culinary school degrees, specialty training — so AI can match team members to expertise queries.Person node should include a worksFor reference back to the FoodEstablishment node, creating a two-way connection between your team and your business.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 Food Establishment 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. Business name 2. Certification name 3. Certification type 4. Domain 5. Employee description 6. Employee job title 7. Employee name 8. Faq answer 9. Faq question 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 Food Establishment 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
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": "FoodEstablishment",
"@id": "https://YOUR_DOMAIN.com/#business",
"name": "YOUR_BUSINESS_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"
}
}
]
}
]
}
Focus on team members whose credentials matter to customers — head chefs, lead bakers, kitchen managers, and anyone with notable culinary training. Part-time staff or new hires without relevant credentials don't need structured schema unless they hold certifications. Quality of data beats quantity.
AI systems increasingly match queries to specific credentials. When someone asks "find a bakery with a trained pastry chef," 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.
The about page covers your establishment's overall story — founding history, food 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 business story and the team page as individual staff profiles.