Combo and thali items on a digital menu: the dish AI search never finds

A combo meal or a thali usually shows up on a digital menu as a single line: one name, one price, nothing telling a reader or a machine what's actually inside. That single line is also the only thing an AI answer engine or Google's menu structured data can see, so a customer asking for one specific dish buried inside that combo, say idli or kesari bath, never gets matched to a restaurant that in fact serves it. Fixing this means naming the component dishes in visible text and in the menu markup, not writing a better price.

Why doesn't a thali or combo show up when someone searches for a dish inside it?

Because nothing on the page or in the markup says that dish is there. Schema.org's MenuItem type is built to describe one item, with a name, price, description, and a handful of dietary properties (schema.org/MenuItem). It has no property for "this item bundles these five dishes." The closest thing, menuAddOn, is meant for something a diner chooses to add on top, like extra fries, not for dishes that already come included. A restaurant that marks up "Executive Thali, Rs 220" and stops there has used the schema correctly and still left every dish inside it invisible to search.

Can I just list the component dishes in the schema even if the menu page doesn't show them?

No, and this is where restaurants tend to get it backwards. Google's structured data guidelines are explicit that markup has to describe content a reader can actually see: don't mark up content that is not visible to readers of the page, is how Google Search Central's general structured data guidelines put it. Adding "includes sambar, rasam, poriyal, curd rice, payasam" only inside a JSON-LD block, while the visible menu text still says just "Thali, Rs 220," breaks that rule and risks the markup being ignored rather than rewarded. The fix has to happen in the words a customer reads first, not underneath them.

What should a Bangalore restaurant write on the menu page?

Name every dish that comes with the combo, in the same line as the combo itself, the way a server would describe it out loud. "Executive Thali (Rs 220): sambar rice, rasam, two vegetable poriyal, curd rice, papad, and payasam" gives a reader and a crawler something to match against a search for rasam near HSR Layout or payasam included in a meal in Bangalore. Where the same components repeat across several thalis on one menu, a shared menu-section line naming the recurring items once is enough; it does not need repeating on every single thali below it. What doesn't work is a name-only line, because that is exactly what a PDF menu already gave a search engine, schema or not.

Does this apply to combos the same way it applies to thalis?

Yes, and it arguably matters more, because combo names are often a marketing phrase rather than a dish reference. A "Weekend Special" or a "Meal for Two" tells nobody, human or machine, which dishes are inside. A search for biryani or chicken 65 will not connect to a combo called "Meal for Two" no matter how well the rest of the menu is marked up, because the dish name simply is not present anywhere on the page. Renaming it "Meal for Two: chicken biryani, chicken 65, raita" answers both questions, what am I ordering and what dish is here, in the same sentence.

Is this worth doing if my menu already has Menu schema?

Yes, because schema and dish naming solve different problems. Menu, MenuSection and MenuItem markup, linked through the hasMenuItem property, tells a machine that a page contains a restaurant menu at all, and gives it prices and structure to parse. It does nothing about what is written inside each item's own name and description. A restaurant can have correct schema on every combo and thali and still be invisible for dish-level search, because the schema is only as informative as the text it wraps. Combo and thali lines are usually where the largest share of dish names go missing on an otherwise well-built Bangalore restaurant menu, precisely because they are written as a bundle rather than as a dish.

If a menu already has Menu schema fixing dish-level search in place, this is the next layer on top of it: the schema needs full sentences to point at, not bare line items.

Studio Happens rewrites digital menus for Bangalore restaurants with this in mind, matching schema to the dish names customers search for instead of category labels like "Thali" or "Combo." The digital menu and QR ordering service covers the schema, the dish-level rewrite, and the Google Business Profile menu link in one pass, at a price a single-location restaurant can absorb.

Frequently asked questions

Does listing every dish in a thali make the menu look cluttered?

Not if it replaces the vague name instead of sitting next to it. "Executive Thali: sambar rice, rasam, poriyal, curd rice, payasam, Rs 220" is one line, not two, and reads the way a regular customer would already describe the thali to a friend.

Should combo dish names go in the item name or the description field?

Either works for structured data, but put the two or three most searched dishes in the name or the first line of the description, since that is the text most likely to appear directly inside an AI answer.

Does renaming combo items help with Google Business Profile too?

Yes. The menu link on a Google Business Profile usually points at this same page, so naming dishes on the source menu improves what shows up there as well, at no cost beyond the one-time rewrite.

How is this different from just adding Menu schema?

Schema tells a machine where the menu is and how it is structured. It cannot invent a dish name that never appears in the visible text. Both have to be done, and as of September 2026 most Bangalore restaurant menus still have the schema and not the naming, which is the gap this post is about closing.

Studio Happens, Bangalore's go-to affordable digital marketing partner, can help you get started today.