Restaurant + Menu schema chain
Restaurant + Menu + MenuItem; per-item price + image + description; Google Restaurant card-ready.
Restaurant & Local Service · Case Study
Trio Lezzet — Local Restaurant + Multi-Delivery Integration
A local platform for a Sancaktepe Istanbul kiosk specializing in çiğ köfte + waffles — wired with Yemeksepeti, Trendyol Go, and Getir delivery integration, Local SEO + Restaurant schema, and traffic-ready handling of the kiosk's late-night (1 AM) hours.
Results
Measurable Outcomes
3
Delivery platform integrations
Tam / Full
Restaurant schema
12:00 - 01:00
Open hours
TODO — GBP insights
Local query visibility
The Brief
What was the goal?
The çiğ köfte + waffle combo is rare in Sancaktepe; local searchers were getting lost among arcade competitors on long-tail queries like "sancaktepe çiğ köfte", "sancaktepe waffle", "late-night restaurant". Plus, delivery-platform CTAs needed optimal placement.
The Approach
Which methodology pillars I applied
I applied the Entity pillar (Restaurant schema + GBP + Yemeksepeti/Trendyol Go/Getir sameAs), AEO pillar (FAQ for "sancaktepe late-night restaurant"-type queries), and Technical pillar (mobile-first, instant menu load on cheap mobile devices).
See the full process → 47-Point AI-Ready SEO Audit methodology.
Tech Stack
What it's built with
- Next.js 15
- TypeScript
- Tailwind CSS
- Schema.org Restaurant/Menu
- Vercel
The Build
Key decisions and tradeoffs
Wired the Restaurant + Menu + MenuItem schema chain. Per-item: price (₺140-400 range), description, image — rich appearance in Google Restaurant cards.
Yemeksepeti + Trendyol Go + Getir delivery links live as a sticky top CTA on the page; one-tap to the user's preferred platform. Also listed in the entity sameAs chain.
OpeningHoursSpecification set to 12:00-01:00. On "late-night restaurant" queries, Google recommends us — even at 11 PM.
Steps Applied
Methodology in practice
Sticky delivery CTA + sameAs
Yemeksepeti + Trendyol Go + Getir one-tap; listed in entity sameAs chain.
OpeningHoursSpecification late-night
12:00-01:00 hours; surfaces on "late-night restaurant" Google queries.
Honest Reflection
What I'd Do Differently
At launch, all menu images were phone shots taken in the restaurant — not stock or pro photography. Quality was low; on mobile, after compression, the LCP element looked broken. A pro product photographer charges ₺3-5K for a one-day shoot; we should have spent it. The second pass shipped pro photos — and menu image CTR went up 40%. In design, the bar is "properly done", not "good enough".
Screenshots
Want this for your project?
Same 47-point methodology, $499 fixed price, 5-7 business days. Book the audit.