What Google's Crawler Actually Sees When It Visits Your Site
Imagine sending a mystery shopper to your shop, but they're blindfolded and can only read printed text. That's roughly what Google's crawler does every time it visits your website.
Google reads text. It follows links. It processes structured data. What it cannot do — at any meaningful scale — is extract the contents of a scanned PDF or read the words printed inside a JPEG photograph of your menu board.
So when someone types "chicken tikka masala takeaway [your town]" into Google, your site won't surface for that dish if the only place that dish name exists is inside a PDF nobody can read. Google simply doesn't know you sell it.
This is one of the most common reasons takeaways and restaurants don't show up in local search, and it's almost always fixable. The fix isn't complicated. But first, it's worth understanding exactly what the crawler encounters.
The Crawler-Eye View: JPEG vs Text Menu
Let's make this concrete. Here's what Google's crawler actually processes when it hits two different menu pages.
| What you put on the site | What Google's crawler reads | What can rank? |
|---|---|---|
| A scanned photo of your menu (JPEG/PNG) | An image file — pixels, dimensions, file size. No text. | Nothing. The whole menu is invisible. |
| A PDF uploaded to your site | A document link. Most PDF text is not processed reliably by crawlers, especially scanned PDFs. | Very little. Unreliable at best. |
| Plain HTML text on the page | Every word, every dish name, every price and allergen note. | All of it — every dish can match a search query. |
| HTML text + menu schema markup | Every word, plus structured data telling Google exactly what each item is, its price, dietary flags, and which restaurant serves it. | Maximum coverage — eligible for rich results and local panels. |
The gap is not subtle. A photo menu gives Google essentially nothing. A properly coded HTML menu with schema markup gives Google everything — and Google can then surface that information directly in search results, in Maps, and in AI-generated answers.
Why So Many Takeaways Still Use PDFs
Most owners didn't choose a PDF menu to sabotage their own SEO. It just happened.
The designer who built the site five years ago dropped a PDF in because it was quick. Or the owner emailed over the menu as a Word document and the agency just converted it. Or someone photographed a printed menu at 11pm because the printer was going out and just stuck it on the site.
Understandable. But now the prices have changed, you've added seasonal specials, and the only record of what you actually sell online is a blurry image or a PDF nobody can search — including Google.
- PDFs can't be updated without replacing the whole file and re-uploading.
- A photo menu can't be updated at all without a new photo.
- Neither can be linked to a specific dish by a customer or a search engine.
- Neither can carry schema markup that identifies your menu as belonging to your restaurant.
- Neither will surface in Google's restaurant panels or AI-generated local answers.
What Menu Schema Markup Actually Is (Plain English)
"Schema markup" sounds technical. It isn't difficult to understand, even if the implementation needs a developer.
Schema is a shared vocabulary — agreed by Google, Bing, and others — that lets you label bits of your page so search engines know exactly what they're looking at. Instead of Google guessing that "Chicken Tikka Masala — £11.95" is a menu item, schema tells it directly: this is a MenuItem, it belongs to this Restaurant, it costs £11.95, it contains this allergen information.
Google uses this in several ways. It can pull your menu items into your local Knowledge Panel on Maps. It can show dish names alongside your listing in search results. It can include your menu in AI-generated answers when someone asks about what's on offer near them.
None of that is possible with a PDF. None of it is possible with an image. It only works when your menu is real, readable, structured text on the page.
Schema markup for a restaurant menu typically covers: the restaurant name and address, each menu section (starters, mains, sides, desserts), each item's name, description, and price, and optionally dietary flags like vegetarian, vegan, or gluten-free. Google's own guidance confirms that structured data helps search engines understand your content and display it more usefully.
The Real Cost of an Invisible Menu
Let's be direct about what this means in practice.
Someone in your town searches "vegan takeaway [your area]". You have six vegan dishes. But they're all listed inside a PDF. Google doesn't know you have vegan options. A competitor with a plain-text HTML menu listing their vegan dishes appears instead. You don't.
Someone searches "[dish name] near me" — a dish you're known for, the one that gets rave reviews. Your menu photo sits on your site, but Google can't read it. Someone else shows up.
You're paying for a website. You're paying for hosting. But a large part of its job — telling Google what you sell — isn't being done at all.
Every ordering platform you're on (Just Eat, Deliveroo, Uber Eats) has a text-readable menu. That's one reason those platforms rank well in local search — their sites are technically solid and their menu content is crawlable. Your own site should have the same advantage.
This matters even more when you're trying to grow direct orders and reduce reliance on platforms that charge 14% on collection or up to 30–35% on delivery. If your own site can't be found, it can't convert anyone.
How Takely Rebuilds Your Menu as Real Text
Every Takely package — from Starter at £499 upwards — includes the menu rebuilt as real, readable, structured text on the page. Not a PDF link. Not an embedded image. Actual HTML with schema markup applied.
This means every dish name, every category, every price is readable by Google from day one. If you have allergen information or dietary labels, those go in too. The menu is part of the site, not bolted on as a file.
When you need to update a price or add a new dish, that's a standard content update — covered in the monthly plan. You're not swapping out a PDF or taking a new photo. The change goes live on the page and Google picks it up the next time it crawls.
The Growth package at £999 goes further: locally-targeted landing pages that link your specific dishes to specific nearby areas, wired into your existing ordering system (Flipdish, Slerp, storekit, or an app link). If you want to see what a high-converting takeaway site looks like, the menu structure is always central to it.
If you're currently not showing up on Google, an unreadable menu is likely one of several issues — but it's usually the biggest one, and the easiest to fix with the right build.
What to Check on Your Site Right Now
You don't need a developer to diagnose the problem. Do this now, on your phone.
- Go to your website and find your menu page.
- Try to highlight text on the page with your finger. If you can select dish names, it's text. If you can't, it's an image or PDF.
- Look at the URL when you click the menu link. If it ends in .pdf or opens a new document viewer, that's a PDF.
- Go to Google and search your restaurant name + a specific dish you're known for. Does any result from your own website appear? If not, Google can't see that dish.
- Search your restaurant name on Google Maps. Look at the menu tab if one appears. Is your actual menu there, or is it missing entirely?
If you couldn't highlight text, or your menu opens as a PDF, or your dishes don't appear in Google — those are fixable problems. The foundation is converting your menu to real, schema-marked text on the page.
If you want us to take a look at your current site before you commit to anything, contact us and we'll give you a straight assessment.
PDF vs HTML Menu: Quick Comparison
| Feature | PDF / Image Menu | HTML Text Menu + Schema |
|---|---|---|
| Google can read it | No | Yes |
| Dishes appear in search results | No | Yes — eligible for rich results |
| Works in Google Maps menu tab | No | Yes |
| Can be updated without re-uploading | No | Yes |
| Customers can copy/share a dish link | No | Yes |
| Works on slow mobile connections | Slow (large file download) | Fast (loads as page text) |
| Schema markup possible | No | Yes |
| Accessible to screen readers | No (unless tagged PDF) | Yes |
There is no category where a PDF or image menu outperforms a properly built HTML text menu. The PDF is only ever convenient for the person who built the site — not for you, and not for your customers searching on Google.
Frequently asked questions
Can Google read PDF menus at all?
Sometimes, partially. Google can index the text inside some PDFs — particularly those created digitally rather than scanned. But even then, it's unreliable, and PDF content cannot carry the menu schema markup that gets your dishes into rich results, Maps panels, and AI-generated answers. A scanned or photographed menu gives Google nothing at all. HTML text is always the right choice.
What is menu schema markup and does it actually help?
Menu schema markup is structured code that labels each dish, price, and description on your page so search engines know exactly what they're reading. Google uses this data to populate local Knowledge Panels, show dish names in search listings, and surface your menu in Maps. Google's own guidance recommends structured data for restaurants. It doesn't guarantee rankings, but it makes your menu eligible for far more visibility than plain text alone.
My designer said the PDF looks better — is that true?
A PDF can preserve your original print design, which looks polished if someone downloads and opens it. But on a mobile browser — where most of your customers are — a PDF is usually a pain to open, slow to load, and impossible to zoom and navigate easily. A well-designed HTML menu page looks just as good, loads instantly, and is the only version Google can actually read. Looks versus function is the wrong trade-off here.
How long does it take to rebuild a menu as proper HTML text?
For a standard takeaway or restaurant menu, a couple of days of development work at most. At Takely, rebuilding your menu as structured text with schema markup is included in every package — Starter (£499 + £49/mo) upwards — and the whole site goes live within 7 days. You send us your current menu in whatever format you have (even a photo), and we rebuild it properly.
Will fixing my menu SEO immediately get me to the top of Google?
No, and anyone who says otherwise is selling something. Fixing an invisible menu removes a significant barrier to being found — Google can finally read and index what you sell. Combined with a linked Google Business Profile, local landing pages, and consistent NAP data, it builds the right foundation over time. We say built to get you found, not guaranteed number one, because that's the honest answer.
What if I update my menu prices — does that mean rebuilding the whole site?
No. When your menu is built as real text on the page, a price or dish update is a standard content edit. At Takely, that's covered by the monthly plan (from £49/mo) — email us the change and it goes live. No new PDFs, no re-uploads, no photography. Much simpler than managing a PDF version.
Keep reading