Why Your Restaurant Needs a Menu Link, Not a Menu PDF, on Google

Nobody chose the PDF. It just happened.

The designer sent a print file. Someone uploaded it to the website because it was the fastest way to get the menu online. Then the Google listing needed a menu, so the same file went there too. Years later it’s still what a stranger sees when deciding whether to eat with you tonight.

It’s the most common setup in the industry, and it creates four separate problems. One of them is legal, and most operators have never heard about it.

What Google’s Menu Field Actually Is

The menu field on a Google Business Profile is just a URL. Google doesn’t host your menu or care what sits behind the link. It points wherever you tell it to.

That’s freeing, and it’s the trap. A link to a PDF is technically valid, so nothing warns you it’s a poor choice. The field saves either way.

The Problem Nobody Mentions: Accessibility

Screen readers, the software blind and low-vision people use to browse, generally struggle with PDFs, and a scanned or image-based PDF is essentially unreadable to them. A web page built with real text is not.

That matters legally. In Robles v. Domino’s Pizza (9th Cir. 2019), the Ninth Circuit held that the Americans with Disabilities Act applies to a restaurant chain’s website and app because of their connection to its physical restaurants, (913 F.3d 898), and the Supreme Court declined to hear the appeal (Supreme Court docket No. 18-1539). Since then, website accessibility claims have become a steady part of ADA litigation. Law firm Seyfarth Shaw counted 8,667 ADA Title III lawsuits filed in or removed to federal court in 2025, down only slightly from 8,800 in 2024 (Seyfarth Shaw, via Mondaq). Not all of those are about websites, and not all involve restaurants, but menus are an obvious target because every restaurant has one and so many are PDFs.

The broader web isn’t doing well either. WebAIM’s 2026 analysis of the top one million home pages found 95.9% had detectable WCAG 2 failures, with an average of 56.1 errors per page (WebAIM Million). Restaurants aren’t unusually bad. A PDF menu is simply one of the most visible, most easily tested problems on a restaurant site.

None of this is legal advice, and requirements vary. The practical takeaway is cheap: replacing a PDF menu with a real-text menu page removes one of the most common accessibility problems on a restaurant website and makes the menu better for everyone at the same time.

The Mobile Problem: Pinch, Zoom, Give Up

Watch someone open a PDF menu on a phone. It loads in a viewer. The whole page renders at once, so the text is tiny. They pinch to zoom, lose the category headers, scroll sideways hunting for prices. Meanwhile the file, often several megabytes because it was built for a printer, is still loading on a patchy signal.

That’s the experience for most people who look at your menu, because most of that looking happens on a phone, before they arrive. You’re making your most important sales pitch in the worst possible format.

The Two-Sources-of-Truth Problem

A PDF has to be regenerated to change. Every price update means going back to whoever has the design file, exporting a new version, and re-uploading it everywhere it lives.

In practice, that doesn’t happen. The website gets updated and the Google listing doesn’t, or the other way round. Within a year you have two or three versions of your menu in public, disagreeing about prices, and a guest who walks in expecting the old one.

A link to a live menu has one version. That’s the whole difference, and it’s worth more than it sounds.

The Invisibility Problem

Search engines and AI assistants read a web page far better than a PDF, especially an image-based one. Google’s own guidance for its AI search features tells site owners to keep important content available as text (Google Search Central). Dish names, ingredients, and dietary terms locked inside a design file often aren’t matchable. Someone searching for a specific dish or a gluten-free option nearby won’t find you, and you’ll never see the miss.

What to Use Instead

The fix is a menu that lives as an actual web page: real text, built for a phone, fast to load, one source of truth, and a link you can paste into your Google listing once.

That’s what MenuOnGo gives you, on every plan including the free one: a permanent menu link, the same one your table QR code opens, that you paste into Google once and never have to touch again when prices change. If accessibility is the reason you’re reading this, the Pro plan’s menu is ADA-ready, built to WCAG 2.1 AA with real text instead of pictures of text, proper headings, strong contrast, and full keyboard and screen-reader support. One honest caveat that applies to any platform: the content you add, photos, videos, colors, and text, stays your responsibility to keep accessible, so describe dishes in words and don’t put text inside images.

And you don’t lose print. The PDF goes back to being what it was always meant to be: a file you send to a printer, not the thing representing your restaurant to everyone who looks you up.

An Honest Note on Effort

If you have a beautifully designed PDF menu you’re proud of, the design wasn’t wasted. Print is where it belongs, and plenty of guests still like holding paper. The argument here is narrower: a print file is the wrong thing to use as a public link. Different job, different format. Keep both.

PDF Menu vs. Menu Link: What Actually Differs

Factor	PDF Menu	Live Menu Link
Screen reader accessibility	Poor; near zero if image-based	Readable text
Accessibility exposure	A commonly tested weak spot	Substantially reduced when built to WCAG
Mobile experience	Pinch, zoom, sideways scrolling	Built for a phone
Load time	Often several megabytes	Light page
Updating a price	Re-export and re-upload everywhere	One change, live everywhere
Versions in public	Usually two or three	One
Search and AI visibility	Limited, often none	Indexable text
Printing	Excellent	Print from the live menu when needed

Frequently Asked Questions

Can I put a PDF menu on my Google Business Profile? Technically yes. The menu field accepts any URL, including a PDF. But it creates accessibility, mobile, and search visibility problems that a normal web page doesn’t, so it’s rarely the right choice for a public link.

Are PDF menus an ADA risk for restaurants? They can be. Screen readers struggle with PDFs and can’t read image-based ones at all, and in Robles v. Domino’s Pizza the Ninth Circuit held that the ADA applies to a restaurant chain’s website and app. Federal ADA Title III filings stood at 8,667 in 2025, according to Seyfarth Shaw. This isn’t legal advice.

Why does menu format matter for showing up in search? Search engines and AI assistants index readable text. Dish names and dietary terms locked inside a PDF, particularly a scanned one, often can’t be matched, so specific searches may never surface your restaurant.

Should restaurants stop making PDF menus entirely? No. PDFs are the right format for sending a design to a printer. The mistake is using that print file as the menu the public sees online.

What’s the fastest way to fix a PDF menu problem? Replace the link on your Google listing and website with a live, real-text menu page, and keep the PDF for printing. It’s usually an afternoon of work.

---

Sources: Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019); Supreme Court of the United States (docket No. 18-1539), Seyfarth Shaw LLP (via Mondaq), WebAIM Million (2026), Google Search Central. Images: Pexels (free to use). Data current as of October 2026. This article is general information, not legal advice.