Restaurant website builder for independent restaurants

A restaurant website builder is the tool or service that puts your menu, opening hours, ordering and bookings on your own web address. For an independent restaurant or takeaway in Ireland or the UK, the website has three jobs. It has to appear when someone searches your name or your food nearby. It has to answer the basic questions within seconds on a phone. And it has to turn that visit into an order or a booking.

You can build the site yourself on a general builder, pay an agency, or use a restaurant platform where the website and ordering come together. Each route costs a different amount of money and a different amount of your time. The right one depends on how many orders you want the site to take, how often your menu changes, and who will keep the site correct on a Tuesday afternoon when the price of chicken goes up.

Choosing the ordering system itself is covered in online ordering system for restaurants. The full local search playbook, including Google Business Profile, reviews and citations, is in restaurant SEO. This page covers the website: pages, design, speed, domain, legal pages, cost and launch.

Restaurant website builder requirements

Start from the jobs, not the templates. Every feature on a builder’s list either helps one of these jobs or adds weight to the site.

What to require from any restaurant website builder:

• Mobile layout first. The phone version is the real site. Google uses the mobile version of a site’s content for indexing and ranking, according to its mobile-first indexing guidance.
• Text menu from one source. Prices, modifiers and allergen information, fed from the same menu as your till so the two never disagree.
• Ordering and payments on your domain. The customer should not leave your address to pay.
• Hours with exceptions. Bank holidays, Christmas and a closed Monday set once, shown everywhere.
• Custom domain with HTTPS. Google’s page experience guidance lists secure pages as part of page experience.
• Editable page titles and descriptions. One per page.
• Restaurant structured data. Code that tells search engines your cuisine, address, hours and menu link.
• Image handling. Automatic resizing and compression, so a 5 MB phone photo does not load at full size.
• Cookie controls and a privacy page. A real choice, not a banner with one button.
• Multiple locations. Separate hours, address, ordering and pages per site.
• Customer data export. Your list, in a spreadsheet, whenever you ask.
• No hold on your domain. The domain stays registered to you if you move platform.

Restaurant website pages, page by page

Home page

The first screen on a phone decides whether someone orders or goes back to the app. Put these on it:

• Your name and a plain description of what and where. Example: “Wood-fired pizza and pasta, Stoneybatter, Dublin 7.”
• One photo of your own food, cropped for a phone screen.
• Two buttons at most: Order online, and Book a table or Call.
• Today’s opening hours.

Keep off the first screen: sliders cycling through six photos, autoplaying music, and pop-ups covering the page. Google’s page experience guidance advises against intrusive interstitials.

Below the first screen: best sellers with prices, delivery area, loyalty or referral offer, a short line on who you are, and your address with a map link.

Menu page

• Text, not an image or a PDF. A text menu loads faster, reads properly on a phone and can be updated in seconds.
• Categories as a row of jump links at the top: Starters, Mains, Sides, Drinks.
• Prices next to every item, including sizes and paid extras.
• Dietary labels such as vegetarian or vegan, with a key.
• An allergen information link on the menu page, no more than one click away.
• Photos for the top sellers, not every item.
• Descriptions that say what is in the dish and how big it is.

Keeping one menu across the POS, the website and the apps, with pricing per channel, is covered in restaurant menu management.

Order online page

• On your own domain, not a link out to a marketplace. A website order button that opens Just Eat means you pay marketplace commission on customers who already came to you.
• Pickup and delivery choice first.
• Delivery area, minimum order, delivery fee and any service fee shown before the basket.
• Prep and delivery times that change on busy nights.
• Apple Pay and Google Pay.

Features, checkout design and card fees for the ordering system are in the online ordering system guide.

Location pages

Give every site its own page:

• Page title with cuisine, area and name. Example: “Indian Takeaway in Swords | Spice Road” (a fictional name).
• Full address with Eircode or postcode, and a map link that opens directions.
• Opening hours for that site, with holiday exceptions.
• A tap-to-call phone number for that site.
• Parking, public transport and accessibility notes.
• Delivery area for that site.
• An order button that opens ordering for that site, not a location chooser.

