A restaurant website that turns visitors into orders and bookings needs 15 things: a text menu with prices, an order button, a WhatsApp button, table reservations, click-to-call, Google Maps, correct hours, mobile-first design, fast loading, real food photos, reviews, occasion pages, SEO basics, structured data and tracking. Miss the first five and most visitors leave to order on an app or call a competitor.
This checklist is from Plateful Consulting (PFC), a Swiggy and Zomato growth consultancy in Noida that has worked with 650+ restaurants and also builds restaurant websites. It is written for owners, not developers. Use it to brief a designer, audit your current site or check a quote before you pay for one.
Quick answer
Your restaurant website has one job: turn a hungry or curious visitor into an order, a booking, a call or a visit.
Put four buttons on every mobile screen: Order, WhatsApp, Call and Book a table (or Directions).
Publish your menu as text with prices, not only as a PDF or photo. Google can read text; it struggles with images.
Get the basics identical everywhere: name, address, phone and opening hours must match your Google Business Profile, Swiggy and Zomato.
Design for a phone on 4G first. Most visitors arrive from Google Maps or Instagram on mobile.
Use real photos of your food, not stock images, and show reviews from real guests.
Track every click on order, WhatsApp, call and booking buttons, or you will never know if the site pays back.
Budget sensibly. PFC builds restaurant websites from ₹15,000.
What a restaurant website has to do in 2026
Most diners in India discover restaurants on Swiggy, Zomato, Google Maps and Instagram. Your restaurant site is where they land to check the menu, prices, location, hours or whether they can book or order direct.
That gives a good resto website four jobs:
Answer questions fast. Menu, prices, location, hours and contact within one scroll.
Convert. A visible next step on every screen: order, chat, call, book or get directions.
Prove quality. Food photos, reviews, awards and your story, so a first-time guest trusts you.
Own the customer. Capture repeat guests on channels you control, such as WhatsApp and direct ordering, instead of renting every order from an aggregator.
A food restaurant website that only looks good does none of these.
The 15 restaurant website must-haves at a glance
# | Must-have | Why it matters | Quick test |
|---|---|---|---|
1 | Text menu with prices | The most visited page on most restaurant sites | Can you copy a dish name from it? |
2 | Online ordering | Captures orders without aggregator commission | Order in under 60 seconds on a phone |
3 | WhatsApp button | The channel Indian guests already use | Does it open a chat with a pre-filled message? |
4 | Table reservations | Turns intent into a confirmed cover | Booking in three taps or fewer |
5 | Click-to-call | Many guests still prefer to call | Tap the number; does the dialler open? |
6 | Google Maps and directions | Removes the "where exactly is it?" drop-off | One tap to navigation |
7 | Correct name, address, phone and hours | Mismatches cost trust and local ranking | Compare with your Google profile |
8 | Mobile-first design | Most visits come from phones | Use it one-handed on a small phone |
9 | Fast loading | Slow pages lose hungry visitors | Run Google PageSpeed Insights |
10 | Real food photography | Photos sell food before words do | Are any images stock photos? |
11 | Reviews and social proof | First-time guests look for proof | Is there a review within the first two scrolls? |
12 | Occasion, party and bulk-order pages | Higher-value enquiries | Can a guest enquire about a party of 20? |
13 | SEO basics | Brings "near me" and dish searches | Unique title and description on each page |
14 | Restaurant structured data | Helps search engines read your details | Run Google's Rich Results Test |
15 | Tracking | Shows what the site earns | Do you know last month's WhatsApp clicks? |
Must-haves 1–5: the restaurant website buttons that make money
1. A text menu with prices
Your menu page is usually the most visited page on the site. Publish it as real text, organised by category, with prices, short descriptions and veg or non-veg markers. A PDF or a photo of the printed menu is hard to read on a phone, hard to update and hard for Google to understand. Keep a PDF as an extra if you like, never as the only version.
2. Online ordering
An "Order online" button should appear in the header and again on the menu page. You have three options: your own ordering system, a white-label ordering platform, or buttons that send guests to your Swiggy and Zomato listings. Direct ordering avoids aggregator commission but adds payment, delivery and software costs, so read direct ordering vs Swiggy and Zomato before you decide. Many restaurants do both: direct ordering for loyal regulars, app links for everyone else.
3. A WhatsApp button
For Indian guests, WhatsApp is often the easiest way to ask "Are you open?", "Can you do a birthday cake?" or "Can I order for 15 people?". Add a floating WhatsApp button on mobile. WhatsApp's own click-to-chat guide explains the link format: https://wa.me/ followed by your number in international format, and you can add a pre-filled message such as "Hi, I want to place an order". That saves the guest typing and tells your team where the lead came from. Make sure someone actually answers during service hours.
4. Table reservations
For dine-in restaurants, cafés and bars, the reservation button is as important as the order button. Use a booking widget, a short form (name, phone, date, time, guests) or a WhatsApp booking flow. Confirm every booking quickly. Show your reservation policy, for example how long you hold a table. If you also take bookings on Zomato or Swiggy Dineout, keep one source of truth so you never double-book.
5. Click-to-call
Put your phone number in the header as a tappable link, not an image. Many family diners and corporate bookers still prefer to call. With several outlets, show each outlet's own number on its page.
Must-haves 6–9: location, hours, mobile and speed
6. Google Maps and one-tap directions
Embed a map on your contact or outlet page and add a "Get directions" button that opens Google Maps navigation. Add a landmark line in plain words, such as "Second floor, above the bank", because Indian addresses alone often confuse guests.
7. Correct name, address, phone and hours
Your name, address and phone number (often called NAP) and your opening hours must match exactly across your website, Google Business Profile, Swiggy, Zomato, Instagram and directories. Mismatches confuse guests and can weaken local search signals. Update holiday hours and festival closures on the website the same day you update Google. If you have several outlets, give each one its own page with its own address, hours, phone and map.
8. Mobile-first restaurant website design
Design for a mid-range Android phone first, then make the desktop version look good. Practical rules:
A sticky bottom bar on mobile with Order, WhatsApp, Call and Book or Directions.
Large buttons that are easy to tap with a thumb.
Readable text without zooming, and no pop-ups that cover the menu.
Menu categories you can jump to without endless scrolling.
9. Fast loading
Hungry visitors are impatient, often on patchy mobile data. Google's Core Web Vitals guidance sets "good" thresholds of 2.5 seconds or less for the main content to load (LCP), 200 milliseconds or less to respond to a tap (INP) and a layout shift score of 0.1 or less (CLS), measured at the 75th percentile of visits. Compress photos, avoid autoplay background videos on mobile, limit heavy plugins and test the site with Google PageSpeed Insights before you go live.
Must-haves 10–12: design that builds trust
10. Real food photography
Photos sell food faster than any description. Use bright, well-lit photos of your actual dishes, your space and your team. Stock photos are easy to spot and make guests wonder what the real food looks like. Shoot your top 15–20 dishes first, plus the interior and exterior so first-time guests recognise the place. If you are in Delhi NCR, PFC's food photography service covers Delhi, Noida, Gurugram, Ghaziabad and Faridabad, starting at ₹25,000 for a one-day shoot with up to 50 edited images. The same photos can then feed your Swiggy, Zomato, Google and Instagram listings.
11. Reviews and social proof
Show a few real guest reviews with names or initials and the platform they came from, plus your Google rating if it is strong. Add awards or press mentions only if they are genuine. Never write or buy fake reviews.
12. Occasion, party and bulk-order pages
Birthday parties, office lunches, kitty parties and festival orders are often worth many times a normal order. Give them their own page with what you offer, sample packages, minimum numbers and a short enquiry form or WhatsApp link. A cafeteria website for a corporate canteen or institutional caterer should lead with exactly this: menus, capacity, hygiene and a clear enquiry route.
Must-haves 13–15: SEO, structured data and tracking for your restaurant site
13. SEO basics
Your website should help you show up when someone searches your brand, your area or your signature dish. The basics:
A unique page title and meta description for every page, for example "Butter Chicken in Rohini | [Your Restaurant Name]".
One page per outlet, with the area and city in the heading and text.
Dish names and cuisine words in plain text on the menu page.
Descriptive alt text on photos and a link from your Google Business Profile.
HTTPS, a working XML sitemap and the site verified in Google Search Console.
14. Restaurant structured data
Structured data is code that tells search engines what your page is about. Schema.org's Restaurant type includes properties such as servesCuisine, hasMenu, acceptsReservations, openingHours, address, telephone and priceRange. Ask your developer to add it to the home page and each outlet page, then check it with Google's Rich Results Test. It does not guarantee any special display, but it removes guesswork about your details.
15. Tracking
If you cannot measure it, you cannot tell whether your website pays back. Set up Google Analytics 4 and track these actions as events: order button clicks, WhatsApp clicks, call clicks, booking submissions, direction clicks and enquiry forms. Add UTM tags to the website link in your Instagram bio, Google profile and any ads. If you run Meta ads to the site, install the Meta pixel too. Review the numbers once a month.
Worked example: what a restaurant website can be worth
Illustrative only. These are not client figures. A family restaurant gets 2,000 website visits a month, mostly from Google and Instagram.
Action | Assumed rate | Monthly result | Value |
|---|---|---|---|
Direct orders via the order or WhatsApp button | 2% of visits | 40 orders at ₹600 | ₹24,000 of sales |
Table bookings | 1.5% of visits | 30 bookings of 3 guests at ₹700 a head | ₹63,000 of sales |
Party or bulk enquiries | 2 that convert | 2 events at ₹15,000 | ₹30,000 of sales |
Total | ₹1,17,000 of sales a month |
The direct orders also avoid aggregator commission. If your effective take-rate on Swiggy and Zomato is around 30%, those 40 direct orders keep roughly ₹7,200 a month that would otherwise go in commission, fees and discounts, before your own delivery and payment costs. Work out your own figure with the commission calculator.
Even at half these numbers, a website that costs from ₹15,000 can pay for itself quickly. None of it happens if the buttons are hidden or nobody answers WhatsApp.
Restaurant website design by outlet type
QSRs
Lead with ordering and offers. Put the order button, menu prices and combos on the first screen. Keep it simple and fast: your guests want to order, not read your story.
Cloud kitchens
You have no dining room, so your website is your shopfront. Show your brands, delivery areas, order links for each app plus direct ordering, and a WhatsApp button for bulk orders. Do not show a public address that sends walk-ins to a kitchen with no seating.
Cafés
Cafés sell an experience. Lead with interior photos, signature drinks, hours and directions, plus a booking or enquiry button for small groups.
Fine dining
Reservations come first. Show tasting and à la carte menus, dress code, the chef's story and private dining. Booking must still take three taps or fewer on a phone.
Multi-outlet brands
Build one page per outlet with its own address, hours, phone, map and booking link. Add a franchise enquiry page if you franchise, a careers page and a corporate or catering page. Keep menus and prices in one system so you do not have twenty out-of-date PDFs.
Common restaurant website mistakes
Mistake | What it costs | Fix |
|---|---|---|
Menu only as a PDF or photo | Guests pinch and zoom, then leave; Google cannot read it well | Publish the menu as text with prices |
No order or WhatsApp button on mobile | Visitors go to an app or a competitor | A sticky bottom bar with the key actions |
Old hours or a disconnected number | Wasted trips and angry reviews | Update the site the same day as Google |
Autoplay video hero on mobile | Slow loading, high bounce | A compressed photo and a clear button |
Stock photos | Guests distrust the food | Shoot your own dishes and space |
One page for many outlets | Weak local search and confused guests | One page per outlet |
No tracking | No idea whether the site pays back | GA4 events on every key button |
Website built, never updated | Old offers and prices damage trust | A monthly 30-minute update routine |
Your 30-day plan to build or fix your restaurant website
Days 1–3: Audit. Open your current site on a phone. Score it against the 15 must-haves above and list what is missing.
Days 4–6: Gather content. Current menu and prices, outlet addresses, hours, phone numbers, logo, brand colours, your story in 100 words and ten genuine reviews.
Days 7–10: Photos. Shoot your top dishes, interior and exterior, or book a professional shoot.
Days 11–18: Build. Home, menu, order, reservations, outlet pages, party and catering, about and contact. Mobile first.
Days 19–21: Connect. Ordering links, WhatsApp click-to-chat, booking widget, Google Maps, structured data, GA4 events.
Days 22–24: Test. Place a real order, make a booking, tap every button, run PageSpeed Insights and the Rich Results Test.
Days 25–27: Launch. Add the link to Google Business Profile, Instagram bio, WhatsApp Business profile, table tents and bills.
Days 28–30: Review. Check the first clicks in GA4 and fix the weakest button.
DIY builder, ordering platform or custom restaurant website?
A DIY builder suits a single café with time to manage it. An ordering-platform site suits restaurants that mainly want direct orders, though design and SEO control are limited. A custom site suits brands that want design, SEO and tracking done properly. Whichever route you choose, make sure you own your domain, can edit the menu yourself and get access to analytics. Plateful Consulting (PFC) builds restaurant websites from ₹15,000, designed around the 15 must-haves above, with ordering, WhatsApp, booking and tracking set up. Tell us what you need on our contact page.
Why restaurants choose Plateful Consulting (PFC)
650+ restaurants worked with across Delhi NCR, Bengaluru, Hyderabad, Mumbai, Pune and more.
Run by operators. The founders ran their own cloud kitchen before starting PFC, so the website is built around orders, not just looks.
7+ years on the platforms and ₹8 crore+ in delivery-app ad spend managed, so your website fits into a wider Swiggy, Zomato and direct-order plan.
Named results. Drama in Delhi grew combined net sales from ₹33.81L to ₹51.32L a month. Punjabi Rasoi's Rohini outlet grew online sales from ₹20.1L to ₹34.3L a month. Individual outcomes, not guarantees.
One team for website, photos and growth. Restaurant websites from ₹15,000 and food photography in Delhi NCR from ₹25,000.
See named cases on our results page and everything we do on our services page. Not sure where to start? Get a free growth audit and we will review your website alongside your Swiggy and Zomato listings.
Frequently asked questions
What should a restaurant website include?
At minimum: a text menu with prices, an order button, a WhatsApp button, click-to-call, table reservations if you take bookings, Google Maps directions, correct address and hours, real food photos and reviews. Then add SEO basics, restaurant structured data and tracking on every button. Everything should work smoothly on a phone, because that is where most of your visitors will be.
How much does a restaurant website cost in India?
It depends on the route. DIY builders charge a monthly fee and need your time. Ordering platforms often charge a subscription or per-order fee. Freelancers and agencies quote anywhere from a few thousand rupees to several lakh for custom work. Plateful Consulting (PFC) builds restaurant websites from ₹15,000. Add a yearly domain and hosting cost, and ask every vendor what updates are included.
Is it worth hiring an agency to build a restaurant website?
It is worth it if the agency builds for orders and bookings, not just looks, and if the site pays back faster than its cost. Ask to see restaurant sites they have built, check them on your phone and confirm you will own the domain and content. A simple, fast site with clear buttons usually beats an expensive one that is hard to update.
Who makes the best restaurant websites in India or Delhi?
There is no single right answer. Look for designers who have built live restaurant sites you can test on your phone, who understand ordering, WhatsApp and reservations, and who set up tracking. Ask about speed, ownership and update support. PFC builds restaurant websites from ₹15,000 and is happy to show live examples, but compare a few options before you choose.
Do I need a website if I am already on Swiggy and Zomato?
Yes, if you want to own part of your customer relationship. Aggregators rent you customers and charge commission on every order. Your website lets regulars order direct, book tables, enquire about parties and find accurate details. It also supports your Google presence. Read our guide on reducing aggregator dependency.
Can I take online orders on my own restaurant website?
Yes. You can use your own ordering system, a white-label ordering platform or a simple WhatsApp ordering flow. You will need payments, delivery cover (your own riders or a delivery partner) and someone to manage orders. Compare the cost per order with your aggregator take-rate before you push direct ordering hard, and keep app links for guests who prefer them.
Should I upload my menu as a PDF?
Not as the only version. A PDF is hard to read on a phone, slow to load and harder for Google to understand. Publish the menu as text on a web page, with categories, prices and short descriptions. You can keep a PDF download for guests who want to print it or share it.
How do I add a WhatsApp button to my restaurant website?
Use WhatsApp's click-to-chat link: https://wa.me/ followed by your number in full international format, without spaces or a leading zero. You can add a pre-filled message with ?text= followed by your message. Place it as a floating button on mobile and on the order and contact pages. Make sure someone replies quickly during opening hours.
How do I get my restaurant website to show on Google?
Verify the site in Google Search Console and submit a sitemap. Give each page a clear title and description, create one page per outlet with the area name, and publish your menu as text. Link the website from your Google Business Profile and keep your address, phone and hours identical everywhere. Add restaurant structured data. Rankings build over weeks, not days.
How long does it take to build a restaurant website?
A focused restaurant website with menu, ordering links, WhatsApp, booking and outlet pages can usually be built in two to four weeks once you have content ready. The usual delays are missing photos, an unfinished menu and slow approvals. Use the 30-day plan above to keep the project on track.
Does a café or cafeteria need a website?
Yes, but it can be simple. A café needs photos, menu, hours, directions and a booking or enquiry button for groups. A cafeteria website for a corporate or institutional caterer should show menus, capacity, hygiene practices and a clear enquiry route for contracts and events. Both should load fast and work well on a phone.
How do I know if my restaurant website is working?
Track actions, not just visits. In Google Analytics 4, count order clicks, WhatsApp clicks, calls, bookings, direction clicks and enquiry forms each month. Compare them with the orders and bookings your team actually receives. If visits are high but clicks are low, fix the buttons and menu. If both are low, work on Google and Instagram traffic.
Last updated: 18 November 2026.
