The contact page is where AI systems find the fastest path to connect a customer with your restaurant. Structured contact data ensures AI can surface your phone number, address, email, and hours directly in answers without sending the user to dig through your site.
When someone asks AI "how do I reach this restaurant" or "what are their hours," the contact page is the authoritative source. Structured data here ensures AI does not have to guess or scrape unstructured text for your phone number and address.
ContactPage schema type tells AI this page is the canonical source for reaching your restaurant, distinguishing it from other pages that may incidentally mention a phone number.telephone and email properties on the Restaurant node give AI the direct contact methods to surface in answers.PostalAddress lets AI provide directions, calculate distances, and display your location in map-based answers.openingHoursSpecification array lets AI answer "are they open right now" queries with confidence.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
nameurltelephoneemailaddressopeningHoursSpecificationCopy 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 Contact 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. City 2. Contact page title 3. Domain 4. Email address 5. Faq answer 6. Faq question 7. Phone number 8. Restaurant name 9. State 10. Street address 11. Sunday close 12. Sunday open 13. Weekday close 14. Weekday open 15. Weekend close 16. Weekend open 17. Zip 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 Contact" - 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 contact page.
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "ContactPage",
"@id": "https://YOUR_DOMAIN.com/contact/#webpage",
"url": "https://YOUR_DOMAIN.com/contact/",
"name": "YOUR_CONTACT_PAGE_TITLE",
"isPartOf": {
"@id": "https://YOUR_DOMAIN.com/#website"
},
"about": {
"@id": "https://YOUR_DOMAIN.com/#restaurant"
}
},
{
"@type": "Restaurant",
"@id": "https://YOUR_DOMAIN.com/#restaurant",
"name": "YOUR_RESTAURANT_NAME",
"url": "https://YOUR_DOMAIN.com",
"telephone": "YOUR_PHONE_NUMBER",
"email": "YOUR_EMAIL_ADDRESS",
"address": {
"@type": "PostalAddress",
"streetAddress": "YOUR_STREET_ADDRESS",
"addressLocality": "YOUR_CITY",
"addressRegion": "YOUR_STATE",
"postalCode": "YOUR_ZIP",
"addressCountry": "US"
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday"],
"opens": "YOUR_WEEKDAY_OPEN",
"closes": "YOUR_WEEKDAY_CLOSE"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Friday", "Saturday"],
"opens": "YOUR_WEEKEND_OPEN",
"closes": "YOUR_WEEKEND_CLOSE"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Sunday",
"opens": "YOUR_SUNDAY_OPEN",
"closes": "YOUR_SUNDAY_CLOSE"
}
]
},
{
"@type": "BreadcrumbList",
"@id": "https://YOUR_DOMAIN.com/contact/#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://YOUR_DOMAIN.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Contact",
"item": "https://YOUR_DOMAIN.com/contact/"
}
]
},
{
"@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"
}
}
]
}
]
}
Yes. Use the same @id for the Restaurant node so AI knows it is the same entity, but include the full address and hours here as well. The contact page is the authoritative source for contact information, and AI systems may crawl pages independently. Redundancy ensures completeness regardless of which page AI reads first.
For a single-location restaurant, the telephone property directly on the Restaurant node is sufficient and simpler. Use contactPoint if you have separate numbers for different purposes, such as one for reservations and another for catering inquiries.
Schema.org supports validFrom and validThrough on OpeningHoursSpecification for temporary hour changes. If you close for holidays or have seasonal hours, add entries with date ranges. However, keep your regular hours as the default and only add date-specific overrides as needed.