76 percent of people who search for something nearby visit a business within 24 hours. If your menu is a PDF, you are invisible to every one of those searches. Every dish you serve is a keyword you are wasting.
Your menu is trapped in a file
You uploaded your menu as a PDF. It made sense at the time. You already had the file from the printer. Your designer made it look good on paper. You put a "Download Menu" button on your website and moved on.
But that file is now a locked box. Google cannot index the text inside it properly. A customer searching for "fish and chips near me" will never find you through that PDF. Someone on their phone has to download the file, wait for it to load, then pinch and zoom to read it. And anyone using a screen reader cannot navigate it at all.
Your menu is the single most important page on your restaurant's website. And you have turned it into a barrier.
Google cannot read what is inside your PDF
Google can technically open a PDF. It can extract some of the text. But it treats that content very differently from a normal web page.
A PDF has no title tag. No meta description. No structured data. No schema markup that tells Google "this is a menu item, this is the price, these are the allergens." It cannot carry Open Graph tags for social sharing. It does not contribute to your site's internal linking structure. Google Analytics cannot track what someone does inside a PDF because there is no page to track.
An HTML menu page can do all of those things. Every dish name, every ingredient, every price becomes searchable text that Google can index and serve to people who are actively looking for it. A PDF buries that information in a file format the web was not built for.
Nobody is pinching and zooming to find your chips
More than 60 percent of restaurant searches happen on mobile devices. Your customers are standing on a street corner, sitting on a bus, or lying on the sofa deciding what to eat. They want to see your menu now.
A PDF designed for A4 paper does not work on a phone screen. The text is too small. The layout is wrong. The customer has to download the file, wait for it to render, then pinch and zoom to read each section. Google's own research found that 53 percent of mobile visitors abandon a page that takes longer than three seconds to load. A menu PDF with images can easily be two to five megabytes. On a mobile connection, that is not three seconds. That is ten.
The Nielsen Norman Group has been saying it since 2003: PDFs are "unfit for human consumption" on the web. Their updated 2023 guidance is even blunter. "Do not use PDF to present digital content that could and should otherwise be a web page."
Your menu is exactly the kind of content that should be a web page.
The search you are invisible to
"Thai food near me." "Vegan brunch Leicester." "Gluten free pizza takeaway." These are real searches that real customers type into Google every day. "Near me" searches have grown by over 900 percent in recent years, and 76 percent of people who search for something nearby visit a business within 24 hours.
If your menu is an HTML page, Google can match those searches to the dishes you serve. "Pan-fried sea bass" on your menu page can appear in results for "seafood restaurant near me." "Margherita pizza" can appear for "pizza takeaway Leicester." Every dish is a keyword. Every ingredient is a search opportunity.
If your menu is a PDF, none of that happens. The words are locked inside a file that Google deprioritises in favour of actual web pages. Your competitors with HTML menus are showing up. You are not.
Accessibility is not optional
A PDF menu is not just inconvenient. For many people, it is unusable. 75.1 percent of screen reader users report that PDFs pose significant accessibility challenges. Navigation is difficult or impossible. Reading order is unpredictable. Tables, columns, and images rarely have the tags that assistive technology needs to interpret them.
The UK Government Digital Service put it plainly: "Compared with HTML content, information published in a PDF is harder to find, use and maintain." If the UK government considers PDFs unacceptable for public information, your restaurant menu should not be one either.
The Equality Act 2010 requires businesses to make reasonable adjustments for disabled customers. The European Accessibility Act, which took effect in June 2025, extends these requirements to digital services. A PDF menu that a screen reader cannot navigate is a barrier you can remove by simply publishing your menu as a web page.
What a proper menu page looks like
An HTML menu page is text on a web page. It loads instantly. It reads perfectly on any screen size. Google can index every word.
It does not need to be complicated. Your dishes, organised by section. Starters, mains, desserts, drinks. Prices next to each item. Allergen information marked clearly. Dietary labels like vegan, gluten free, and dairy free that customers can scan at a glance.
Add schema markup and Google can display your menu directly in search results. Your opening hours, your cuisine type, your price range, all structured in a format that search engines understand and surface to people who are ready to book or order.
The page updates instantly when your menu changes. No need to redesign a PDF, export it, upload it, and hope the old cached version does not still show up. Change the text. Save. Done.
The bottom line
Your menu is the most visited page on your restaurant's website. It is the page that decides whether someone books a table, places an order, or keeps scrolling. And right now, on most restaurant websites, it is a downloadable file that Google cannot index, phones cannot display properly, and screen readers cannot navigate.
An HTML menu page fixes every one of those problems. It loads instantly. It reads perfectly on any device. Google can index every dish, every ingredient, every allergen. It costs nothing extra to maintain and it makes your restaurant visible to every "near me" search that your PDF is currently hiding you from.
The fix is not complicated. Stop uploading a file. Start publishing a page.
How we can help
We build restaurant, cafe, and takeaway websites with proper HTML menus that Google can read and customers can actually use. No PDFs. No downloads. No pinching and zooming.
Your menu as clean, responsive text that loads instantly on any device. Schema markup so Google shows your dishes, hours, and location in search results. Allergen information structured so customers find what they need without asking. And when the menu changes, we update it. No delays, no re-uploading files, no outdated PDFs sitting in browser caches.
Whether you run a single cafe or a multi-site restaurant group, your menu is the most important page on your website. It should work like one.