Back to tools
Restaurant schema generator

Generate clean Restaurant JSON-LD without touching Schema.org docs

Fill in the practical restaurant fields Google expects to see. Copy the JSON-LD into your site, then validate it with Google Rich Results Test or Schema Markup Validator.

Structured data

Restaurant schema helps search engines connect the dots.

A good Restaurant schema block turns scattered page copy into machine-readable facts: name, address, cuisine, phone, menu, reservation URL, opening hours, and profiles. It will not magically rank a weak site, but it reduces ambiguity around the business entity and its guest actions.

Only include facts you can verify. Do not add fake reviews, ratings, prices, or opening hours.

Build your schema

Required fields are name, address, locality, and country. Everything else improves context.

Schema checklist

  • Required name
  • Complete address
  • Menu URL
  • Reservation URL
  • Cuisine and price range
  • Opening hours

JSON-LD output

Add a restaurant name and address to generate JSON-LD.

Before you paste

Restaurant schema FAQ

  • What schema type should a restaurant use?

    Use Restaurant when food service is the main business. It is more specific than LocalBusiness and supports restaurant-specific fields like servesCuisine, menu, and acceptsReservations.

  • Can I add ratings if I have Google reviews?

    Only add ratings if they are shown on the page and you control the source in a way that follows Google guidelines. Do not copy ratings from platforms without displaying and validating them properly.

  • Where should JSON-LD go?

    Place it in a script tag with type application/ld+json on the relevant page. In most frameworks, the head or page component is the right place.

  • How does Guestavo use this idea?

    Guestavo can expose public venue, menu, reservation, and event pages. Those pages become more valuable when their structured data is generated from verified venue data.

Schema is better when it comes from real venue data.

Keep restaurant facts, menus, events, and reservation links in one system instead of rebuilding JSON-LD by hand every time something changes.