Your menu shouldn’t be a PDF because PDFs are slow to open on a phone, awkward to zoom and read, hard for screen readers, often out of date, and harder for search engines and AI tools to read reliably than a normal web page. A menu built as an ordinary web page loads quickly, reads well on any screen, can be updated in minutes, and sits right next to the booking button. For a restaurant, café or bar, that is usually the single most useful change you can make to the website.
What’s actually wrong with a PDF menu?
A PDF is designed for printing. On a phone, a guest has to wait for the file to download, pinch and zoom across a page designed for A4 or A3, and then find their way back to your site to book. Some phones open the PDF in a separate app, and the guest never comes back.
- Speed. Menu PDFs exported from design software are often large, especially with photos or embedded fonts.
- Readability. Small text and multi-column layouts don’t reflow on a narrow screen.
- Accessibility. Many PDFs aren’t tagged properly, so screen readers can’t read them in order, or at all.
- Freshness. Updating usually means asking whoever has the design file, so old menus stay up for months.
- Search. Search engines can read many PDFs, but a page with clear headings, dish names and prices is easier for them, and for AI answer tools, to understand and show.
Keeping a printable PDF as an extra download is fine. It just shouldn’t be the only version.
How should an online menu be built?
A good HTML menu is plain and structured. Each section, such as starters, mains and desserts, is a heading. Each dish has a name, a short description and a price as real text, not part of an image. Dietary markers such as vegetarian, vegan or gluten-free use a consistent key, explained once at the top.
The most important part is that someone at the venue can update it without a developer. On WordPress, Squarespace, Shopify or most other platforms, that means a simple editable list or structured fields, rather than a designed image. If prices change seasonally, being able to edit one line on a Tuesday afternoon matters more than a beautiful layout.
Separate menus for lunch, dinner, drinks, functions and kids’ meals are often best as tabs or anchor links on one page, so guests don’t have to hunt. If your menu changes daily, say so and show the current version, with the date.
What about allergen information?
Allergens are a safety issue first. The Australia New Zealand Food Standards Code, developed by Food Standards Australia New Zealand (FSANZ), sets out requirements for declaring certain allergens, including for food that isn’t packaged, such as restaurant meals. Broadly, guests must be able to get accurate allergen information about the food you sell. How that applies to your venue, including to online menus and online ordering, is something to confirm with your state or territory food regulator.
On the website, some practical points:
- Allergen information online must match what the kitchen actually does. An out-of-date online menu with wrong allergen details is worse than none.
- Avoid absolute claims like “allergen-free” unless you’re certain, and explain any cross-contact risk.
- Tell guests clearly to speak to staff about allergies when they order or book.
- If your booking form asks about dietary requirements, make sure those notes actually reach the kitchen.
Where should the booking button go?
Everywhere a hungry person might look: the header of every page, next to the menu, and on the contact and opening hours section. Booking platforms such as OpenTable, SevenRooms and Quandoo are common examples, and many offer an embeddable widget or a booking link. What each offers depends on the provider and plan, so check its current options.
Test the booking flow on a phone the way a guest would. Does the widget load quickly, or does it hold up the whole page? Does it work after you’ve scrolled to the menu? Does the confirmation email arrive? Widgets from third parties are a common cause of slow pages, so it can be worth loading them only when a guest taps “Book”.
Should your menu be on Google Business Profile too?
Yes, in most cases. Many guests never reach your website. They see your Google Business Profile in search or Maps, check hours and photos, and decide there. Food businesses can usually add a menu link, and in some cases menu items, to their profile. Point the menu link at your HTML menu page, not a PDF, and keep hours, holiday closures and the booking link up to date. Our guide to local SEO for Australian service businesses covers how the website and profile work together, and getting recommended by AI answers explains why consistent, readable details matter.
Is your restaurant website fast enough?
Restaurant sites tend to be heavy: full-screen video, large food photos, booking widgets, Instagram feeds and several tracking scripts. Guests are often on mobile data, standing on a footpath deciding where to eat. Check your home page and menu page on a phone using Google’s PageSpeed Insights, and look at the three Core Web Vitals, which we explain in Core Web Vitals for business owners.
The usual fixes are compressing and resizing photos, using modern formats such as WebP or AVIF, lazy loading images further down the page, and removing scripts nobody uses. Our article on image optimisation goes into the detail.
Online ordering: your own, or the marketplaces?
Delivery marketplaces such as Uber Eats, DoorDash and Menulog bring you customers you might not otherwise reach, and handle delivery. They charge commission and own the customer relationship. Direct ordering through your own website, using a dedicated ordering platform or your POS system’s online ordering feature, typically costs less per order and gives you the customer’s details, but you have to bring the customers yourself.
Many venues use both: marketplaces for discovery, and a direct ordering link on the website and Google profile for regulars. Compare the actual fees, contracts and payout terms of each option for your venue, as they vary by provider and plan.
A checklist for your restaurant website
- The menu is an HTML page, with a printable PDF as an optional extra.
- Staff can update dishes and prices without a developer.
- Allergen and dietary information is accurate, and guests are told to check with staff.
- The booking button is in the header of every page and works on a phone.
- Opening hours and holiday closures match your Google Business Profile.
- The menu and home pages load quickly on mobile data.
- Online ordering links are easy to find, with your direct option first.
If you only do three things
Turn your menu into a real web page that staff can edit, put a working booking button on every page, and make the menu and home page fast on a phone. Our hospitality and food page has more on the work we do for venues.
Rebuilding a menu as an editable page, or a small venue website around it, is a defined job in our small websites work, and our performance service can speed up a site you already have. Landing pages from $900. Small sites up to five pages typically $2,500–$4,000.