Contact and opening hours

• Hours identical to your Google Business Profile. Different hours on two pages means customers ring to check, or do not come.
• Phone number as a tap-to-call link.
• An email address you read, for catering and complaints.
• Links to your Instagram and Facebook profiles.

Table bookings

• Party size, date and time on one screen.
• Deposit and no-show policy in plain words before the booking is confirmed.
• A phone number for groups above your online limit.
• Confirmation by email or SMS, with a way to cancel.

About page

Two or three short paragraphs. Who cooks, when you opened, what you do differently, where key ingredients come from. Real facts only, and no invented awards or quotes.

Allergen information page

Explain how allergen information is shown on the menu, how customers can ask before ordering, and how you handle requests. The legal requirements for Ireland and the UK are in the legal section below.

Privacy, cookies and terms

• Privacy notice. Who you are, why you collect data, the legal basis, who you share it with, how long you keep it and people’s rights.
• Cookie policy and controls. What each cookie does and a way to accept or refuse non-necessary ones.
• Ordering terms and refund policy. What happens with wrong, missing or late orders.

Restaurant website examples and templates

The five examples below are fictional. Each shows how the same set of pages is arranged differently depending on how the restaurant makes its money.

Example: a pizzeria doing mostly delivery

• Home page leads with Order online and a delivery area check by Eircode or postcode.
• Menu sorted by pizza size first, with bases and toppings as priced modifiers.
• Late-night hours shown in large text, because most orders come after 9pm.
• A meal deal for two and a family deal at the top of the menu.
• Location page for each delivery area the shop serves, each with its own title.

Example: an Indian takeaway with a busy phone line

• Order online first, Call second, because regulars still ring on Friday nights.
• Spice level key at the top of the menu and on each dish.
• Set meals for two and four, with what is in each written out.
• Allergen link on the menu and in the basket.
• A line on the order page explaining that online orders go straight to the kitchen, freeing the phone for people who prefer to call.

Example: a brunch café

• Book a table first on Friday to Sunday, Order for pickup first on weekdays.
• Menu split by time of day: breakfast, brunch, lunch.
• Dog-friendly, buggy access and outdoor seating noted on the location page.
• Coffee pre-order for pickup, with a ready time.

Example: a two-site burger shop

• A location chooser on the first screen, with each site’s hours for today.
• Separate ordering for each site, so a customer in one town never orders from the other.
• One shared menu, with prices that can differ by site.
• A location page per site with its own title, address and phone.

Example: a neighbourhood restaurant with a set menu

• Book a table first, Gift vouchers second.
• This month’s set menu with price per person and dated.
• Private dining and group enquiry form.
• Wine list as text, with prices.

Choosing a template

Test a template with your own content before you commit.

• Load it with your real photos and menu, then run a speed test on mobile.
• Check the menu is text, not a picture of text.
• Check the order button stays visible while scrolling on a phone.
• Look for an hours block that supports holiday exceptions.
• Check there is a page type for each location.
• Delete every demo element: sample reviews, stock photos, placeholder text and fake social feeds.
• Check text contrast on photos. White text on a pale pizza photo is unreadable in sunlight.

Restaurant website builder, agency or restaurant platform

General website builders

A builder gives you the most control over layout for the lowest cash outlay. You pay in hours: building pages, resizing photos, updating hours before every bank holiday, and fixing things when a plugin or add-on changes. Wix’s plans page says most paid plans include a one-year free domain voucher, which cannot be used to renew a domain you already own, so budget for the renewal from year two.

Builders fit a restaurant with a simple menu, low online order volume, and an owner or family member who enjoys the work.

Web agencies

An agency can build a distinctive site for a destination restaurant, with custom photography and design. Ask whether the agency builds ordering and bookings itself or connects separate systems, and who pays for those. Before you sign, get these in writing:

