A quick sanity check on the structured data Google sees
Paste your JSON-LD or a page of HTML and the checker will tell you which fields Schema.org expects, which Google rewards, and which you have quietly forgotten. No account, nothing saved on our side.
Why this exists
Rich results live and die by the small fields
LocalBusiness, Restaurant, Event, and FAQPage markup is what lets Google show your hours, reviews, reservation link, and price band in the result card. Miss a required field and the rich result is silently dropped; miss a recommended one and it stops standing out. This tool runs the checks without asking you to open DevTools.
Educational, not a substitute for the Rich Results Test. Use Google’s tool once you have cleaned the obvious misses.
Paste your markup
Drop a single JSON-LD object, an array, or the full HTML of a page. The checker auto-detects the mode on change.
Paste something to get started
The results panel will list each detected @type with its own checklist. Use the Load example button to see a slightly-broken sample.
Questions we get
Schema checker FAQ
What does LocalBusiness schema actually do?
It tells Google what you are, where you are, when you are open, how to call you, and how guests rate you. With it, the search card can show hours, phone, rating stars, a reservation link, and a map pin. Without it, Google has to guess, and usually does badly.
Why do reviews need aggregateRating with a reviewCount?
Google only renders star ratings in the result card if the markup has both a ratingValue and a reviewCount (or ratingCount). A rating on its own is ignored. Pulling those numbers from your actual review system, not inventing them, is also a hard requirement.
What does priceRange accept?
Either the currency-symbol shorthand ("€", "€€", "€€€", "€€€€") or a plain range like "$10–$30". Keep it consistent across pages. It maps to the "$", "$$", "$$$" dots you see on restaurant result cards.
JSON-LD or microdata — which should I use?
JSON-LD. Google has said so explicitly for years and every tool assumes it. Microdata still works but it is much harder to maintain and much easier to break. JSON-LD also lives in a single script block you can swap without touching the HTML.
How is this different from Google Business Profile?
Business Profile is the listing you manage inside Google. Schema markup is the metadata on your own website. Google cross-references them; conflicts between the two (hours, address, phone) confuse ranking. The checker makes sure the metadata on your side is clean — you still need to claim and maintain your Business Profile separately.
We build this markup for you automatically on Guestavo venue pages.
Every public venue page on Guestavo ships with a validated LocalBusiness / Restaurant schema including hours, reservation link, and menu. No tinkering, no copy-paste — it is just there.