Restaurant structured data: the schema that actually helps

Structured data is a block of machine-readable code that tells search engines what a page is about in terms they already understand: this is a restaurant, it serves this cuisine, it opens at these hours, it sits at this address, and this is its menu. It does not change what the page says to a guest. It changes how confidently a search engine can interpret it.

For restaurants the return is unusually good, because almost every fact a guest wants before booking — hours, address, price band, cuisine, menu — is a fact search engines have a documented property for.

Google is explicit that structured data helps it understand content and can make a page eligible for rich results. Eligibility is not entitlement — a valid markup block is a request, not a guarantee, and Google can choose plain results for any query.

• It does: describe entities and their properties in a standard vocabulary
• It does: make a page eligible for certain enhanced search appearances
• It does: reduce ambiguity where your name, address or hours appear inconsistently elsewhere
• It does not: rank a page on its own
• It does not: allow you to claim star ratings you have not genuinely collected on your own site

Source: Google Search Central — Intro to how structured data works — Google's own description of eligibility, formats and validation.

Ignore the long tail of schema types. Four blocks cover almost everything a restaurant benefits from, and each maps to a page you should already have.

Multi-site groups add one Restaurant block per location page, each with that venue's own address, hours and phone number — never a single shared block repeated across every page.

Source: Google Search Central — Local business structured data — Restaurant is a LocalBusiness subtype; this page documents the supported properties, including menu and reservation actions.

Hours in structured data have to match the hours on the page, and both have to match the Business Profile. Where the three disagree, the profile usually wins in Maps and the guest loses in practice — arriving to a closed door and leaving a review about it.

Menu structured data is only as good as the page underneath it. A PDF menu cannot be marked up meaningfully, and a menu rendered as a flat image cannot be read at all. The markup is the last ten per cent; an HTML menu with real headings, dish names, descriptions and prices is the other ninety.

1. 01Write it as JSON-LD in a script tag — Google's recommended format, and the easiest to maintain
2. 02Populate it from the same source as the visible page, so the two cannot drift apart
3. 03Validate with the Rich Results Test before publishing
4. 04Recheck in Search Console after indexing, under the relevant enhancement report
5. 05Re-validate whenever hours, menus or booking links change

Source: Google Search Central — Rich Results Test — The validation tool that reports eligibility and errors for a live or pasted page.

Structured data rarely produces a step change you can point at. What it produces is fewer misunderstandings: correct hours in the result, a breadcrumb path, an FAQ expanded under the listing, a menu that can be quoted. Watch Search Console's enhancement reports for valid items and errors, then watch click-through rate on the affected pages over a full month rather than a week.

Written by

Alex Opsenica

Founder, Moolah Media

Founder of Moolah Media, a founder-led restaurant marketing specialist based in Ireland, working with restaurants worldwide on websites, SEO and Google Maps, and Google Ads. Around 20 years in hospitality, including hands-on restaurant management.

More about how Moolah works.