How to build a restaurant website, in five steps

Choose a design that matches how you serve

Start from one of fifty restaurant templates rather than a blank page. They are not colour swaps of one layout: a tasting-menu room, a neighbourhood trattoria, a late-night noodle counter and a multi-site group need different things from a homepage, and the templates differ in what they put first — the booking, the menu, the room, the order button.

Pick on the strength of one question: what does a stranger need from this page at nine o’clock on a Friday night? If the answer is “a table”, choose a design that leads with booking. If it is “is there anything my daughter can eat”, choose one that leads with the menu. You can change the design later without retyping the content — the content is stored separately from the skin.

Turn your menu into a page instead of typing it

This is the step that usually kills a restaurant website project, because typing out a menu is a job nobody volunteers for and doing it wrong is worse than not doing it. So do not type it. Photograph the menu, or upload the PDF you already send to the printer, and the scan reads the dishes, sections, descriptions and prices into structured fields you can correct.

Structured is the operative word. A PDF menu is a picture of a menu: a phone renders it at a zoom level nobody can read, and a search engine cannot tell a dish from a price from a heading. The same menu as real page content is legible on a phone, searchable, translatable, and available to the systems that answer questions about your restaurant.

Check the details a search engine actually reads

The review step is the one most website tutorials skip, and it is the one that decides whether any of the rest gets found. What a search engine reads is not what a visitor sees: it reads the page title, the description, the address that each page declares as its real one, the structured restaurant data, the internal links, and whether the whole thing is reachable at all.

Work through the details in the review screen the way you would check a delivery note:

• Name, address, phone — exactly as they appear on your door and everywhere else you are listed. Inconsistency here is the most common reason a restaurant loses to a directory in its own local results.
• Opening hours, including the exceptions — the bank holiday you close and the Monday you do not open are the two facts a guest most often gets wrong about you.
• Cuisine, price range and service style — these are what a search engine matches against “Thai near me”, not just your name.
• The menu itself — dish names and descriptions in the words a guest would search, not internal kitchen shorthand.

Edit the site in the words you use with guests

Now write like a restaurant, not like a brochure. The pages that earn direct bookings are specific: the table by the window that is worth asking for, the fact that the kitchen will do the tasting menu without dairy given a day’s notice, where to park, which door to use after nine, what happens if a guest is running twenty minutes late.

Edit blocks directly — text, images, menu sections, booking, hours, contact — and see the change as it will publish. Nothing here needs a developer, and that is the point: the site is only as accurate as how easily you can change it at four in the afternoon. Add your legal pages while you are here; privacy, cookies and terms are generated from your own store details rather than left as a link to nowhere.

Publish, and know what goes out with it

Publishing is free to reach — you build the whole site before you pay for anything. When you do publish, the search-readiness goes out with the site rather than waiting for a second project:

• A sitemap.xml and a robots.txt generated for your site, so crawlers are told what exists and what to ignore.
• Restaurant and LocalBusiness structured data, so your hours, address, cuisine and menu are machine-readable facts rather than sentences to be guessed at.
• Canonical addresses, page titles and descriptions on every page, so no two addresses compete to be the real one.
• Mobile-first output, because the phone in a guest’s hand is the only screen that matters at seven o’clock.
• Managed search-verification setup, so the site can be watched rather than hoped about.
• Search engines pinged the moment you publish, so a price change is not waiting on the next crawl that happens to come along.

Connect your own domain with managed SSL on Growth, and from the same login run direct reservations, live availability, floor plans, deposits and reminders — or add direct online ordering and table QR ordering on Full. TableSpark takes 0% commission on those bookings and orders.