Marketing and Local Growth

Menu SEO: Put Your Menu Where Google Can Read It

Why HTML menus beat PDF-only menus, how to write dish names and descriptions people search for, add menu structured data and keep menus current everywhere.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why the menu page matters for search
  2. HTML menu or PDF?
  3. Build the menu page
  4. Write dish names and descriptions people search for
  5. Add structured data for the menu
  6. Your menu on Google itself
  7. Keep every copy of the menu in sync
  8. Drinks, specials and dietary menus
  9. Make the menu page accessible
  10. Check your work like a guest
  11. Frequently asked questions
  12. References
Marketing and Local Growth: Menu SEO: Put Your Menu Where Google Can Read ItArticle coverMARKETING AND LOCAL GROWTHMenu SEO: Put Your MenuWhere Google Can ReadItAva for RestaurantsInsightsMarketing and Local Growth: Menu SEO: Put Your Menu Where Google Can Read ItArticle coverMARKETING AND LOCAL GROWTHMenu SEO: Put YourMenu Where Google CanRead ItAva for Restaurants

Key takeaways

  • Publish your menu as an HTML page with dish names, short descriptions and prices; keep any PDF as an extra, not the only version.
  • Schema.org's FoodEstablishment type has a hasMenu property that accepts a structured menu, text or a menu URL[1].
  • Google's local business structured data lists a menu property: for food establishments, the fully qualified URL of the menu[2].
  • Build the same menu in Google's menu editor and set your preferred menu; changes can take 24 to 48 hours to appear[3].
  • Change the website, Google, delivery apps and printed menus on the same day, from one master menu file.

Many restaurant searches are really menu searches. Guests look for a dish (“birria tacos,” “cacio e pepe,” “vegan ramen”), a dietary need (“gluten-free pizza”) or a format (“bottomless brunch”), usually with “near me” attached. Google can only match those searches to your restaurant if it can read what you serve. A menu locked inside an image, an outdated PDF or a third-party widget that loads after the page is a weaker signal than a clean, current HTML page.

The menu page also does the selling. Guests compare menus on phones before choosing where to eat or order. National Restaurant Association research found that 57% of adults have recently used mobile ordering, including 74% of millennials and 65% of Gen Z adults[4]. A menu that is hard to read on a phone loses those guests before they reach your ordering page.

US adults who have recently used mobile ordering (2025)
US adults who have recently used mobile ordering (2025)Bar chart. Millennials: 74%; Gen Z adults: 65%; All adults: 57%.MillennialsMillennials: 74%74%Gen Z adultsGen Z adults: 65%65%All adultsAll adults: 57%57%US adults who have recently used mobile ordering (2025)Bar chart. Millennials: 74%; Gen Z adults: 65%; All adults: 57%.MillennialsMillennials: 74%74%Gen Z adultsGen Z adults: 65%65%All adultsAll adults: 57%57%

Source: National Restaurant Association, 2025[4]

Show the data
ItemValue
Millennials74%
Gen Z adults65%
All adults57%

HTML menu or PDF?

HTML menu pages compared with PDF-only menus.
QuestionHTML menu pagePDF-only menu
Readable on a phone without zoomingYes, if built responsivelyUsually not
Easy for search engines to read dish by dishYesLess reliable; depends on how the PDF was made
Easy to update the same dayYes, edit textNeeds a new file and upload
Works with screen readersYes, with proper headings and labelsOften poor unless carefully tagged
Can link to specific sectionsYes (lunch, dinner, drinks)No
Loads quickly on cellular dataYesOften slow for large files
Good for printingPossible with a print stylesheetYes

The answer for most restaurants is both: an HTML menu as the main version, linked from every page and from your Google profile, with a printable PDF offered as a download for guests who want it.

Build the menu page

  1. One page per menu, or clear sections

    Separate lunch, dinner, brunch, drinks, desserts and kids with headings. Each menu can be its own page if it is long, with a short URL such as /menu/brunch/.

  2. Use real headings

    Section names (Starters, Mains, Sides) as headings, dish names as text, not as images. Assistive technology and search engines both use headings to understand structure.

  3. Add dish details

    Name, a one-line description with key ingredients and method, dietary labels and price.

  4. Add a short introduction

    Two sentences at the top saying what kind of food you serve, where, and when each menu is available.

  5. Link to action

    Book a table and Order pickup buttons at the top and bottom of the menu page.

  6. Date it

    A small “Menu updated” date reassures guests the prices are current.

Write dish names and descriptions people search for

Creative names are fine, but pair them with the words guests use. “The Godfather” tells a search engine nothing; “The Godfather: spicy soppressata pizza with hot honey” tells it, and the guest, exactly what to expect.

  • Lead with the common dish name, then the house twist: “Birria tacos, braised beef, consommé for dipping.”
  • Name the cooking method and key ingredients: wood-fired, smoked, hand-pulled, house-made.
  • Use dietary labels consistently and only where accurate: vegan, vegetarian, gluten-free, contains nuts.
  • Mention regional styles where they help: Neapolitan, Detroit-style, Sichuan, Oaxacan.
  • Avoid stuffing keywords. One natural description per dish reads better and works better than lists of search terms.

Add structured data for the menu

