What a Restaurant Website Needs (and What It Doesn't)

01

The four things

The menu, with prices and a note on common dietary needs. Opening hours that are easy to find and updated for bank holidays. Your address, a map, and a line about parking or nearby stations. And a booking or ordering button that's hard to miss, linked to whatever system you use. Put a phone number people can tap, too.

02

Please don't use a PDF menu

It's the most common mistake we see. A PDF is slow to open on a phone, awkward to read, and invisible to search engines. A menu written as text on the page loads fast, can be found by search, and you can change a price in a minute without redoing a design file.

03

Use your own photos

Real pictures of your food and your room beat stock images by a mile, even if they're not perfect. Show a handful of your best dishes and a sense of the place, and compress them so the page doesn't crawl.

04

Help people find you

Plenty of people find restaurants through the map, so fill in your Google Business Profile properly and keep your name, address and phone number the same everywhere. Ask regulars to leave a review, and reply to them.

05

What you can skip

Music that starts playing by itself. The full history of the building on the homepage. Fancy animations that make the page stutter on an older phone. Nobody's booking a table because of a spinning logo.

Common questions