• The domain is registered to your business, with the login held by you.
• The price of hosting and maintenance after launch, per month or per year.
• What each change costs, and how quickly it is done.
• What happens to the site and files if you stop paying.

Agencies fit restaurants where the site sells an experience more than takeaway orders, and where the menu changes rarely.

Restaurant ordering platforms

The provider supplies the website, ordering, payments set-up and often the till. You choose from restaurant-specific layouts rather than designing from scratch. Menu changes on the till reach the website. The trade-off is less design freedom and a contract to read.

Platforms fit takeaways and restaurants where direct orders are a large share of the business and the owner has no spare hours for website upkeep.

Commission-based white-label providers

The provider builds the site and app and takes a share of the orders. Cash outlay at the start is low. Cost grows with every order. Read the minimum term, the notice period and who owns the ordering system before signing. Fee structures in depth are compared on the commission-free online ordering page.

Free widgets

A free widget bolts ordering onto a site you already have. It works for low volume. Check the product’s future before you build on it: GloriaFood’s own home page gives an end-of-life date of 30 April 2027.

Restaurant website design for mobile

Layout

• Order button in reach of a thumb. A sticky button at the bottom of the screen stays visible as the customer scrolls the menu.
• Tap-to-call. The phone number opens the dialler.
• Address opens maps. One tap for directions.
• Readable text. Body text large enough to read without zooming, with strong contrast.
• Menu jump links. Categories at the top so nobody scrolls past 40 starters to find the curries.
• Accordions and tabs for long content. Google’s mobile-first guidance suggests accordions or tabs to save space while keeping the same content as on desktop.
• No content hidden behind taps. The same guidance says not to lazy-load primary content on user interaction, because Google will not load content that needs a swipe, click or typing to appear.

Photos

• Shoot your own food in daylight, instead of using stock images.
• Crop for a phone: square or portrait for dishes, wide shots only for the dining room.
• One strong photo per top seller beats a gallery of fifty.
• Write short alt text for each photo. Example: “Large pepperoni pizza with fresh basil.”

Accessibility in design

• Colour contrast strong enough to read on a phone in sunlight.
• Buttons with words on them, not icons alone.
• Form fields with visible labels, not placeholder text that disappears.
• Menu, ordering and booking usable with a keyboard and a screen reader.
• No information carried by colour alone. Mark vegetarian dishes with a letter or word as well as a green dot.

The law on accessibility in Ireland and the UK is in the legal section below.

Restaurant website speed

Google’s page speed guidance, last updated 10 December 2025, gives three targets for a good experience:

PageSpeed Insights reports two kinds of data. Field data comes from real users over the previous 28 days. Lab data comes from a simulated test run by Lighthouse. A page passes on field data when the 75th percentile of visits meets the good threshold. A new site has no field data yet, so use the lab test at launch and check field data after a month.

Google also says that page experience is not a single signal and that its systems still show the most relevant content even when page experience is weaker. Speed helps customers finish an order. It does not replace relevance.

Speed fixes, in order

1. Photos. Resize to the size they display at, use a modern format such as WebP, and compress. A hero photo straight from a phone can be several megabytes.
2. Video backgrounds. A video is heavier than a photo. If you use one, keep it short, muted and compressed, give it a still image to show first, and test LCP with and without it.
3. Menu as text. A PDF or image menu is slower and harder to read than text.
4. Third-party scripts. Every chat widget, social feed, review widget and extra tracking tag adds load time. Remove the ones nobody uses.
5. Fonts. One or two font families. Each extra weight is another file.
6. Image dimensions. Set width and height for images so the page does not jump as they load, which is what CLS measures.
7. Embedded ordering. An ordering widget inside a slow site waits for both to load. Test the embedded version against a standalone ordering page.
8. Hosting and caching. On a builder or platform this is handled for you. On an agency site, ask who is responsible.

Domain names

.ie domains

The .ie registry, run by weare.ie, sets these rules on its document requirements page:

