Restaurant website guide: what yours must include (and what it should cost) in 2026
"We already have a Google listing and an Instagram account. Do we really need a website?" It is probably the digital question restaurant owners ask most often, and it is a fair one: between the agency quote that runs into thousands and the cousin who offers to "knock something together on WordPress", it is hard to see clearly.
This guide answers without hedging: yes, a website earns its keep, but probably not the website someone is trying to sell you. An effective restaurant website is small, current, and built for exactly one job: turning a hungry person scrolling on their phone into a guest sitting at your table.
In short:
- your Google listing gets you found; your website convinces and converts. They complement each other, they do not replace each other;
- a good restaurant website fits in a handful of pages: an up-to-date menu, hours, photos, directions, and a way to book;
- realistic budget: from a few dollars (or pounds) a month if you do it yourself to a few thousand with an agency;
- the three mistakes that cost you guests: a PDF-only menu, a site nobody updates, and no visible booking button;
- you do not need to rebuild your site to take online bookings: a simple link or button is enough.
Do you really need a website when you already have a Google listing?
Let's be honest: for getting found, your Google Business Profile already does most of the heavy lifting. When someone searches "Italian restaurant" plus your city or neighborhood, the map pack and local listings show up first, not websites.
But being found is only half the journey. Once the listing is open, would-be guests want to picture the evening: the full menu with prices, the feel of the dining room, whether there is a vegetarian option, whether you take groups, how to book a table (or make a reservation, depending on which side of the Atlantic you are on). A survey by the marketing agency MGH, reported by Restaurant Dive, puts numbers on it: 77% of diners check a restaurant's website before dining in or ordering, and nearly 70% have been discouraged from visiting because of that website, with hard-to-use navigation and dated design leading the complaints. The same survey found the menu is the single strongest factor in the decision.
In other words, the question is not "Google listing or website" but "what happens after the click". The listing captures attention; the website closes. And the website is the only online space you fully control: Google can redesign its listings tomorrow, your site remains your storefront.
One more practical point: your Google listing has a "website" field. Leave it empty and the click goes nowhere, or worse, to a third-party platform that charges you a commission per cover. With a site of your own, even a minimal one, you decide where that click lands, and you can add commission-free online booking to it without paying a cent per seated guest.
Verdict: yes to a website, but a simple one. Five well-kept pages beat fifty abandoned ones.
What a restaurant website must include (and nothing more)
A visitor lands on your site with a precise mental checklist, roughly in this order: what do you serve, at what price, are you open, how do I book, how do I get there. Your site must answer all five in under a minute, on a phone.
The menu, current and readable on a phone
This is THE page people come for; the MGH survey cited above found menu content is the top driver of the decision to visit. Three rules:
- publish the menu as text, directly in the page (HTML), not only as a PDF (more on this in the mistakes section);
- show prices: a menu without prices scares people off, because everyone assumes the worst;
- keep it dated and seasonal: nothing erodes trust like a "spring menu" read in November.

