Google Business Profile's AI menu feature, and its limits

You take a photo of your laminated menu, upload it to Google Business Profile, and Google hands you back a structured menu — item names, prices, sections, done. No typing, no formatting, no manually fixing the arancini price for the third time this year.

That's the pitch behind a quietly significant addition to Google Business Profile: an experimental AI feature that reads a photo — or now a multi-page PDF — of your printed menu and turns it into a real, structured menu on your listing. If you run a cafe, restaurant, bar or food truck, it's important to understand exactly what this does before you lean on it, because "Google wrote it" and "Google wrote it correctly" are two different claims.

Why this actually matters

Your menu is one of the most-clicked things on a Google Business Profile. Before this feature, you had two options: drop a Menu URL that points people off your listing to a PDF or a page, or hand-type every item into GBP's structured menu editor — which is tedious enough that most owners set it up once and then let it drift out of date.

The AI tool removes the typing barrier. But the output still represents your business, in public, on the search engine most of your customers actually use to decide where to eat. Getting it slightly wrong isn't cosmetic. It's a customer expecting a $14 dish that's quietly become $16, or a menu with no gluten-free or vegan markers at all because that data was never in the photo to begin with.

How the feature actually works

The flow, as covered by Search Engine Land and Search Engine Roundtable: open the GBP dashboard, go to Edit menu, choose "Photos of menu," upload your image, then hit "Generate a menu." Google reviews the photo and proposes a structured menu with section headers, item names, descriptions and prices. You then land on a review step — you can edit anything before choosing "Publish and edit." It is not autonomous. Nothing goes live without you looking at it first, which is worth knowing before you assume Google is quietly rewriting your listing in the background.

The feature rolled out in an initial form around April–May 2026, and at that point it only accepted a single photo — a genuine limitation if your printed menu ran to more than one page. A later update removed that cap and added support for multi-page PDF menus, along with better recognition of headers, item names and prices.

One detail that's easy to miss: using it means opting into Google's separate Generative AI Additional Terms of Service, not the standard Business Profile terms you already agreed to when you claimed your listing. Most owners clicking "Generate a menu" are very unlikely to read what they've just agreed to — which is fine until it isn't, but it's worth knowing it's a distinct agreement, not a checkbox inside the feature you already trust.

It's also useful to separate two things GBP has always had. There's the simple Menu URL field, which just links out to whatever menu page or PDF you've hosted elsewhere. And there's the Structured Menu Editor, which renders items directly on your listing and Maps card. The AI feature populates the second one — it's writing directly into the part of your profile Google displays inline, not just adding a link.

What it's genuinely good at

The upside is real, and it's an SEO one. A photo of a menu is just pixels to Google — it can't match "mushroom arancini" to someone searching for mushroom arancini nearby. A structured menu can. Individual dish names and prices become search-matchable content sitting directly on your profile, which a flat image never was. Even a rough first pass at that structure is worth having, provided you're the one who checks it before it goes live.

What to double-check before you trust it

A menu photo isn't a data structure — it's a photo. Turning it into one is exactly the kind of task where small, confident-looking errors slip through, and this is where they'll show up if you skip the review step:

• Google labels it experimental. That's Google's own status flag on the feature, not marketing caution — it means no quality guarantee, and Search Engine Roundtable's own trade coverage described the early version as experimental and, in their words, buggy.
• It only reads what's on the page. The single-photo limit at launch meant a genuinely multi-page menu simply didn't fit — a structural gap, not a rare edge case, for any venue with more than one page of items.
• Editing happens after the fact, not before. You don't get to tell it how to group or describe your dishes up front — you get to fix what it produced. That review screen is doing real work; treat it as a proofread, not a formality.

One more thing worth saying clearly, because it's easy to conflate: there's separate reporting about Google's AI Overviews showing incorrect business information with no easy way for an owner to correct it. That's a different Google AI system entirely — AI Overviews sits inside general search results, not inside your GBP menu editor — and it isn't evidence that the menu feature itself is unreliable. Worth knowing about, but not something to pin on the wrong tool.

None of the above makes the feature useless. It makes it a first draft, not a finished menu — and the review screen is where that draft becomes reliable or doesn't. Before you tap "Publish and edit," walk the generated menu against the physical one, line by line, and don't skip past any of these:

• Every price, checked against the printed menu — a misread character turns $16 into $18, and that's the number your customer holds you to when the bill arrives, not the number the tool guessed. Read straight down the generated list against your printed one before you approve anything.
• Section groupings, sanity-checked — confirm dishes landed under headers you'd actually use, not wherever the tool's read of the page happened to place them. This is where a two-column or multi-section printed menu is most likely to come out wrong.
• Nothing merged or dropped — a printed menu with side notes, boxed specials, or a squeezed-in drinks list is exactly where an item goes missing, or two separate items get read as one line with one price. Count the generated list against the physical one, item for item, before you publish anything.
• Dietary and allergen tags, added manually afterward — GBP has a separate, optional field for dietary and allergen tags, and the AI extraction doesn't touch it. It reads names, prices and section headers off the photo — nothing more. Add it once the structure is right — exactly the kind of fix the review-and-edit step was built for, if you remember to make it.

Google can only read what's on the page you gave it; whether what comes out matches your actual business is still your call to make, every time you hit "Generate." Remember too that Google itself labels this experimental — checking it yourself is the difference between a first draft and a menu customers can actually trust.

This is also, at bottom, a Google feature sitting inside a Google product, not a page on a site you own — worth remembering when you're deciding how much of your menu strategy to build around it. We've covered the broader sequencing question of GBP versus your own website in more detail over here if you haven't settled that yet.

The honest pitch

If you want a menu page that's actually yours — structured, searchable, carrying the dietary and allergen details Google's tool skips, and live regardless of what Google rolls out or rolls back — that's exactly what FastPage builds for hospitality venues. No experimental flag, no separate terms to agree to, no one-page limit history. You can get started here and have a real menu page up in minutes, then let Google's AI tool do whatever it wants to your listing on top of that.