What should a restaurant website include?

What are the absolute must-haves on a restaurant website?

Before getting into the finer details, here is the short list of things that if missing will cost you real customers. A visitor who cannot find your hours, cannot read your menu on their phone, or cannot figure out where you are parked will leave. These are not nice-to-haves.

Everything else on this page adds value, but these six items are the ones that determine whether a restaurant website actually does its job. If yours is missing any of them, fix that before anything else.

Should the menu be a webpage or a PDF?

A real webpage, every time. This is one of the most common mistakes restaurant owners make, and it hurts in two separate ways at once.

PDF menus do not display reliably on phones. They open in a separate viewer, require pinching and zooming, and frequently show the wrong file if someone uploaded a new menu six months ago and forgot to replace the old one. Hungry people on phones give up fast.

The second problem is search. Google cannot index a PDF menu the way it can a webpage. When someone searches for "wood-fired pizza in Coral Gables" or "gluten-free brunch Miami," your individual dish names and descriptions can appear in results if they are on a real HTML page. They will not if they are locked in a PDF. An HTML menu is also faster to load, easier to update, and works properly with screen readers.

If you have seasonal menus or frequent specials, the solution is a simple menu page with clearly dated sections, not a new PDF every week.

How should hours, address, and contact information be presented?

This information needs to be impossible to miss and consistent everywhere it appears. Inconsistency between your website, your Google Business Profile, and third-party listing sites is one of the most common causes of poor local search rankings. Google cross-references these signals constantly.

• Hours: Display them on the homepage and on a dedicated contact or location page. If your hours change for holidays or private events, update them in both places and on your Google Business Profile at the same time.
• Address: Mark it up with structured data (Schema.org LocalBusiness) so Google can read it unambiguously. Link directly to Google Maps so visitors can tap and navigate without copying and pasting.
• Phone number: Make it a tel: link so mobile visitors can call with one tap. Burying a phone number in an image or a footer-only text block costs you real calls.
• Parking and transit notes: If parking is tricky or there is a nearby transit stop, a one-sentence note prevents the friction of a last-minute "where do I park" search that might send someone elsewhere.

Does a restaurant website need an online booking or ordering widget?

For most full-service restaurants, yes. For counter-service or takeout-heavy concepts, an online ordering option matters more than reservations. The key is removing as much friction as possible between a visitor deciding they want to come and actually committing.

A booking widget connected to a service like OpenTable, Resy, or a simpler direct booking tool lets guests reserve a table at midnight, on a Sunday, without calling. That alone captures a meaningful share of business that used to require a phone call during staffed hours.

For restaurants that do takeout or delivery, an embedded ordering widget or a clearly labeled link to your preferred ordering platform keeps the transaction as close to your own site as possible, which matters for both the guest experience and for reducing the cut third-party platforms take when orders come through their own apps directly.

A booking widget is a $300 add-on at FineWright, integrated into the rest of your custom build. It is not a templated plug-and-play: it is wired into your site's design so it does not look like a foreign object dropped onto the page.

What kind of photos does a restaurant website need?

You need three categories. Food photos, interior photos, and at least one exterior shot. Each one does a different job.

Food photos are the most important. They are what convert a browser into a reservation. The bar here is not professional food photography, though that is the best option when the budget allows. The bar is: does this photo make someone want to eat that dish right now? Natural light, a clean background, and a phone camera with a steady hand can clear that bar. Dark, blurry, or heavily filtered photos do not. If your current photos are not making the food look good, either retake them or leave those dishes unphoto-graphed rather than use a bad shot.

Interior photos set expectations for atmosphere. A first-time visitor wants to know if the space is casual or formal, loud or quiet, suited for a date or for a group. One or two well-lit interior shots answer those questions before the visit and reduce the friction of the unknown.

An exterior photo is practical: guests recognize the building when they arrive. For restaurants in mixed-use buildings or areas with confusing street numbers, this removes a small but real source of frustration.

Avoid stock food photography. Diners are good at recognizing it, and it erodes the trust that real photos build. Your actual food, photographed honestly, is always better than a generic image of a dish that is not yours.

How does local SEO work for a restaurant website?

Local SEO for restaurants is about showing up when someone nearby searches for what you serve. That search might be "Thai food near me," "brunch Miami Beach," or "private dining room for 20 in Wynwood." The people doing those searches are high intent: they are looking to spend money soon.

The main levers are:

• Google Business Profile. This is free and is the single highest-leverage thing a restaurant can do for local visibility. Fill every field, add photos regularly, and respond to reviews. Your website and your profile should have identical name, address, and phone number information.
• Structured data on your website. Adding Schema.org markup for Restaurant, with your cuisine type, hours, address, and menu URL, tells Google exactly what your site is about without guessing.
• Location and cuisine in page titles and headings. A page titled "Dinner reservations" is weaker than one that reads "Italian restaurant in Little Havana, Miami." Your city, neighborhood, and cuisine type belong in the copy on the page, naturally, not stuffed awkwardly.
• Reviews linked or quoted on-site. Reviews build trust with visitors and reinforce your legitimacy to search engines. A simple testimonial section with names and star ratings, or a widget pulling from Google reviews, does both jobs.
• Consistent citations. Yelp, TripAdvisor, OpenTable, and local directories should all show the same name, address, and phone number as your website. Inconsistency across these signals genuinely hurts local rankings.

The local SEO approach for a restaurant overlaps with what other local service businesses do. If you are curious how this applies across industries, the principles are similar to what we cover for a great roofing company website and what a plumber's website should include, though the specific trust signals and conversion actions are very different.

