AI visibility for
restaurants.
Expose a readable menu, dietary information and current opening details so diners can check a specific meal plan.
A menu should be readable, not just viewable
A photo or scanned PDF can make a menu inconvenient for both diners and automated readers. Publish the core dishes, prices where appropriate and dietary notes in accessible page text. Make the current menu easy to distinguish from an old seasonal version. If an item’s preparation can change, give diners a clear route to confirm allergies directly with staff.
Publish the dining details that matter
- State cuisine, service style and the actual address and opening hours.
- Identify vegetarian or other dietary options using verified menu information.
- Explain reservation rules, group constraints and accessibility details.
- Keep seasonal menus, kitchen closing times and temporary closures up to date.
Structure the real menu
Restaurant can describe the venue, while Menu and MenuItem can describe the published offering. An illustrative summary might read: “[Brand] serves [cuisine] at [address], with a lunch menu from [verified hours].” Do not turn one dietary option into a blanket allergy-safety guarantee. A booking widget should not be the only place key dining policies appear.
Read a recommendation in its context
Sample a neighborhood cuisine question, a dietary constraint and a branded opening-hours question. Record the exact wording; changing the budget or group size changes the decision. Check whether sources cite the current menu or an outdated review. A mock mention and a high technical score do not establish food quality or a safe meal.
Technical failures to check on restaurant sites
- Menu as a PDF or photo. When the menu exists only as a file or image, crawlers get no dish names or prices. Publish dishes, prices and dietary notes in HTML, and keep the PDF for printing.
- Booking widget as the only content. Reservation systems embedded from another domain leave the page with no text about the restaurant. Add a description of the cuisine, opening times and location.
- Hours that change seasonally but not online. Holiday closures and summer hours often appear only on social media. Update the site first and keep hours in text.
- Allergen information missing or in an image. Diners ask about allergens and dietary options. State what is available and how to ask staff, without promising an allergen-free kitchen you cannot guarantee.
- Multiple locations on one page. Groups that list every venue in one block make each harder to find. Give each location its own page with address, hours and menu link.
Search the page source of your menu page for three dish names. If they are missing, the menu is an image or file. Compare the opening hours on your site with those on your business profiles and social accounts during the next holiday period. Read your allergen statement and confirm it explains how to ask staff rather than promising what the kitchen cannot guarantee. If you run more than one venue, check that each has its own address, hours and menu link on a separate page.
Example JSON-LD
Restaurant describes the venue. Link a Menu that is published as HTML on your site. The example below is illustrative: replace every bracketed value with facts from your own page.
{
"@context": "https://schema.org",
"@type": "Restaurant",
"name": "[Restaurant name]",
"url": "https://[domain]/",
"telephone": "[Phone]",
"servesCuisine": "[Cuisine]",
"address": {
"@type": "PostalAddress",
"streetAddress": "[Street]",
"addressLocality": "[City]",
"addressCountry": "[Country code]"
},
"hasMenu": "https://[domain]/menu",
"acceptsReservations": true,
"openingHours": "Tu-Su 12:00-22:00"
}Mark up individual MenuItem prices only if the HTML menu shows them and you update both together.