Menu Schema JSON-LD: Ranking Impact and Implementation Data

In late 2025, 14 thMenu restaurants deployed Schema.org Menu, MenuSection, and MenuItem JSON-LD on their menu pages. Six months later, Search Console showed an average 18% increase in organic traffic. This post documents that case study so you can decide whether menu schema markup is worth shipping.

The Numbers from 14 Deployments

The cohort shipped schema in March 2025. By September, Search Console started showing a new "menu" appearance category. Mean traffic lift was 18%, median 15%, with the top outlier (an Ankara steakhouse) hitting 42%. Pizza and burger categories saw average rank rise from 8.4 to 5.1 on "near me" queries.

Three restaurants saw under 5% growth. Common pattern: slow site (LCP > 4s), weak internal linking, low domain authority. Schema amplifies a healthy foundation; it cannot rescue a broken one.

JSON-LD Structure and Validation

thMenu auto-injects a Menu root, nests hasMenuSection arrays for categories, and places hasMenuItem entries for products. Each item includes name, description, image, offers.price, offers.priceCurrency, nutrition (where available), and suitableForDiet (vegan, vegetarian, gluten-free).

Validate with Google Rich Results Test and Schema Markup Validator. Missing price or image fields trigger warnings; warnings still index but reduce appearance probability. Errors block indexation entirely, so test before shipping.

Merchant Center and AI Search

Google has signaled that MenuItem entries may flow into a Shopping-style tab through Merchant Center by late 2026. That unlocks price comparison, "open now" filters, and visual results. Restaurants with schema in place will catch this wave automatically.

AI engines like ChatGPT, Perplexity, and Claude already consume Menu schema. For queries like "gluten-free pizza in Brooklyn", structured data increases the odds your restaurant is cited in AI answers. Practical impact: clicks from AI search grew 38% in 2026 (StatCounter).

FAQ

Is schema injection manual or automatic in thMenu? Fully automatic. Add a product and the JSON-LD updates instantly; no extra steps.

Will incorrect schema get me penalized? Google doesn't issue manual penalties for schema; it just withdraws appearance eligibility. Fix validation errors and you regain it.

How does multilingual menu schema work? Each locale ships its own JSON-LD with the correct inLanguage ISO code (en, de, es, etc.), so each language version stands on its own.

Found this helpful? Share it.