Melbourne has more restaurants per capita than almost any other city in the world. The food is world-class. The marketing is world-class. The websites, for most of these places, are a disaster. PDF menus from 2018. OpenTable widgets crash-landing in the middle of the page. Stock photography of generic food that isn't theirs. "Our chef trained in Paris and believes in seasonal ingredients" on every single About page.

If your Melbourne restaurant has a website that looks like most Melbourne restaurant websites, it's leaking customers every day. Here's what a good one actually has.

1. Real photography of your actual food

This is the single biggest lever on any restaurant website and almost everyone gets it wrong.

Stock photos of "food" look like stock photos. Even the expensive ones. A visitor's brain processes "this is stock photography" in about half a second and downgrades their trust in the rest of the site accordingly. The photos you have of your actual food, shot in your actual dining room, with your actual plating — even if shot on an iPhone by a waiter — are worth more than the most expensive licensed stock image ever will be.

The correct investment is a half-day with a Melbourne food photographer. Budget $800–$2,500. In a few hours you get 20–40 usable shots of your menu, your space, and your staff. This is the single most impactful $1,500 most restaurant websites can spend.

If budget genuinely doesn't allow for a photographer, a smartphone and natural window light in the afternoon will beat stock photography nine times out of ten. The bad version is generic. The authentic version is you.

2. A current menu in the actual site, not a PDF from 2019

Every week we see a restaurant site with a menu link that opens a PDF. The PDF is usually:

Out of date (prices, specials, and dishes no longer on the menu)
A scan of a printed menu (low resolution, hard to read, obvious it was faxed from 1997)
Designed for print, not screens (tiny text, unreadable on mobile)
An ugly placeholder that actively hurts the brand

The fix is to put the menu on the actual page as HTML text. That means:

Your team can update it from the CMS in minutes
It renders correctly on every device
Google can index it (menu items are a real SEO ranking factor)
It respects dietary tags and allergen indicators
It doesn't require the visitor to download anything

A live menu also lets you highlight specials, mark dishes as "new", show dishes the kitchen is proud of, and change the header for seasonal transitions. A PDF menu is frozen at the moment it was exported. A live menu is a working tool.

3. Reservations without the widget takeover

Every major reservation system — OpenTable, ResDiary, SevenRooms, Resy — has an embeddable widget. Most restaurants embed these and discover that the widget looks like a completely different website has crash-landed in the middle of theirs.

There are three levels of quality here:

Level 1 (bad): the widget embedded as-is, with its own fonts, its own colours, its own layout. The visitor's brain registers the jarring brand shift and trust drops.

Level 2 (OK): the widget embedded with custom CSS overrides to roughly match the brand. Better, but usually still fights the rest of the site.

Level 3 (good): a native-looking reservation flow on the site that submits to the reservation system via API. The visitor never leaves your brand, and the reservation still lands in your existing system.

Level 3 takes a bit more engineering but is worth it. It's the difference between a reservation flow that feels like part of your restaurant and one that feels like a third-party tool you bolted on.

4. Clear answers to the questions every guest asks

Every potential guest has the same handful of questions before deciding to come in:

Where are you? (address, neighbourhood, nearest public transport)
When are you open? (exact hours, with holiday exceptions)
What kind of food is it? (cuisine, style, vibe)
Do you take walk-ins, or do I need to book?
Is it BYO or licensed?
What's the price point? (so they know if it's a $40 or $140 evening)
Is there parking?
Can you accommodate dietary requirements?
Is there a private dining option?

Most restaurant websites hide these in an FAQ or don't address them at all. A good site answers all of them within the first 60 seconds of browsing — usually in the footer, the about page, or a small info block on the homepage.

Getting these questions answered on the site means your host isn't answering the same phone call 30 times a day. It also means guests arrive with accurate expectations, which improves the in-room experience.

5. A story worth telling

The best restaurant websites have a voice. The worst ones sound like every other restaurant website. The difference is usually a single paragraph about who the chef is, why the restaurant exists, and what makes it different.

This is the part that should sound like a specific human. Not "seasonal produce, locally sourced, Mediterranean influences" — that's template text that could describe any restaurant. Something specific: the owner spent four years cooking in a specific kitchen in a specific city and brought a specific dish home. The restaurant exists because they got sick of how much a specific ingredient costs at every other venue. The team is six people and they all come from the same neighbourhood.

Specific beats generic every time. A website with a specific story gets shared on social media, talked about by food writers, and remembered by guests. A generic website disappears.

This is also the place where you pitch your restaurant as a destination rather than a meal. "Come here for a plate of food" is the default. "Come here because it's Tuesday and you deserve an evening" is a reason to book.

The bonus sixth thing: local SEO that actually works

None of the above matters if nobody can find the site. Melbourne restaurants live and die by local search: "best pasta Fitzroy", "restaurant near me open now", "pizza Brunswick". Getting found in these searches requires:

Google Business Profile claimed, filled out, with current photos and hours
Schema markup (specifically Restaurant schema with address, opening hours, menu link, price range, cuisine type)
NAP consistency (name, address, phone) across your site, Google, and Australian directories
Reviews on Google, with replies from the restaurant
A working phone link on mobile (tap-to-call, not a plain text phone number)

These are the things that get you into the Google map pack — the little block of 3 restaurants that shows up above the regular search results. If you're not in the map pack, you're competing against the restaurants that are with one hand tied behind your back.

The scorecard for your restaurant's website

Out of the five (plus the bonus):

6/6: your website is doing its job. The food and service have to do the rest.
3–5/6: you're leaking bookings. The fix is usually a small redesign or a focused content project, not a full rebuild.
0–2/6: your website is actively hurting the restaurant. Most bookings that come through the site are happening despite the website, not because of it. You need a proper rebuild.

What a proper restaurant site costs

For reference: a custom-coded restaurant website in Melbourne in 2026 typically runs $10,000–$18,000 depending on scope. That includes the photography shoot, the menu CMS, the reservation flow integration, the Local SEO work, and a mobile-first build. Less scope gets a cheaper price. More scope (events, private dining, gift cards) adds to it.

A full bad Webflow or Squarespace restaurant site costs roughly $4,000–$7,000. The difference is what you get: a template vs. a custom brand, a worse reservation experience, a menu that's harder to update, and a site that will need to be rebuilt within 2–3 years.

The honest recommendation

If your restaurant is doing more than $500k/year in revenue and the website is a meaningful source of bookings, the custom-coded option pays for itself. If you're under that threshold, a good Squarespace build with real photography and a real menu beats most of the custom work in the middle bracket anyway.

The biggest mistake Melbourne restaurants make is spending $5k on a mediocre site, then wondering why bookings aren't growing. That bracket is the worst value.

If you want us to audit your restaurant's current website against the five-point checklist, book a free audit. We'll run through every item, score it, and send back a written report with the fixes that would move the needle most. Free, keep the audit.

Related reading: Restaurant web design Melbourne — the full breakdown of what restaurant websites need, with links to our Harvest Table design study.