Google can index the text in a PDF menu, and a PDF prints as you designed it. A menu written as a web page can fit a phone screen, give every dish its own address, and carry structured data that a PDF has no place for. Screen reader users report trouble with PDFs too: in WebAIM's 2019 survey, 75.1% of respondents said PDFs were likely to cause them significant accessibility issues. The practical answer for most restaurants is both, with the page as your menu and the PDF as a printable extra.
This guide compares the two on a phone, in search, for guests who use screen readers and for keeping prices current, then walks through moving from a PDF to a page.
PDF menu vs online menu at a glance
| PDF menu | Menu as a web page | |
|---|---|---|
| On a phone | A page laid out for paper, read by zooming in | Can be built to fit the width of the screen |
| In Google | Its text can be indexed, as one file | Its text can be indexed, as a page |
| An address for each dish | One address for the whole menu | Each dish can have its own |
| Structured data | Google's formats need a web page | Goes in the page's HTML |
| Screen readers | Needs tags, headings and a reading order | Needs real text, headings and alt text |
| Changing a price | Edit the source file, export, upload again | Edit the page and save |
| Printing | Prints as designed | Depends on how the page is set up to print |
Each row is explained below, with the source behind it.
What a PDF menu does well
A PDF holds a fixed layout. Your typeface, spacing and columns stay as your designer set them, on screen and on paper. That makes it a good match for the menu printed on your tables.
Picture a company booking your back room for 30 people. The organiser wants a menu to print and pass around the office, or to attach to an email. A PDF is the right tool for that job, and the same goes for catering, private dining and set event menus. Nielsen Norman Group says PDFs are meant for distributing documents that people will print (NN/g, Avoid PDF for on-screen reading).
A PDF is also quick to make from a design file you already have. Google can index the text in it, as the search section below explains. And a PDF can be made accessible: the W3C publishes a set of PDF techniques for WCAG, covered later in this guide.
Reading a PDF menu on a phone
A guest standing outside your door at 7:10 opens your menu on their phone. The PDF opens at the size of a printed page. They zoom in to read the starters, move sideways to find the prices, then zoom out again to find the mains.
Nielsen Norman Group's 2020 article by Jakob Nielsen and Anna Kaley describes the same problem in general terms (NN/g). PDFs are laid out for paper sizes, so the view on a screen shows only a small part of the content at a time. People can't scan and scroll around a PDF the way they can a web page. Content is split across sheets of paper, and a PDF has none of the navigation that helps people keep their place on a website. Their advice is to use PDF only for documents people will print.
A menu built as a web page can set its text to the width of the screen, so the guest reads by scrolling down. Section headings can link straight to each part of the menu. Whether a given page does this well depends on how it's built, so check yours on a phone.
PDF menus in Google search
What Google indexes in a PDF
PDF is on Google's list of indexable file types. In a 2011 post, Google explained how it handles them (Google, PDFs in Google search results):
- it can index the text in PDF files, in any language
- if you can copy and paste the text out of a PDF, Google should be able to index that text
- it may run OCR on PDFs made of scanned images to extract the text
- links in a PDF are treated much like links in HTML
So a PDF menu isn't hidden from Google. If your PDF was exported from a design program, try selecting a dish name. If you can select and copy it, the PDF holds real text.
Dish addresses and structured data
The whole menu is one file at one address, and every dish shares that address. A website can give each dish its own page and a plain link to it, which Google can crawl (Google, link best practices).
A PDF also has no place for structured data, the code that describes your restaurant and dishes in a standard vocabulary. The three formats Google supports (JSON-LD, Microdata and RDFa) are all written into a web page's HTML (Google, intro to structured data). Our guide to restaurant menu SEO covers that markup, with an example to copy.
A menu page with text and structured data is eligible to appear in search. Google doesn't guarantee that any feature using structured data will show up (Google, structured data guidelines).
PDF menus and screen readers
A guest who is blind uses a screen reader, software that reads the screen aloud. They want to know which dishes have nuts before booking a table for their family. Whether they can find out from your website depends on whether your menu is text their software can read, in an order that makes sense.
What screen reader users report
WebAIM, a non-profit service centre at Utah State University (WebAIM, About), surveys screen reader users. Its eighth survey ran in August and September 2019 and received 1,224 valid responses (WebAIM, Screen Reader User Survey #8). It asked how likely it was that each kind of document would pose significant accessibility issues.
| Document type | Very likely | Somewhat likely | Total likely |
|---|---|---|---|
| 36.8% | 38.3% | 75.1% | |
| Microsoft Word | 9.5% | 21.4% | 30.9% |
WebAIM notes that its sample was not controlled and may not represent all screen reader users. The survey is from 2019, so read it as a picture of that year.
Images of text and WCAG 1.4.5
The W3C's Web Content Accessibility Guidelines (WCAG) are the guidelines the Department of Justice points to, covered below. Success criterion 1.4.5, Images of Text, is at Level AA. It asks that information be shown as text wherever the technology can produce the same look (W3C, Understanding images of text). The exceptions are images of text the user can adjust, cases where a particular presentation is essential, and logotypes.
The reason given is that some people need text in a particular size, font, line spacing, alignment or colours. Real text lets them change all of that. A photo of your printed menu, or a PDF made from a scan, is an image of text.
Making a PDF accessible
A PDF can be made accessible. The W3C lists 23 PDF techniques for meeting WCAG (W3C, WCAG 2.2 techniques). If you keep a PDF, these are the ones to ask your designer about:
- PDF1: text alternatives for images
- PDF3: correct tab and reading order
- PDF6: table markup for tables
- PDF7: OCR on a scanned PDF, so it holds actual text
- PDF9: headings marked with heading tags
What the law says: the DOJ's guidance and Robles v. Domino's
In March 2022, the Department of Justice published Guidance on Web Accessibility and the ADA. It says Title III of the Americans with Disabilities Act prohibits discrimination against people with disabilities by businesses open to the public, and its list of examples includes food and drink establishments. It says the Department has taken the position since 1996 that the ADA applies to web content, including the goods and services businesses offer on the web.
The same guidance says the Department has no regulation setting out detailed standards for web accessibility. Businesses can currently choose how they make what they offer online accessible, and existing standards, including WCAG, provide helpful guidance. It also states that guidance documents have no legally binding effect. It doesn't mention menus or PDFs.
On 15 January 2019, the US Court of Appeals for the Ninth Circuit decided Robles v. Domino's Pizza (No. 17-55504), a case about a restaurant chain's website and app. Guillermo Robles, who is blind and uses screen-reading software, tried at least twice to order a customised pizza online from a nearby Domino's. He said he couldn't, because the website and app weren't designed so his software could read them.
The court held that the ADA applied to Domino's website and app. Its reasoning rested on their connection to Domino's physical restaurants, which are places of public accommodation under the ADA (42 U.S.C. § 12181(7)(B) lists a restaurant). Customers use the website and app to find a nearby restaurant and order pizzas for delivery or pickup, and the court called that connection critical to its analysis. It also held that applying the ADA didn't violate Domino's right to due process, and it sent the case back to the district court.
Here is what the opinion didn't decide:
- It expressed no opinion on whether Domino's website or app complied with the ADA.
- It said it didn't need to decide whether the ADA covers websites or apps whose inaccessibility doesn't get in the way of the goods and services of a physical location.
- It was about ordering food through a website and an app. It's one appeals court's decision, and it doesn't mention menus or PDFs.
Keeping a PDF menu current
Your supplier raises the price of short rib on a Tuesday. To change one number on a PDF menu, someone opens the design file, edits the price, exports a new PDF, uploads it to the website and checks that the menu link opens the new file. If the new file gets a new address, every link to the old one keeps opening the old prices. That includes the QR code on your tables and the menu link on your Google Business Profile, until someone updates them.
The same loop applies when the kitchen runs out of the halibut at 7:30. A PDF can show it as sold out only if someone repeats every step. On a web page, you change the text and save.
Structured data adds one more thing to keep in step. Google's guidelines say your markup must be a true representation of the page content (Google, structured data guidelines), so a price change on the page needs the same change in the markup.
How to move from a PDF menu to a menu page
1. Get your menu into text
Start from the file you designed the PDF in, or copy the text out of the PDF if it lets you select words. A scanned menu has to be typed out. Check every price and description against the menu your kitchen is cooking today.
2. Build the menu page at one address
Give the menu one page on your own site, at a short address such as /menu, and keep that address when the menu changes. Use a heading for each section. Write each dish's name, description and price as text, along with dietary information such as "vegan" or "contains nuts".
Make sure every dish is in the page when it loads. Google says it won't load content that needs a swipe, click or typing to load (Google, mobile-first indexing).
3. Add structured data
Describe the restaurant and its menu with JSON-LD. Our restaurant menu SEO guide covers the properties Google documents for restaurants, schema.org's Menu, MenuSection and MenuItem, and a full example to copy.
4. Keep the PDF as a printable extra
Link the PDF from the menu page with a label that says what it is, such as "Print the menu (PDF)". Update it whenever the page changes, so the two never disagree. If you can, ask your designer to apply the W3C's PDF techniques above.
5. Point everything at the page
In your Google Business Profile, select Edit profile, then Business information, then Contact, then Menu link, and enter the page's address (Google Business Profile Help). Update the menu link in your social profiles and booking pages. A QR code that holds the old PDF's address keeps opening that file, so make new codes that point to the page.
6. Check the page
Open the page on your phone and read it as a guest would. Then use URL Inspection in Google Search Console to see the page as Google renders it, and request indexing once it's live. The restaurant menu SEO guide explains both checks.
Where MenuFramer fits
If you'd rather not build and update the page by hand, MenuFramer fills the menu page you already have. You paste one snippet into that page, and it becomes a menu with a photo per dish, search, and dietary and allergy filters. You can change a price or mark a dish sold out from your phone, and it shows on the menu when saved. Each location gets a QR code that keeps opening the current menu after you change it. See dishes and how the embed works.
Frequently asked questions
Can Google read my PDF menu?
Yes. PDF is one of the file types Google indexes, and Google has said it can index the text in a PDF and may use OCR on scanned ones. The whole menu is one file at one address, so no dish has an address of its own, and Google's structured data formats need a web page.
Is a PDF menu ADA compliant?
Neither the DOJ's 2022 guidance nor the Robles opinion mentions PDF menus. The DOJ says the ADA applies to the web content of businesses open to the public, including food and drink establishments, and treats WCAG as helpful guidance without setting a fixed standard. Whether your menu meets the law is a question for a lawyer, and this guide isn't legal advice.
Should I delete my PDF menu?
There's no need to. Keep it as a printable extra, linked from your menu page, and update it when the page changes. Make sure your QR codes and Business Profile menu link point to the page.
What about a photo of the printed menu?
A photo of a menu is an image of text. WCAG 1.4.5 asks for real text wherever the same look can be made with text, so people can change its size, font and colours. Keep the photo if you like it, and put the dishes on the page as text as well.
Can a PDF menu be made accessible?
Yes. The W3C lists 23 PDF techniques for WCAG, including headings marked with heading tags, a correct reading order and OCR for scanned pages. If you keep a PDF, ask for those when it's made.
Sources
- Avoid PDF for On-Screen Reading, Nielsen Norman Group, checked October 2026
- Screen Reader User Survey #8 Results, WebAIM, checked October 2026
- About WebAIM, WebAIM, checked October 2026
- Understanding SC 1.4.5 Images of Text (Level AA), W3C, checked October 2026
- Techniques for WCAG 2.2, W3C, checked October 2026
- Guidance on Web Accessibility and the ADA, US Department of Justice, checked October 2026
- Robles v. Domino's Pizza, LLC, No. 17-55504 (opinion), US Court of Appeals for the Ninth Circuit, checked October 2026
- File types indexable by Google, Google Search Central, checked October 2026
- PDFs in Google search results, Google Search Central Blog, checked October 2026
- Link best practices for Google, Google Search Central, checked October 2026
- Introduction to structured data markup in Google Search, Google Search Central, checked October 2026
- General structured data guidelines, Google Search Central, checked October 2026
- Mobile site and mobile-first indexing best practices, Google Search Central, checked October 2026
- About the menu editor, Google Business Profile Help, checked October 2026