• Applicants must show a connection with the island of Ireland.
• Irish companies can use express registration by choosing the Company application type and entering their CRO number.
• Accepted documents for companies include a registered business name or CRO number, an Irish VAT number, a tax clearance certificate from Revenue, an Irish or European Union trademark number, a WIPO trademark enforceable in Ireland, or HMRC correspondence showing trading registration.
• Sole traders and partnerships can use the same documents, or give separate evidence of their connection to Ireland and their commercial identity.
• The registry does not sell domains directly. You register through one of its accredited registrars.

.uk and .co.uk domains

UK domains are registered through registrars, which register domain names with Nominet on behalf of their customers. Prices are set by each registrar, so compare the renewal price as well as the first-year offer.

Domain ownership rules

• Registrant. The registrant is your business, not the agency, the platform or a relative who set it up.
• Login. The registrar account uses an email address the business controls.
• Renewal. Auto-renew switched on, with a payment card that will not expire before the renewal date.
• DNS. When you move platform, you change the DNS settings to point at the new provider. The domain stays where it is.
• Redirects. When you rebuild, redirect old page addresses to the matching new pages, so old links and search results still land somewhere useful.
• Email. Keep domain email, such as orders@ or bookings@, on a separate service from the website so a website move does not break email.

Search basics for a restaurant website

The website is one part of local search. The full playbook, including Google Business Profile, reviews, citations and tracking, is in the restaurant SEO guide. The website-side basics:

• Page titles. Google’s title link guidance asks for descriptive, concise titles, unique to each page, without repeated keywords, with the site name at the start or end separated by a delimiter such as a pipe. Example: “Pizza Delivery in Galway | Harbour Slice” (fictional).
• One main heading per page that matches the title’s meaning.
• Restaurant structured data. Google’s local business structured data documentation, last updated 8 September 2026, supports a Restaurant type with properties for cuisine, menu URL, opening hours, price range, address and telephone.
• Google Business Profile links. Google’s help centre says food and drink businesses can list menu items with the menu editor, with changes typically showing within 24 to 48 hours. Businesses outside the US can add Place an order links and choose a preferred provider for pickup or delivery. Point both at your own website.
• Consistent details. The same name, address, phone and hours on the website, Google, the apps and social profiles.
• Location pages. One per site, with that site’s details.
• Sitemap. A sitemap file listing your pages, submitted in Google Search Console.

Legal pages and rules for restaurant websites in Ireland and the UK

Allergen information

• Show allergen information per dish on the menu page, or a clear link to it no more than one click away.
• Repeat the link in the basket before payment.
• Put allergen details on the order at delivery, on a sticker or an enclosed menu.
• Keep the website’s allergen data in the same menu as the till, so a recipe change updates both.

Privacy notice

The Data Protection Commission lists the minimum information to give people: who you are, why you process their data, the legal basis, whether data goes to other organisations, how long you keep it, and their rights to access, correction, erasure, restriction, objection and portability. On a restaurant website, name the ordering platform, payment processor and any marketing or booking tools that receive customer data.

Cookies

In Ireland, the DPC’s guidance, published in April 2020, says consent must be a clear, affirmative act, and that consent is not needed only where a cookie is strictly necessary to provide a service the user has asked for, such as a working basket.

In the UK, Schedule A1 to PECR, in force from 5 February 2026, keeps the consent rule and adds exceptions. One covers analytics used to improve the service, where the information is not shared with others, visitors get clear information about the purpose, and they have a simple, free way to object. Another covers adapting the site’s appearance or functions to a visitor’s preferences, on similar conditions. Advertising cookies still need consent.

A practical set-up for both countries:

• Load only strictly necessary cookies until the visitor chooses.
• Give Accept and Reject equal weight on the first layer.
• Link the cookie policy and a way to change the choice from every page footer.

Accessibility

