The single most visited page on any restaurant or bakery website is the menu. It is the reason most people come to your site in the first place. And yet, an enormous number of food businesses in Ontario handle their online menu in the worst possible way: they upload a PDF.
If your menu is a PDF — or worse, a photo of a printed menu — you are actively working against yourself. Here is why, and what to do instead.
Why PDF Menus Are a Problem
PDF menus feel convenient from the restaurant's perspective. You already have the file from your printer, so you just upload it. Done. But from the customer's perspective, the experience is terrible, and the consequences are measurable.
They are unusable on mobile. A PDF designed for an 8.5 x 11 inch page does not work on a 6-inch phone screen. Customers have to pinch, zoom, and scroll sideways to read anything. Most of them will not bother — they will just go to a different restaurant's site where the menu is easy to read.
They are slow to load. A typical PDF menu is 2-5 MB. On a mobile connection, that can take several seconds to download and render. Google's research shows that every additional second of load time increases the probability of a visitor bouncing by 32%[1]. For a menu PDF, you are adding seconds of unnecessary load time.
They are invisible to search engines. Google can technically index text inside PDFs, but it does so poorly and inconsistently. If your menu only exists as a PDF, all those dish names, ingredient descriptions, and cuisine keywords are essentially invisible for SEO purposes. You are missing the easiest content win in restaurant web design.
They are inaccessible. Most PDF menus fail basic accessibility standards. Screen readers cannot reliably parse them, which means visually impaired customers are excluded. Under the AODA[2], larger organizations (50+ employees) are required to provide accessible web content, and the Ontario Human Rights Code creates broader obligations for accessible service. A PDF menu rarely meets accessibility standards.
The Better Approach: HTML Menus
The solution is straightforward: put your menu on a web page as real HTML text. This means your menu items, descriptions, and prices are actual text on the page — not an image, not a download, not embedded in a viewer.
An HTML menu has every advantage a PDF lacks:
- Instant loading — text renders in milliseconds, not seconds
- Perfectly responsive — it adapts to any screen size automatically
- Fully searchable — Google indexes every dish name and description
- Accessible — screen readers can navigate it like any other web content
- Easy to update — change a price or add a seasonal item without redesigning the whole document
How to Structure Your Online Menu
A good online menu is organized the way your customers think, not necessarily the way your kitchen is organized. Here are the principles that work best:
Use clear categories. Group items the way a customer would expect — appetizers, mains, desserts, drinks. For bakeries, this might be breads, pastries, cakes, seasonal specials. Use headings that are scannable at a glance.
Include brief descriptions. You do not need a novel for every dish, but a one-line description that mentions key ingredients helps customers decide and helps search engines understand your content. "Pan-seared Atlantic salmon with roasted root vegetables and dill cream" is better than just "Salmon."
Show prices. This is a contentious topic in the restaurant industry, but the data is clear: customers overwhelmingly prefer to see prices before they visit. Hiding prices does not make people less price-sensitive; it makes them anxious and more likely to choose a competitor who is transparent.
Mark dietary information. If an item is vegetarian, vegan, gluten-free, or contains common allergens, indicate that clearly. This is not just good practice — it is increasingly expected, and it serves customers with genuine dietary needs who are trying to find somewhere safe to eat.
Use photos strategically. You do not need a photo for every item. In fact, too many photos can make a menu page feel cluttered and slow to load. Choose your best five or six dishes and photograph them well. One great photo of a signature dish does more than twenty mediocre ones.
Related: A PDF menu is just one of eight common website mistakes that drive customers away. See the full list.
Handling Seasonal and Rotating Menus
One objection we hear from Ontario restaurants is: "Our menu changes frequently — we can't update the website every time." This is a valid concern, and there are practical solutions.
If your core menu stays relatively stable with seasonal specials rotating in and out, structure your page with a permanent section and a "Seasonal Specials" section that is easy to update. A well-built website makes this a five-minute task, not a production.
If your menu changes daily — as with some farm-to-table restaurants — you have two good options. You can use a simple content management system that lets you update the menu page yourself, or you can keep a "Sample Menu" on the site with a note that the actual menu changes daily. Either approach is better than a PDF.
For bakeries with products that sell out throughout the day, consider listing your full range with a note about availability. Customers understand that the butter tarts might be gone by 2 PM — they just want to know you make them.
Need help building your online menu? We design menu pages that load fast, look great on every device, and help your SEO. Get in touch for a free consultation.
Adding Schema Markup for Search
Once your menu is in HTML, you can take it one step further with structured data markup. Schema.org provides a Menu vocabulary[3] that lets you tag your menu items, prices, and categories in a way search engines can parse directly.
This can result in rich search results — where Google displays your menu items, prices, or dietary options directly in the search listing. It is a competitive advantage that very few independent restaurants in Ontario are using, which means there is a real opportunity to stand out.
What About Third-Party Menu Platforms?
Services like Popmenu, BentoBox, and others offer to manage your online menu across multiple platforms. These can be useful for keeping your menu consistent on Google, Yelp, and delivery apps, but they should supplement your own website menu, not replace it.
The menu on your website should be the authoritative version — the one you control completely, that loads the fastest, and that gives the best experience. Third-party platforms can syndicate a version of it, but your site is the source of truth. A PDF menu is just one of many common restaurant website mistakes that cost you customers — and it is the easiest to fix.
Getting Started
If your restaurant or bakery is still using a PDF menu, switching to an HTML menu is one of the highest-impact improvements you can make to your website. It improves the customer experience, boosts your search visibility, meets accessibility requirements, and makes your site faster.
We build menu pages for restaurants and bakeries across Ontario as part of our web design service. All our sites are built and hosted on Canadian servers — your data never leaves the country. If you are still weighing whether your restaurant needs its own site in the first place, our article on whether restaurants need websites lays out the case. And if you are not sure where to start, reach out for a free consultation and we will take a look at your current setup and show you what a proper online menu could look like for your business.