Hours and practical information
Opening hours by day, holiday closures, a clickable address that opens directions, a clickable phone number that starts the call, a note about parking or the nearest station. These are details, but they are exactly what prevents the 7 pm "are you open tonight?" call in the middle of service.
Crucially, your hours must be identical everywhere: website, Google listing, social profiles. One inconsistency and guests start doubting everything else.
A way to book, visible immediately
A "Book a table" or "Reservations" button in the navigation, visible without scrolling. Booking is the action you want to trigger, so it should never be more than one click away. A generic contact form that nobody checks is not a booking channel.
If you already take bookings online, the button simply points to your booking page. If you still take them only by phone, display the number prominently, but know that part of your audience will never call: a phone cannot take a two-tap booking at 11 pm.
Photos that make people hungry, and that are yours
A few shots of your dishes, the dining room, and the patio or terrace are enough. Avoid stock photos: diners spot them, and the gap between the photos and reality gets paid back in negative reviews. A series of smartphone photos taken in good daylight beats a generic stock gallery.
What you can skip
A blog you will never feed, an embedded guestbook, an intro animation, a newsletter module with no plan behind it. Every element you add is an element you must maintain. When in doubt, cut.
Accessibility is not optional, especially in the United States
An often-overlooked point that has real legal teeth. The US Department of Justice states in its web accessibility guidance that Title III of the ADA, which prohibits discrimination by businesses open to the public, explicitly including food and drink establishments, applies to their websites. The best-known case involved a restaurant business: a blind customer sued Domino's Pizza because he could not order through its website with a screen reader, the Ninth Circuit ruled the ADA applied, and in 2019 the Supreme Court declined to hear Domino's appeal, letting that ruling stand.
This is not theoretical risk. UsableNet's mid-year 2025 report counted 2,019 digital accessibility lawsuits filed in the first half of 2025 alone, with food service the second most targeted industry at 18% of filings. In the UK, the Equality Act 2010 prohibits service providers from discriminating against disabled people, which is generally understood to cover online services too.
The good news: for a simple restaurant site, the basics go a long way, and they overlap almost entirely with good practice anyway. A menu in real HTML text (a screen reader cannot read a scanned PDF), meaningful descriptions on images, sufficient text contrast, buttons and links that can be used with a keyboard. Modern website builders handle much of this by default; a text menu instead of a PDF is the single biggest step you can take yourself.
What a restaurant website costs: the honest options
This is where guides contradict each other most, usually because they are written by someone selling one of the options. Here are the realistic orders of magnitude, with their honest trade-offs.
| Option | Realistic budget | Best for |
|---|---|---|
| Website builder (Wix, Squarespace...) | roughly $15 to $40 per month depending on the plan | doing it yourself, clean result fast |
| WordPress + shared hosting | domain around $10 to $15 per year + hosting a few dollars per month | comfortable with tech, wants full control |
| Local freelancer or agency | from a few hundred to several thousand dollars or pounds, plus maintenance | delegating everything |
| Site included in a hospitality tool | included or an add-on, depending on the tool | fewest tools to manage |
Website builders: Wix, Squarespace and friends
The principle: pick a template, drop in your text and photos, and the result is live the same day, hosting included. Plans that let you connect your own domain typically run somewhere between $15 and $40 per month; the exact tiers change regularly, so check the current pricing pages of Wix and Squarespace directly.
For most independent restaurants this is the most sensible option today: no technical skills required, professional-looking output, and you can update the menu from your phone in five minutes. The trade-off: you are renting the platform, and the monthly cost runs forever.
WordPress on shared hosting: the most flexible, the most demanding
WordPress, the open-source software, costs nothing. You pay for the domain name, usually $10 to $15 a year, and for hosting, which starts at a few dollars a month on shared plans from most mainstream hosts.
On paper it is unbeatable. In practice you have to install it, choose a theme, apply security updates, and debug it yourself when a plugin breaks the layout. If none of that appeals to you, the time spent will quickly outweigh the money saved. It is a good option if you are comfortable, or if a genuinely committed tech-savvy friend is in it for the long haul.
The local freelancer or agency: delegate, but set the terms
A freelancer or a small agency delivers a custom site. Prices vary enormously by region and ambition: from a few hundred dollars or pounds for a simple brochure site from an independent to several thousand from an agency, plus monthly or yearly maintenance.
Two questions to ask before signing; they eliminate most bad surprises:
- "Who updates the menu, and what does each update cost?" If the answer is "email us and we bill you", walk away: your menu will change faster than your budget.
- "Is the domain name registered in my name?" The domain must belong to you. A provider who keeps it in their own name holds you captive.
Sites bundled with hospitality tools
Some hospitality tools (booking, online ordering, takeout or takeaway, click and collect) include a mini-site or a public page. The upside: one interface, no duplicated information. The limit: the design is standardized and you depend entirely on the vendor, including for your visibility.
Let's be honest about our own case: ViteUneTable does not build websites. We provide the booking layer, a branded online booking page that any website can point to, whatever tool built it. That is deliberate: your website belongs to you; our job is to make it capable of taking bookings.
The classic mistakes that drive guests away
They repeat from site to site, and each one can be fixed in an evening.
The scanned PDF menu
Mistake number one. A PDF, and worst of all a scan of the paper menu, forces the mobile visitor to download a file, then pinch and zoom through a blurry image. Many give up before reading the first appetizer (or starter). A PDF is also poorly read by Google and unusable for blind guests relying on screen readers, which, as covered above, is a legal exposure in the US, not just a UX flaw.
The fix is simple: retype the menu as text on a page of the site. Keep the PDF as an optional extra download if you like, never as the only way to see the menu.
The site nobody updates
The menu from two years ago, the hours from before the renovation, the "Happy holidays" banner in May. An outdated site is worse than no site: it actively gives wrong information, and every error ends with a disappointed guest in front of a closed door.
Hence the rule stated earlier: only publish what you are certain you will maintain. A one-page site that is accurate beats a ten-page site that is stale.
The overloaded showcase site stuck in 2010
Autoplay music, an intro animation, carousels sliding on their own. These "wow effect" sites of another era load slowly, work badly under a thumb, and bury the useful information. Guests do not come to admire an animation; they come to read your menu.
No mobile version
Most of your visitors arrive from a phone, often on the sidewalk or the sofa, at the exact moment the decision is made. A site that is unreadable on mobile, with tiny text, untappable buttons, and cut-off tables, is a site that serves no one. Every recent website builder produces mobile-friendly sites by default; if yours does not, that is the sign it is time to rebuild.
The hidden or missing booking option
A guest convinced by your menu should be able to book on the spot, while the craving is there. If they have to hunt for a phone number, make a mental note to call tomorrow, or fill in a form with no guaranteed answer, a share of them evaporates. A prominent booking button on every page is the highest-return improvement on your entire site.
Local SEO basics: get found without giving up your evenings
You do not need an SEO agency to cover the essentials. Four actions are enough for an independent restaurant:
- Link your Google listing and your website both ways: the listing's "website" field points to your site, and your site shows the same name, address, and phone number, character for character. That consistency is a baseline trust signal for Google.
- Name things the way your guests search: your homepage title should contain your cuisine and your city ("Trattoria Bella, Italian restaurant in Portland"), not just "Home". That is the query people actually type.
- Take care of your reviews: Google reviews weigh heavily in local ranking and in the guest's decision. We cover this in a dedicated guide on getting more Google reviews for your restaurant.
- Stay fast and light: compressed photos, no autoplay video. A site that takes eight seconds to load on a phone has already lost its visitor.
With that foundation in place, the best SEO is consistency: accurate hours, a current menu, and reviews you actually answer.
Add online booking to your website without rebuilding it
Good news to finish: whatever site you have or choose, adding online booking requires neither a redesign nor a developer.
Here is how it works with ViteUneTable: your restaurant gets its own online booking page. On your website, you add a "Book a table" button or link pointing to that page. It works on Wix, Squarespace, WordPress, an agency-built site, or even a single landing page: anywhere you can place a link, you can take bookings.
Concretely:
- the free plan is enough to start: online bookings with 0% commission on your covers, no time limit, no commitment;
- guests book in a couple of taps at any hour and automatically receive a confirmation email;
- every booking lands in one place, the ones from your site alongside the ones you take by phone;
- the same link also goes on your Google listing and your social profiles, and the Standard pack, at €29 excl. VAT per month, goes further by activating the Reserve with Google button directly on your listing.
Your website tells the story of your cooking; the booking button turns readers into covers. Together they complete the chain: found on Google, convinced by the site, seated at your table.
Frequently asked questions
Can a restaurant get by without a website?
Technically yes: a well-maintained Google listing covers the survival minimum of visibility. But 77% of diners check a restaurant's website before visiting, according to the MGH survey reported by Restaurant Dive, and nearly 70% have been put off by a bad one. Without a site, you hand that decisive moment to your listing, your reviews, or third-party platforms. A simple site of a few pages captures that audience for a very modest cost.
How much does a restaurant website cost?
Roughly $15 to $40 per month with a website builder like Wix or Squarespace, a few dollars per month in shared hosting if you set up WordPress yourself (plus the domain, around $10 to $15 per year), and from a few hundred to several thousand dollars or pounds with a freelancer or agency, maintenance on top. The right budget is the one that lets you update the menu yourself, for free.
Can I build my restaurant's website myself?
Yes, and for an independent it is often the best choice. Today's website builders require about the same skill level as posting on social media: pick a template, replace the text and photos. Plan an evening or two for setup, then a few minutes per menu update.
Is a PDF menu on my website really a problem?
Yes, especially on mobile: a download, zooming, blurry text, and content Google reads poorly. It is also unusable with screen readers, which matters legally in the US since the Department of Justice considers restaurant websites covered by the ADA. The menu should exist as text on a page of the site, with prices. Keep a PDF as an optional download if you want, never as the only access to the menu.
Does the ADA really apply to restaurant websites?
In the United States, yes. The Department of Justice's guidance states that Title III applies to the websites of businesses open to the public, including food and drink establishments, and the Supreme Court let stand a ruling to that effect in the Domino's Pizza case in 2019. Practical basics: a text menu rather than a scanned PDF, image descriptions, readable contrast, and keyboard-friendly buttons.
How do I add a booking button on a Wix, Squarespace, or WordPress site?
Create a button or link in your navigation and point it to your online booking page. With ViteUneTable, that page is included in the free plan: copy its address, paste it into the button, and your site takes bookings at 0% commission, with no technical changes at all.
Also worth reading
Walk-ins vs reservations: finding the right mix for your restaurant
All reservations, walk-in only, or a deliberate mix of both? Each model wins in a different restaurant. Here is how to choose yours, how many tables to hold back, and why overbooking is a trap for restaurants even though it works for airlines.
VAT on restaurant food in the UK: rates, takeaway rules and worked examples
Eat-in at 20%, cold takeaway at 0%, and a dozen traps in between. A plain-English guide to VAT for UK restaurants, with worked examples in pounds.
Valentine's Day restaurant reservations: the playbook for your biggest nights of the year
February 14 does not get a do-over: demand lands on a single night. Here is the complete method for peak dates, from the set menu to the D-30 run sheet, including protection against the year's worst no-shows.