In Ireland, the CCPC’s guidance defines a microenterprise as fewer than 10 persons with annual turnover or balance sheet total not exceeding €2 million, and says the European Accessibility Act’s requirements do not apply to microenterprises providing services. A group that passes either threshold falls within scope for its e-commerce services. In the UK, section 29 of the Equality Act 2010 places a duty to make reasonable adjustments on service providers. The design checks in the mobile section above are a sensible baseline in both countries.

Prices and refunds

Show delivery fees, minimum orders and any service fee with the menu. In the UK, the CMA’s summary, published 7 January 2026, says fines for breaking the price transparency rules can reach 10% of turnover or £300,000, whichever is greater. Publish a short refund policy for wrong, missing and late orders, and link it at checkout.

Restaurant website cost

Three-year cost example

Example: a takeaway in Ireland planning its website for three years. All figures except Eclyde’s prices are examples to replace with your own quotes. Card fees on direct orders are the same on each route if they all use Stripe, so they are left out.

Route 1: general builder, built by the owner.

• Example builder plan with payments: €30 a month.
• Example restaurant ordering add-on: €30 a month.
• Example domain: €20 a year.
• Owner’s time: example 4 hours a month valued at €20 an hour = €80 a month.
• Three years: (€30 + €30 + €80) × 36 = €5,040, plus €60 for the domain = €5,100.

Route 2: agency site with a separate ordering subscription.

• Example agency build quote: €3,000.
• Example hosting and maintenance: €50 a month.
• Example ordering subscription: €69 a month.
• Example domain: €20 a year.
• Owner’s time: example 1 hour a month at €20 = €20 a month.
• Three years: €3,000 + (€50 + €69 + €20) × 36 = €3,000 + €5,004 = €8,004, plus €60 = €8,064.

Route 3: Eclyde.

• €499 to launch.
• €99 a month for the whole platform.
• Example domain: €20 a year.
• Owner’s time: example 1 hour a month at €20 = €20 a month.
• Three years: €499 + (€99 + €20) × 36 = €499 + €4,284 = €4,783, plus €60 = €4,843.

What the totals leave out matters as much as the totals. Route 3 includes the POS, kitchen display, loyalty and marketing tools, which routes 1 and 2 would buy separately. Route 2 gives the most design freedom. A free builder plan cuts route 1’s plan line to zero but leaves the owner’s time. Change every example figure to your own quotes, and your own hourly value, before deciding.

Launch steps

1. Collect the content. Logo, 10 to 20 photos of your own food and room, the full menu with prices and allergens, hours per site with holiday exceptions, address with Eircode or postcode, phone, delivery area, booking rules and social links.
2. Secure the domain. Registered to the business, login held by you, auto-renew on.
3. Choose the route. Builder, agency or platform, using the cost example above with your own figures.
4. Build the menu and ordering pages first. They take the orders. The home page comes after.
5. Build location, contact, booking and about pages.
6. Connect payments. Set up or connect your Stripe account early. Stripe’s payout documentation says the first payout is typically 7 to 14 days after your first live payment.
7. Write a title and description for every page.
8. Add restaurant structured data, or confirm the builder or platform adds it.
9. Publish the legal pages. Allergen information, privacy notice, cookie policy with working controls, ordering terms and refund policy.
10. Test on real phones. An iPhone and an Android phone, on mobile data. Place an order, book a table, tap the phone number, open the map link, refund a test order.
11. Run PageSpeed Insights on the home, menu and ordering pages. Fix photo sizes and scripts until the lab test is inside Google’s targets.
12. Run basic accessibility checks. Alt text, contrast, keyboard use and form labels.
13. Point the domain. Change the DNS settings, then check that every page loads over HTTPS.
14. Redirect old addresses. Map every page on the old site to its new page.
15. Update Google Business Profile. Website link, menu link or menu editor, and ordering link set as preferred.
16. Update everywhere else. Instagram, Facebook, printed menus, receipts and the shop window.
17. Submit the sitemap in Google Search Console.
18. Review after 28 days. PageSpeed field data, direct orders, bookings and calls.

