·Adiamo Studio
How to put your menu on your restaurant website
Choose the page, a PDF, or Google’s menu as the place guests actually read — then structure sections, prices, signatures, and allergens so a phone scan leads to a booking.
Answer first
Put signature dishes on the page itself, with a price next to each name, and keep one PDF as a backup for people who want the full carte. Do not make a scanned PDF the only menu. Point your Google Business Profile menu link at the same page, update the page, the PDF, and the Google menu in the same week the carte changes, and state allergens in plain words the floor can stand behind.
Guests open your site to answer one question before they book: what do you actually serve, and what does it cost? A beautiful homepage that hides the menu behind a PDF, or a PDF that is a photo of last season’s print, fails that question on a phone.
This guide is about the menu as a booking tool, not as graphic design. It covers where the menu should live, what to show first, how prices and allergens should read, and how to keep the website, the PDF, and Google from drifting apart. The pass/fail version of the same idea sits in the restaurant website checklist.
How a page menu differs from a PDF or Google’s menu
You will end up with more than one copy. That is fine if each copy has a job. The page is what a guest scans before booking. The PDF is the full carte for people who ask for it. Google’s menu editor is what shows inside Maps. Trouble starts when those three disagree, or when the PDF is the only thing you maintain.
| On your website | Google menu editor | ||
|---|---|---|---|
| Best for | A phone scan before booking | The full carte, on request | Guests already on Maps |
| Who controls the layout | You | You, until the file is stale | Google’s menu module |
| Phone reading | Normal text, no zoom | Often needs pinch-zoom | Short items in Google’s UI |
| Prices | Next to the dish name | Wherever the designer put them | A field on each item |
| How fast a change shows | When you publish | When you replace the file | Google says updates can take 24–48 hours |
| A link you can share | Yes — the page URL | Yes — if the file URL stays stable | No — it lives inside the listing |
Google documents the menu editor, including sections, prices, and a separate menu URL, in About the menu editor. Set that menu URL to your website menu, not to a file you will rename next month.
Page
Signatures, prices, one scan
Full carte, clearly a backup
Same dishes, same prices
When the page should lead, and when a PDF is enough
A full HTML carte of eighty dishes is not the goal for a one-page restaurant site. Guests deciding whether to book do not need every side. They need the dishes that define the room, a sense of price, and a way to see the rest if they want it.
Lead with the page
- Most bookings are decided on a phone.
- You have a short set of signatures worth naming.
- The carte changes often enough that a scanned PDF goes stale.
- You want the menu and the Reserve button on the same screen.
A PDF can stay primary
- The menu is a fixed tasting menu and the page already states the price.
- You change the print once a season and replace the file the same day.
- Guests book through a venue that already explains the menu, such as a hotel desk.
- You still put the price and the format (tasting, à la carte) in text on the page.
How to build the menu guests will actually read
Signatures
Six to ten dishes on the page
Price
Next to the name, not in a footnote
Allergens
Plain words, not a legend of icons only
Full carte
PDF and Google point at the same list
Reserve
One action, still visible
- 1
Choose the dishes that earn the booking
List the plates people mention in reviews and the ones the floor is proud to sell. Six to ten is enough on the page. The rest can live in the PDF. If a review names a dish, that dish is a candidate — the method is the same as in how to turn Google reviews into a restaurant website.
- 2
Put the price on the same line as the name
Guests should not hunt. A range is honest when the plate varies (“market price”, “from €18”). A missing price reads as a surprise at the table, and surprises cost bookings.
- 3
Write one line, not a paragraph
Ingredients and preparation. Cut adjectives. People scan; they do not read a menu like an essay. Nielsen Norman Group’s research on how users read on the web is the general point: most of the page is skimmed.
- 4
Name allergens in words the kitchen can defend
In the EU, food served to guests — including non-prepacked plates — must carry allergen information. Regulation (EU) No 1169/2011 sets the list; member states decide the means for food that is not prepacked. A website is a useful place to state it, and it does not replace what service must be able to answer at the table. Use words (“contains wheat, milk, almonds”), not only a row of icons nobody has the key for. How to follow that list is in how to show allergens on your menu. The legal text is Regulation 1169/2011.
- 5
Point every copy at one carte
Publish the page. Upload or replace the PDF at a stable URL. In Google Business Profile, set the menu link to the page and update the editor so Maps does not show last winter’s prices. If Maps is still your main discovery surface, read why your Google Maps listing is not enough for how the two should stay in step.
- 6
Leave the Reserve button in charge
The menu is support for the booking, not a second homepage. One reservation path — the channel the floor answers — stays the primary action, as in WhatsApp and email reservations that actually get answered.
What each field is for
| Field | On the page | Skip it when |
|---|---|---|
| Dish name | Always. The name the floor uses. | You only have internal recipe codes |
| One-line description | When the name is not self-explanatory | The name already says the dish |
| Price | Always, or an honest range | Never — a missing price is not a strategy |
| Section | Starters, mains, dessert, drinks — few sections | You have twelve sections for twelve dishes |
| Allergens | The ones that are actually in the dish | You are guessing, or the recipe changes daily without a check |
| Photo | One strong photo per signature, if you have it | The photo is dark, old, or a different plating |
| Story paragraph | Rarely. One sentence on the section is enough | Every dish has a origin story |
If you add structured data, Menu and MenuItem are the vocabulary for a menu, its sections, and its dishes. Use them so the page describes the same carte in a consistent way. They are not a promise of a special search result.
When a website menu fails
- The only menu is a scanned PDF. Phone guests pinch, give up, and book somewhere that showed a price. If that file is also what the table code opens, the fix is in what your menu QR code should open.
- The page, the PDF, and Google disagree. Two prices for one dish is worse than a short menu.
- Allergen icons with no key. A guest with an allergy will call anyway — or will not come.
- Every dish, no emphasis. A wall of text hides the plates that should earn the booking.
- Last season’s specials. A menu that names a dish you no longer serve trains guests not to trust the rest.
- The menu replaces the booking path. Three buttons — Menu, Call, Book — and no primary action.
What a website menu does not do
It does not replace the printed carte on the table, the daily verbal specials, or the legal allergen answer your service is required to give in person. It does not need a photo of every plate before you publish. It does not need to list eighty dishes to be useful. And it does not, by itself, make Google show your menu differently — consistency with the listing is the point, not a formatting trick.
Frequently asked questions
Should I put the full menu on the website or only highlights?
Highlights on the page, full carte in a PDF. Guests booking on a phone need the dishes and prices that define you. Offer the complete list as a file with a stable link.
Is a PDF menu bad for SEO?
A PDF is a poor primary menu because many phone users will not zoom it, and a scan is hard to keep current. Search is a secondary concern. Put real dish names and prices in the page text, and keep the PDF as a backup.
Do I have to match the Google menu exactly?
Prices, dish names, and what you no longer serve should match. Google’s module will not carry your tone or your full descriptions. The page can say more; it should not contradict the listing.
How should I show allergens?
In words, on the dishes that contain them, using the names your kitchen will confirm. In the EU, allergen information for food you serve is mandatory; a website note does not replace the answer at the table. If you are not sure, do not guess — link to a short line that says “ask us” only as a bridge until the list is real.
How often should I update the menu online?
The same week the carte changes, in all three places: the page, the PDF, and the Google menu. A monthly check is enough when nothing has changed. A special that ended last month should not still be on the site.
Can Adiamo generate the menu from my Google listing?
A draft can pull menu signals from your listing into the page structure. You still edit names, prices, and allergens before publishing. The listing is a start, not a finished carte.