What trust signals belong on a restaurant website?

A trust signal is anything that reduces a visitor's uncertainty about whether your restaurant is worth their time and money. For restaurants specifically, the most effective trust signals are:

• Reviews and ratings. Even a handful of quoted reviews with names and star ratings on the homepage tell a visitor other people have been here and had a good time. A live Google review widget updates automatically and adds social proof without extra maintenance.
• Press mentions or awards. If a local publication has covered you, or if you have won a local dining award, a short "as featured in" line with the outlet's name carries real weight. Keep it factual: just the name and context, not invented superlatives.
• Team or chef story. People eat at restaurants partly for the experience, and knowing who is behind the kitchen creates a connection. A short paragraph about the chef or the origin story of the restaurant is not filler; it is conversion content.
• Clear cancellation and reservation policy. Ambiguity about whether a reservation can be cancelled, or whether there is a deposit, creates hesitation. Stating it plainly removes that hesitation.
• Accessibility information. Noting that the space is wheelchair accessible, or that you accommodate common dietary restrictions, is both practically useful and a trust signal that you have thought about your guests.

What pages does a restaurant website actually need?

The page count depends on the size and complexity of the restaurant, but here is a practical map for a typical sit-down restaurant:

A single-page site can compress the essential items into one scrollable layout and works well for simpler concepts or ghost kitchens. A multi-page site gives each section room to breathe and makes it easier for Google to rank individual pages for specific searches. The right choice depends on how much you have to say and how many distinct search queries you want to capture. Our guide to turning visitors into customers covers the conversion architecture side of this decision in more detail.

What are the most common mistakes on restaurant websites?

These show up on a large share of restaurant sites and each one loses customers directly.

• Outdated menus. A menu with items that are no longer served, old prices, or dishes that have changed creates a bad experience at the table and erodes trust online. Treating the menu page as a living document, not a set-and-forget file, is one of the most important maintenance habits a restaurant can build.
• Autoplay music or video. It was a trend for restaurant sites in the early 2010s and it still appears. It startles visitors who are browsing in public or at work, and it is one of the fastest ways to get someone to close a tab. Do not do it.
• No mobile optimization. The majority of restaurant searches happen on phones. A site that requires pinching and zooming to read the menu, or where the reservation button is too small to tap, is losing bookings every single day.
• Slow load times from heavy image files. Beautiful food photos are essential, but uploading raw camera files at full resolution without compression can push page weight to several megabytes. Images should be compressed and served in modern formats so the page loads in under two seconds on a mobile connection.
• No clear call to action above the fold. When someone lands on your homepage, the most important action is usually making a reservation or viewing the menu. If neither of those is immediately visible without scrolling, you are adding friction where there should be none.
• Using a third-party link-in-bio page as the main site. Some restaurants rely entirely on an Instagram bio link to a Linktree or similar page. That works for social traffic but does nothing for Google search, gives you no control over your brand, and provides no room for a real menu or booking experience.

How much does a restaurant website cost?

A single-page restaurant website, covering the essentials in one clean scrollable layout, starts at $599 at FineWright. A full multi-page site with a dedicated menu page, about section, gallery, location page, and contact form starts at $1,499. Adding a booking or scheduling widget is a $300 add-on. Online ordering integrations and more complex builds are quoted individually.

Every build is custom: no templates, no page builders, no bloated WordPress installs that need constant plugin patching. The starting price becomes a fixed quote once scope is confirmed, and you own everything we build. See the full breakdown on the FineWright pricing page.

After launch, care plans start at $49 per month and cover hosting, backups, security, and monthly edits. For a restaurant where the menu changes seasonally and hours shift around holidays, having someone on hand for small updates without negotiating a new project each time is practically useful.

Frequently asked questions

Does a restaurant actually need its own website if it already has a Google Business Profile?

Yes. A Google Business Profile is free and essential, but it cannot host your full menu, tell your story, take reservations, or control how your brand looks. Your own website is the only place online where you have full control over the experience. The two work together: the profile drives discovery, the website closes the visit.

Should a restaurant menu be a PDF or a real webpage?

A real webpage, every time. PDF menus do not display well on phones, they cannot be indexed properly by Google, and they break when you update them and forget to re-upload. An HTML menu page is faster, mobile-friendly, and shows up in search results for dishes people are looking for.

How important is page speed for a restaurant website?

Very important. Restaurant visitors are almost always on a phone, often deciding where to eat right now. A site that takes more than two or three seconds to load loses a large share of those visitors before they even see a menu. Speed is also a Google ranking factor, which affects whether you show up for searches like "restaurant near me."

Do I need a booking widget, or is a phone number enough?

For most full-service restaurants, an online booking option significantly reduces friction. Many diners, especially younger ones, prefer not to call. A booking widget connected to a service like OpenTable or Resy can handle reservations around the clock. A click-to-call phone number should always be present too, as some guests still prefer it.

What photos does a restaurant website actually need?

You need three types: food photos that make dishes look genuinely appetizing, interior photos that set expectations for the atmosphere, and at minimum one exterior photo so guests can recognize the building when they arrive. Phone photos taken in good natural light are acceptable if professional photography is not in the budget yet, but blurry or dark shots do more harm than good.

How much does a restaurant website cost?

A single-page restaurant website starts at $599 at FineWright. A multi-page site with a full menu, about section, gallery, and contact page starts at $1,499. A booking widget is a $300 add-on. The exact price depends on scope, and FineWright provides a fixed quote before any work begins.

Keep reading: what makes a great roofing company website, what a plumber's website should include, and turning visitors into customers.