Key takeaways
- Use the most specific schema.org type: Restaurant, CafeOrCoffeeShop, BarOrPub, Bakery or another FoodEstablishment subtype[1].
- Google requires name and address for local business markup and recommends properties including telephone, url, openingHoursSpecification, geo, priceRange, servesCuisine and menu[2].
- FoodEstablishment adds acceptsReservations, which can be true or false, text, or a booking URL, and hasMenu for the menu[1].
- Validate with the Rich Results Test, deploy a few pages, then check them with URL Inspection before rolling out everywhere[2].
- Generate markup from the same data as the visible page so hours, menu and links never drift apart.
What structured data does for a restaurant
Structured data is a short block of code, usually JSON-LD placed in the page's head, that describes the page in a shared vocabulary from schema.org. For a restaurant, it states plainly what a search engine would otherwise have to infer from the page: this is a restaurant, this is its address, these are its hours, this is its cuisine, here is the menu, here is where to book.
Markup does not replace a good Google Business Profile or a clear website, and adding it does not guarantee any particular search feature. It reduces ambiguity, especially for sites with several locations, unusual hours or menus on separate pages. Treat it as part of keeping your details accurate everywhere, not as a ranking trick.
Step 1: Pick the right type
Schema.org's FoodEstablishment type has subtypes including Bakery, BarOrPub, Brewery, CafeOrCoffeeShop, Distillery, FastFoodRestaurant, IceCreamShop, Restaurant and Winery[1]. Choose the one that best describes the business guests visit. A coffee shop that serves food is still a CafeOrCoffeeShop; a gastropub can be a BarOrPub with food described through servesCuisine and hasMenu.
One location, one block of markup, on the page about that location. A restaurant group with three sites should have three location pages, each with its own markup, not one block listing every address.
Step 2: Fill in the properties
Google's local business documentation lists two required properties, name and address, and recommends including as many address properties as possible. Recommended properties include telephone, url, openingHoursSpecification, geo, priceRange, servesCuisine and menu, which for food establishments is the fully qualified URL of the menu. Google notes that aggregateRating and review are recommended only for sites that capture reviews about other local businesses, so a restaurant should not mark up its own selected testimonials as reviews[2].
| Property | What to put in it | Example value (fictional) |
|---|---|---|
| @type | Most specific FoodEstablishment subtype | Restaurant |
| name | Exact name on your sign and Google profile | Juniper Kitchen |
| address | PostalAddress with street, city, state, ZIP, country | 100 Example St, Springfield, IL 62701, US |
| telephone | Main public number, with country code | +1-312-555-0142 |
| url | The location page URL | https://example.com/springfield/ |
| geo | Latitude and longitude of the entrance | 41.92, -87.70 |
| openingHoursSpecification | Days and opening and closing times; special dates where needed | Tue–Sun 17:00–22:00 |
| servesCuisine | One or more cuisines, in plain words | Seasonal American |
| priceRange | A short price indicator | $$ |
| menu / hasMenu | URL of the HTML menu page, or a structured Menu | https://example.com/menu/ |
| acceptsReservations | True or false, or the booking URL | https://example.com/book/ |
| image | A few representative photos | Dining room, signature dish |
Step 3: Menus and reservations
Two FoodEstablishment properties matter most for restaurants. hasMenu accepts the actual menu as a structured representation, the menu as text, or a URL of the menu, and supersedes the older menu property. acceptsReservations indicates whether the establishment takes reservations; it accepts a true or false value, text, or a URL for booking[1].
- Simple and robust: hasMenu set to the URL of your HTML menu page, and acceptsReservations set to your own booking page URL.
- Detailed: a Menu object with MenuSection entries (Starters, Mains) and MenuItem entries with name, description and offers for price. Only do this if you can generate it automatically from your menu data.
- Several menus: a separate Menu for brunch, lunch, dinner and drinks, each pointing to its own page.
- No reservations: set acceptsReservations to false so the markup matches reality.
Pointing acceptsReservations at your own booking page is worth doing because guests often book through other doors. In a 2012 Cornell study, about 60% of diners who reserved online used a multi-restaurant site, while the rest used the restaurant's own website[3]. Make sure the booking path you control is clearly declared.
- Multi-restaurant reservation sites 60%
- The restaurant's own website 40%
Source: Cornell University Center for Hospitality Research (Kimes and Kies), 2012[3]
Show the data
| Item | Value |
|---|---|
| Multi-restaurant reservation sites | 60% |
| The restaurant's own website | 40% |
Step 4: Hours, including the tricky ones
- Use openingHoursSpecification entries for each set of days with the same hours, such as Tuesday to Thursday, then Friday and Saturday.
- For split service, such as lunch and dinner with a break, add two entries for the same day.
- For hours past midnight, follow the format in Google's documentation for times that run past midnight, and check the result in the Rich Results Test.
- For holidays, add special entries with validFrom and validThrough dates, and remove them afterward.
- Keep markup hours identical to the website footer and your Google profile.
Step 5: Test, deploy, then check again
Validate the code
Paste the page URL or code into Google's Rich Results Test and fix any critical errors before publishing[2].
Deploy to a few pages first
Publish markup on one or two location pages and leave the rest until the first ones check out.
Inspect the live pages
Use the URL Inspection tool in Search Console to see how Google fetched and read the deployed pages[2].
Roll out
Add markup to the remaining location pages, generated from the same template.
Recheck after changes
Run the test again after any change to hours, menu URLs, booking links or site templates.
Common mistakes
- Hours in markup that differ from the visible page or Google profile, often left over from before a seasonal change.
- A menu URL pointing to an old PDF or a third-party page instead of your current HTML menu.
- Marking up your own hand-picked testimonials as reviews or an aggregate rating.
- One block of markup listing all locations on the home page, instead of one per location page.
- Copying markup from a plugin or template without replacing placeholder values.
- Using a generic LocalBusiness type when Restaurant or another FoodEstablishment subtype fits.
Keep it maintained
Markup goes stale quietly. The safest setup generates it from the same source as the visible page: the site's location settings for name, address, phone and hours, and the menu data for hasMenu. If your site builder or plugin cannot do that, put a markup check on the same list as your Google profile check, and review it whenever hours, menus or booking systems change.
Example (fictional): a three-location taco group finds its home page carries a single block of markup with the first location's address and last year's hours. The developer replaces it with one generated block per location page, each using the location's own hours and booking link, validates two pages, inspects them live, then rolls out the third. The next hours change updates the footer and the markup together.
Single locations, groups and who maintains the code
Most restaurants only need one block of markup: 7 in 10 US restaurants are single-unit operations[4]. For them, the work is a single template on the home or location page, filled with the same details as the footer. Groups need more structure, and the risk of drift grows with every location.
- One location page per restaurant, each with its own markup, phone, hours, menu link and booking link.
- A parent organization, if you want one, described on the About page rather than repeated on each location.
- Separate markup for a ghost kitchen or delivery-only brand only if it has a real, eligible location.
- A named owner for the markup: the web developer, the agency or the person who edits the site. Write their name in your listing log.
- A check of every location page's markup after any site template change, since one template edit can break them all.
Where to put the code
Most site builders and content management systems let you add JSON-LD in the page head through a setting, a plugin or a code injection field. Plugins save time but often fill fields with defaults or leave placeholders, so check the output in the Rich Results Test rather than trusting the settings screen. If a developer hand-codes the markup, ask them to build it from the site's own location settings so it updates when the footer does. Avoid adding the same markup twice through a theme and a plugin at once, which produces duplicate or conflicting entries.
A quick markup checklist before you publish
- The type is the most specific FoodEstablishment subtype that fits.
- Name, address, phone and hours match the visible page and the Google profile exactly.
- The menu URL opens your current HTML menu, not a PDF or a third-party page.
- acceptsReservations points to your own booking page, or is false if you do not take bookings.
- There are no review or rating fields describing your own restaurant.
- The Rich Results Test shows no critical errors, and URL Inspection shows the live page was fetched.
Frequently asked questions
What schema should a restaurant use?
The most specific FoodEstablishment subtype, usually Restaurant, with name, address, telephone, url, hours, servesCuisine, a menu URL and acceptsReservations[1][2].
Is there menu schema for restaurants?
Yes. schema.org's hasMenu accepts a structured Menu, text or a URL. A structured Menu uses MenuSection and MenuItem entries[1].
How do I test restaurant structured data?
Validate with Google's Rich Results Test, deploy to a few pages, then check them with the URL Inspection tool before rolling out further[2].
Can a restaurant mark up its own reviews?
Google says aggregateRating and review markup are recommended only for sites that capture reviews about other local businesses, so a restaurant should not mark up its own selected reviews[2].
References
Schema.org (2026). FoodEstablishment (type definition) (opens in a new tab) ↑
Google Search Central (2026). Local business (LocalBusiness) structured data (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Kimes and Kies) (2012). The Role of Multi-Restaurant Reservation Sites in Restaurant Distribution Management (Cornell Hospitality Report, 2012) (opens in a new tab) ↑
National Restaurant Association (2025). National Statistics: Restaurant Industry Facts at a Glance (opens in a new tab) ↑