Restaurant schema markup
JSON-LD structured data covering menu, opening hours, address, telephone, price range, accepted payment methods. Google reads it as a real restaurant, not a generic webpage.
Section 01
What the client actually wanted
The owner runs a family restaurant in Gwalior. He'd been getting orders through phone calls and a basic Instagram page, and walk-ins from people who already knew the place. New customers were finding him through word of mouth, but slowly.
He didn't want a fancy website with animations and parallax scrolling. He wanted three things: somewhere customers could see the menu, a way to place orders without calling, and a Google listing that didn't look broken. That was the entire brief.
"Bhaiya, kuch aisa banao jisse log seedha order kar sakein. Phone uthane ka time nahi rehta lunch mein."
That brief drove every decision. No homepage carousel. No "About our journey" timeline. No newsletter signup. A clean menu, a WhatsApp button, a Google Maps embed, and structured data so the restaurant shows up properly when someone searches.
Section 02
How it got built in nine days
The promise was four weeks because that's a fair window for a small business website. The reality was nine days because the brief was tight, the client was responsive on WhatsApp, and the AI workflows handled the parts that usually take the most time.
Day one to three: structure, copy, and on-page SEO drafted with AI assistance, then edited by hand for the local context. Day four: the menu PDF was processed and structured into both a downloadable and a screen-readable format. Day five and six: schema markup for the restaurant, the menu items, the operating hours, the location. This is the part that makes Google take a restaurant seriously.
Day seven: WhatsApp ordering integration with pre-filled message templates so a customer tapping the order button gets a chat that already has the dish names ready to send. Day eight: Google Maps embed, click-to-call buttons, mobile testing on six different screen sizes. Day nine: launch, indexing request to Google, owner trained on how to update the menu.
Section 03
What changed mid-flight
The original plan had a basic contact form. By day five, it was clear that nobody who orders from a small restaurant fills a contact form. They either call or they message on WhatsApp. So the contact form was scrapped and replaced with a single big WhatsApp button on every page.
The menu was also supposed to be a single long page. The client mentioned that his menu changes seasonally with festivals and weather. So instead of hard-coding it, the menu became a downloadable PDF the owner could replace whenever needed. Cheaper to maintain. Faster to update. No coding knowledge required from the client.
These changes came from staying in WhatsApp contact with the client almost every day, not from a quarterly roadmap meeting. Solo operations aren't slower. They're more responsive.