Skip to content

Restaurant Websites

Restaurant menu pages that search engines can actually read

Why PDF and image menus underperform, what an HTML menu page should contain, and how menu content supports dish-level and dietary searches.

Alex Opsenica, founder of Moolah Media

Alex Opsenica · Founder, Moolah Media

4 min read
On this page

On most restaurant websites the menu is the single most-visited page, and on a large share of them it is a PDF designed for print. That decision quietly removes the site's richest source of relevant text from search, and adds friction for the guest who opened it on a phone.

Key takeaway

If the menu is a PDF or an image, the most valuable content on the site is invisible to search and awkward on mobile. Publish it as text first, and offer the print version as an extra.

Why a PDF menu underperforms

  • Pinch-and-zoom on a phone is friction at the exact moment of decision
  • Dish, dietary and ingredient terms are not available as page content
  • The file has no headings, no internal links and no booking call to action
  • Updating it requires a designer, so it goes stale between seasons
  • Analytics show a file open, not an engaged page view

Worth avoiding

Prices that are wrong in a cached PDF are a service problem before they are a search problem.

What an HTML menu page should contain

Menu page anatomy

One H1 naming venue and menu

Purpose
Establishes the page subject clearly

Sections as headings

Purpose
Starters, mains, desserts, wine — navigable and scannable

Dish name, short description, price as text

Purpose
The content that answers dish-level and dietary searches

Dietary markers in text, not only icons

Purpose
Vegetarian, vegan, gluten-free read by guests and machines alike

Service times and last orders

Purpose
Prevents the most common wasted journey

A booking action within thumb reach

Purpose
Converts the intent the menu just created

Link to the printable version

Purpose
Keeps the designed PDF available without making it the primary

Source: Google Search Central — Local Business structured data (restaurants and menus) — Markup that describes a restaurant and its menu to search engines.

Menu page build checklist

  • Menu published as selectable text, not an image or PDF-only
  • Separate pages for genuinely separate menus — lunch, dinner, tasting, wine, group
  • Dietary and allergen guidance written as text
  • Prices reviewed on the same schedule as the kitchen changes them
  • Structured data describing the restaurant and its menu
  • Booking action visible without scrolling back to the top
  • Page loads quickly on a mid-range phone over mobile data

Separate menus deserve separate pages

A tasting menu, a set lunch, a wine list and a group menu answer different questions and attract different searches. Collapsing them into one long page makes each harder to find and impossible to link to precisely from a Business Profile or an enquiry email.

Example · hypothetical

Hypothetical: the group menu that was a paragraph

A venue keeps its group menu as three lines inside the main menu page. Enquiries arrive asking what is included. Giving it a page with courses, minimum numbers and a deposit policy removes the exchange and captures a search nobody else in the area answers.

See this in practice

Building local search infrastructure from the ground up.

Premium steakhouse group · name withheld · Dublin 2

33 → 47Domain Authority · recorded in Moz Domain Authority

Fifteen months of local search infrastructure: Domain Authority 33 to 47, linking domains 104 to 197, 83% map pack coverage.

See a website and profile rebuild in a real engagement

Dish-level and dietary demand

Menu pages earn traffic that no other page can: people search for a specific dish, a dietary requirement or a price band alongside a place name. That demand only exists if the words are on the page as text.

What the text has to carry

Dish plus location

What the page needs
The dish named in a heading or item text, not only in a photograph

Dietary plus cuisine

What the page needs
Vegetarian, vegan, gluten-free and allergen notes written out

Set menu or early bird

What the page needs
Its own section with times, price and what is included

Wine or cocktail lists

What the page needs
A separate page when the list is long enough to be a reason to visit

Group or Christmas menus

What the page needs
A dated page kept live, then updated rather than deleted

Deleting a seasonal menu page each year throws away whatever authority it accumulated. Keep the URL and update the content, so the next season starts from an established page.

Menu page review

  • Every dish name selectable as text on a phone
  • Prices current and matching the room
  • Dietary markers written as words as well as icons
  • Last orders and service times stated
  • A booking action within reach at the bottom of the page
  • Seasonal menus updated at a stable URL rather than replaced

The menu on the profile and the menu on the site

Most restaurants maintain at least three menus: the printed one, the website one and the Business Profile one. Guests treat any of them as authoritative, and a price that is out of date reads as a bait-and-switch at the table.

Keeping menus in step

  • One master menu owned by the kitchen, with a date on it
  • Website menu updated from the master the day it changes
  • Business Profile menu updated in the same pass
  • Delivery and ordering platform menus checked monthly
  • Old seasonal menus updated at the same URL rather than deleted

A single owner and a single trigger — the kitchen changing the master — prevents almost all of the drift that produces complaints.

Where allergen information is involved, the stakes of drift are higher than a wrong price. Tools exist to keep every version aligned from one approved source — Crumb, built by Moolah Media's founder, is one, keeping QR menus, printed menus, allergen matrices and staff sheets in step. A disciplined manual process can do the same job; what matters is that no public menu is edited independently of the kitchen's record.

Common questions

Can I keep a PDF menu at all?

Yes, as a secondary printable version. The primary menu should be text on a page so guests and search engines can both read it.

Should prices be on the menu page?

Yes. Price is one of the first things a guest looks for, and omitting it usually sends them to a third-party listing that shows one anyway.

Do I need menu structured data?

It helps describe the page accurately, but it never substitutes for a readable, current menu in the page content itself.

How often should the menu page change?

Whenever the kitchen changes it. A menu page that contradicts the dining room damages trust faster than any ranking gain repays.

Working on this yourself? Restaurant website and content.

Discuss your restaurant

Is your website helping or quietly getting in the way?

The audit reviews menu accessibility, location content, structured data and mobile performance, and separates search issues from booking friction.

Get Your Free Visibility Audit

Written by

Alex Opsenica, founder of Moolah Media

Alex Opsenica

Founder, Moolah Media

Founder of Moolah Media, a founder-led restaurant marketing specialist based in Ireland, working with restaurants worldwide on websites, SEO and Google Maps, and Google Ads. Around 20 years in hospitality, including hands-on restaurant management.

More about how Moolah works.

Continue exploring

More on Restaurant WebsitesAll insights