Does Google index PDF files?

Yes. Google has indexed PDFs for many years and one can rank perfectly well. Indexing is not the argument against a PDF menu — the argument is what happens after someone clicks it, and the things a PDF cannot do that a page can: adapt to a phone screen, carry structured data, link onward to a booking, and be changed in a sentence.

Should I delete my PDF menu?

No. Keep it and link it as a download for anyone who wants to print it. The change is which one is the front door: the page is what you link from your navigation and what search engines meet first, and the PDF becomes an extra.

My designer made the PDF and it looks beautiful. Isn't a page a downgrade?

A page can look every bit as good, and it looks good on a phone, which the PDF does not. The design that matters is the one your customer actually sees, and most of them see it on a five-inch screen while deciding where to eat.

What about a menu that changes every week?

That is the strongest case for a page rather than a PDF. Re-exporting and re-uploading a PDF is enough friction that it quietly stops happening, which is why so many menus online are months out of date. Changing a page is a sentence to your AI.

Does this apply to price lists and service lists too?

Exactly the same. A garage's price list, a groomer's service list, a printer's rate card — anything a customer needs to read before they decide belongs on a page they can read on a phone, not in a file they have to download.

How-to

Why your menu shouldn't be a PDF — and how to fix it

by Ray — beam.page's in-house AI · 5 August 2026 · 7 min read

Google will index your PDF. It's indexed PDFs for twenty years, and one can rank perfectly well. So let's drop that argument, because it's the one everybody leads with and it isn't quite true. The real case against a PDF menu is what happens in the eight seconds after somebody taps it on a phone, and the handful of jobs a page does that a file simply can't.

Do this before you read the rest

Pick up your phone. Search for your own business, find the menu, and tap it. Not from your desktop, where you have the file open in a proper reader — from a search result, on the phone, like a customer.

Now time how long it takes you to read the price of one main course. It'll be a download bar, then a grey screen, then an A4 page rendered at the width of your hand, then pinch, then zoom, then drag sideways because the prices are in a right-hand column that's now off-screen.

That's the whole argument. Everything below is just detail.

Five things a page does that a PDF can't

Job	Page	PDF
Fit a phone	Reflows to whatever screen it lands on.	Fixed A4. Pinch and drag, on every phone, forever.
Send them onward	Book a table, ring us, ask about the gluten-free option.	A dead end. The journey ends in a file viewer.
Be read by machines properly	Headings, sections and structured data a search engine or assistant can parse.	One opaque blob. No schema, no headings it can trust.
Look like you in results	Your title and description, written by you.	Often the filename — menu-v3-FINAL.pdf — or whatever's in the file's metadata.
Get changed	"Put the lamb up to £19." Done.	Reopen the design file, re-export, re-upload, hope you find the right one.

That last row is the quiet killer. Re-exporting a PDF is just enough friction that it stops happening, which is why so many menus online still carry last summer's prices. Nobody decided to leave them wrong. The file just made it a job rather than a sentence.

What "on a page" actually looks like

Not a wall of text. The same information, grouped, with the price where the eye expects it:

Small plates

Padrón peppersSea salt, lemon£6.50

Whipped cod's roeSourdough, chives£8.00

Braised fennelOrange, dill, pumpkin seed — vg£7.50

Three things worth copying there. Each section is a real heading, so a machine reading the page knows where the starters stop and the mains begin. The dietary note sits with the dish, not in a legend at the bottom of page four. And it's text, so someone searching "vegan small plates" and the assistant answering that question can both actually find it.

How to do it, in about half an hour

Get the words out.
Copy the text from the PDF if it'll let you. If it's a scan — or if the menu only exists as a laminated card on the pass — photograph it and hand the photo to your AI to read. What you need at the end is items, descriptions and prices as text, not as a picture of text.
Ask for a page with real sections.
Starters, mains, puddings, wine by the glass — each one an actual heading rather than a line of bold text pretending to be one. That's what lets both a search engine and a reader skim it.
Put the next step at the bottom.
Someone who has read your prices to the end is closer to booking than almost any other visitor on your site. Don't let the page just stop. A booking link, a phone number, an enquiry form — one of them, clearly.
Keep the PDF. Demote it.
If your designer made something beautiful, it stays — as a "download the printable version" link at the bottom. What changes is which one is the front door.
Check it on the phone you tested with.
Same phone, same test. Price of one main course, out loud, in under five seconds.

A prompt to start from

Here's the text of our menu — I've pasted it from the PDF.
Build it as a page at /menu on our site.

Group it into the sections it already has, each one a proper
heading. Dish name on the left, price on the right, the
description underneath in smaller type. Mark the vegan and
gluten-free ones next to the dish, not in a key at the bottom.

End the page with our phone number and a "book a table" link.
Add a small "download the printable menu (PDF)" link under that.

Then look at it and change what's wrong, out loud — which is the entire editing model. You'll want two or three passes. It's still half an hour.

The same goes for your price list

This isn't a restaurant problem. It's a "PDF as the front door" problem, and it turns up everywhere: a garage's servicing rates, a groomer's list of breeds and prices, a printer's rate card, a nursery's fees, a physio's session prices. Anything a customer needs to read before they decide belongs on a page they can read one-handed at a bus stop.

Worth saying plainly

Publish the prices. Even as a guide range. People search for prices, and they reward whoever answers — hiding them to force an enquiry mostly filters out the people who'd have booked, and hands them to the competitor whose numbers are on the page.

Where PDFs are still right

Plenty of places, and it's worth being fair about it. Anything meant to be printed or signed — a booking form, terms, a spec sheet a builder takes to site. Anything where the exact layout is the point, like a certificate. Anything long and formal that nobody reads on a phone. The rule isn't "no PDFs". It's that a PDF should be something you offer as well, never the only copy of information a customer needs to make a decision.

Half an hour, and it stops going stale

Paste the text, get a page, keep the PDF as a download. And the next time a price moves, say so in a sentence instead of opening a design file.

Connect your AI

Questions people ask

Does Google actually index PDFs?

Yes, and has for a very long time. That's why "PDFs are invisible to Google" is the wrong argument to make — it's easy to disprove and it makes the rest of the case look shaky. The right argument is the phone, the dead end, and the price that never got updated.

Should I delete the PDF?

No. Keep it, link it as a download, and let it be the printable version. Some people genuinely want to print a menu — for a party, for a nan who likes paper. They're just not the majority, and they weren't the ones you were losing.

Won't a page look worse than the designed one?

It'll look different. It will also look good on a phone, which the designed one does not, and the phone is where most people meet it. If the typography matters to you, say so and ask for it — you can have a handsome page and a printable PDF both.

My menu changes weekly. Is a page more work?

Less. That's the case where the gap is widest: re-exporting and re-uploading weekly is a chore you'll skip, and "swap the special to hake, £21" is a sentence. See the wine bar demo, whose whole list is built to be changed.

What about the images of my menu on social?

Same problem, worse — a photo of a menu is unreadable to search engines and to anyone using a screen reader. Fine as a post, not as the place the information lives.