Launch checklist

• Domain registered to the business, with auto-renew on and the login held by the owner.
• Every page loads over HTTPS.
• Order button visible on every page on a phone.
• Menu published as text, with prices, dietary labels and an allergen link.
• Menu on the website matches the menu on the till.
• Hours match the Google Business Profile, including holidays.
• One location page per site, each with its own title, address, hours and phone.
• Phone number opens the dialler; address opens maps.
• Apple Pay and Google Pay tested on real phones.
• Test order printed or shown in the kitchen and refunded.
• Test booking received and cancelled.
• Largest Contentful Paint within 2.5 seconds in the lab test on mobile.
• No pop-up covering the first screen.
• Photos compressed and sized; no demo content left from the template.
• Privacy notice names every tool that receives customer data.
• Cookie banner gives Accept and Reject equal weight, and blocks non-necessary cookies until a choice is made.
• Refund policy linked at checkout.
• Structured data in place for the restaurant type.
• Old website addresses redirected.
• Sitemap submitted.

Common mistakes with restaurant websites

• A PDF or photo of the menu. Slow on a phone and out of date after the next price change.
• An order button that opens a marketplace. The customer came to you, and you pay commission anyway. More on turning app customers into direct regulars in how to get more direct orders.
• The domain registered by someone else. An agency, a former manager or a relative holds the keys to your address.
• Hours that disagree with Google. Customers ring to check, or arrive to a locked door.
• A heavy first screen. Autoplaying video, a six-photo slider and a pop-up, all before the menu.
• Stock photos. The dish that arrives should look like the photo. Photograph your own food.
• No allergen information online. Required in Ireland before the purchase is concluded, and FSA best practice in the UK.
• One page for two sites. Each location needs its own page, hours and ordering.
• A cookie banner with only an Accept button. Refusing should be as easy as accepting.
• Deleting the old site without redirects. Old links and search results lead to error pages.
• Contact form only. A takeaway customer wants a phone number, not a form.
• No owner access. If only the agency can change a price, prices stay wrong.

Websites on Eclyde

Eclyde gives each restaurant a branded ordering website on its own domain, as part of the whole platform. The website is built for conversion, order value and repeat orders rather than endless configuration, so there is less layout freedom than on a general builder and less to maintain.

• Ordering. Pickup and delivery, Apple Pay and Google Pay at checkout, and address lookup and verification.
• Menu. Menu import from a photo and menu photo enhancement.
• Search. SEO landing pages, a sitemap and a custom domain. A Google Business Profile connection shows your Google reviews in Eclyde, with AI-drafted replies.
• Bookings. Table bookings on the website.
• Customers. You own the customer data: who your customers are, what they order, how often and their favourite items. Points-based loyalty, referral rewards, discount codes, email and SMS campaigns, and a review request after every order.
• Payments. Eclyde does not process cards. Online payments go through your own Stripe account, connected during set-up.
• Set-up. €499 to launch covers menu build, website and ordering set-up, POS and printer configuration, customer import, staff onboarding, testing and go-live support. It is refunded in full within 30 days if Eclyde is not right for your restaurant.
• Monthly. €99 a month for the whole platform, with no Eclyde commission on direct orders and no limits on orders or customers.
• Getting live. Sign up, complete the set-up flow (connect your domain, walk through the dashboard, connect Stripe), install the POS app on an Android tablet, enter the activation code and start taking orders.

If your site’s main job is showing off a tasting menu and a wine list with a custom design, an agency or a general builder gives more design control. If its main job is taking orders and bookings from regulars, compare the three-year costs above. Prices are on the Eclyde pricing page.

Your website’s score

Before you rebuild, measure where the current site stands. The free Eclyde restaurant audit looks at your Google profile and your website and estimates what you pay in marketplace commission each year, in euro. Use it next to PageSpeed Insights and the launch checklist above to decide whether your site needs a few fixes or a rebuild, and which restaurant website builder route fits your numbers.