Structured data is code in a standard vocabulary that describes the page. Schema.org defines a FoodEstablishment type, with subtypes such as Restaurant, CafeOrCoffeeShop and BarOrPub. Its hasMenu property accepts either the actual menu as a structured representation, the menu as text, or a URL of the menu, and it supersedes the older menu property[1].

Google's documentation for local business structured data lists menu among the recommended properties, described for food establishments as the fully qualified URL of the menu, alongside properties such as servesCuisine, telephone and openingHoursSpecification. Google recommends validating markup with the Rich Results Test and checking deployed pages with the URL Inspection tool[2].

  • Minimum: Restaurant markup on the home or location page with name, address, phone, hours, cuisine and a hasMenu or menu URL pointing to the HTML menu page.
  • Fuller option: a structured Menu with MenuSection and MenuItem entries, each with name, description and price, generated from the same data as the visible page.
  • Keep markup and visible text identical. Prices or dishes that appear only in the markup are a quality problem, not an optimization.
  • Regenerate the markup whenever the menu changes; stale structured data is worse than none.

Your menu on Google itself

Google's Business Profile has its own menu editor for food and drink businesses. Customers see the items under the Menu section of your profile, grouped into sections you define. Google says changes can take 24 to 48 hours to display on Maps and Search, and that when it finds more than one menu source you can choose which one appears as your preferred menu[3].

  1. Build the menu in the editor using the same sections and dish names as your website.
  2. Add the menu link pointing to your HTML menu page.
  3. Set your preferred menu so an old PDF or a third-party menu is not shown instead.
  4. Plan for the delay: update Google a day or two before a menu launch if you can.

Keep every copy of the menu in sync

Guests find your menu in many places: your website, Google, Apple Maps, Yelp, reservation platforms, delivery apps and printed menus. When they disagree, guests lose trust and staff spend time explaining. Keep one master menu file, usually a spreadsheet or your POS menu, and update every channel from it on the same day.

  • Keep a channel list with the person responsible for each: website, Google, delivery apps, QR menus, printed menus.
  • When prices change, update online ordering and delivery apps first, since those are where guests pay.
  • Remove seasonal dishes from every channel when they come off the menu.
  • Check each channel once a month by searching your restaurant and opening each menu.

Example (fictional): a Sichuan restaurant replaces its PDF menu with an HTML page that names each dish in English with its common Chinese name and a short description, adds Restaurant markup with a menu URL, and rebuilds the Google menu in the editor. Over the following months, staff notice more guests arriving to order specific dishes they found by searching, and fewer calls asking whether the restaurant serves dan dan noodles.

Drinks, specials and dietary menus

Drinks lists, daily specials and dietary menus are often left off the website because they change often. They are also exactly what some guests search for: “natural wine bar,” “happy hour oysters,” “vegan brunch.” Give each its own section or page, even if it is short.

  • Drinks: list categories and a few named examples with prices, and update the page when the list changes, rather than leaving it off.
  • Specials: a “This week” section with dates, removed when the special ends.
  • Dietary: a filtered view or a short page listing vegan, vegetarian and gluten-free dishes, with the same labels as the main menu.
  • Happy hour: days, times and the items included, also added under More hours on your Google profile if offered.

Make the menu page accessible

An accessible menu is also a better menu for search and for every guest on a phone. Some guests rely entirely on mobile data and small screens: 16% of US adults are smartphone-only internet users[5]. Build the page so it works for them and for guests using screen readers or keyboard navigation.

  • Real text with strong contrast, never menu text baked into a photo.
  • Headings for each section so screen readers can jump between Starters, Mains and Desserts.
  • Alt text for dish photos that names the dish.
  • Prices and dietary labels in text next to each item, not shown only as icons or colors.
  • A layout that reflows on small screens without sideways scrolling.

Check your work like a guest

Once a month, search for three of your signature dishes plus “near me” on a phone, and for your restaurant name plus “menu.” Note which version of the menu appears first: your website, Google's menu, a delivery app or an old PDF. Open each and compare prices and dishes with what you serve today. Then ask a friend who has never eaten with you to find a vegetarian main and the price of a glass of wine on your site; if it takes more than a few taps, simplify the page.

Frequently asked questions

Is a PDF menu bad for restaurant SEO?

A PDF-only menu is weaker than an HTML menu: harder to read on phones, harder to update and less reliable for search engines and screen readers. Use an HTML menu as the main version and keep a PDF for printing.

What structured data should a restaurant menu use?

Restaurant markup with a hasMenu or menu URL at minimum; schema.org's hasMenu accepts a structured menu, text or a URL[1]. A fuller Menu with sections and items is optional.

How do I add my menu to Google?

Use the menu editor in your Google Business Profile, add a menu link to your HTML menu page and choose your preferred menu. Changes can take 24 to 48 hours to appear[3].

How often should a restaurant update its online menu?

Every time the printed menu or prices change, on the same day across your website, Google, delivery apps and QR menus, from one master file.

References

  1. Schema.org (2026). FoodEstablishment (type definition) (opens in a new tab) ↑

  2. Google Search Central (2026). Local business (LocalBusiness) structured data (opens in a new tab) ↑

  3. Google Business Profile Help (2026). About the menu editor (opens in a new tab) ↑

  4. National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑

  5. Pew Research Center (2026). Americans’ Use of Mobile Devices in 2026 (Fact Sheet) (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo