Google Restaurants API: Transmitting Menu Data Directly to Google
Most restaurant operators know that Google Business Profile (GBP) is important. Very few know that GBP has an API that allows complete, structured menu data to be transmitted directly to Google — not as text, but as machine-readable datasets that Google incorporates directly into its Knowledge Graph.
This API — officially the Google Business Profile Food Menus API (GBP FoodMenus v1) — is the most direct route to making your restaurant visible in Google Gemini, Google AI Overviews and voice assistant-based recommendations. And chiwai is one of the few platforms that implements this push fully automatically for every restaurant operator.
→ AI Visibility Hub
→ Google AI Overviews for Restaurants
What the Google Food Menus API Is
The Google Food Menus API is a programming interface that allows restaurants and platforms to feed structured menu data directly into Google Business Profile. Unlike the manual entry of dishes through the GBP interface, the API enables the fully automated, structured transmission of:
- Categories: starters, main courses, desserts, beverages
- Individual dishes: name, description, price
- Nutrition information: calories, protein, fat, carbohydrates
- Allergen data: all 14 EU allergens per dish, machine-readable
- Dietary attributes: vegan, vegetarian, halal, gluten-free
- Images: high-resolution photos per dish
The API transmits this data in a structured format that Google understands directly — without interpretation, without guessing. The result: your GBP profile becomes a complete, machine-readable restaurant database that Google Gemini and AI Overviews can directly use.
Why the Direct API Push Is Critical
There are three ways to transmit menu data to Google:
Method 1 — Manually via GBP interface: You type dishes individually into the Google Business Profile interface. No structured format, no allergen metadata, time-consuming, error-prone and requiring manual repetition for every menu change.
Method 2 — Website Schema.org markup: Google crawls your website and reads the Schema.org JSON-LD markup. Better than Method 1, but dependent on the crawl cycle — Google sees changes only when it next crawls your page (days to weeks delay).
Method 3 — GBP Food Menus API push: Structured menu data is transmitted directly via API to Google. No waiting for crawl cycles. Google processes the data within 24-72 hours. The result is immediately visible in GBP and available for Gemini.
Method 3 is the gold standard — and the path chiwai takes automatically.
→ Google Business Profile and AI
The Data Structure: What Google Expects
The GBP FoodMenus API follows a defined schema. For optimal AI visibility, every dish must contain these fields:
MenuItem {
displayName: "Kung Pao Chicken"
description: "Classic Sichuan dish with tender chicken..."
price: { currencyCode: "EUR", units: 16, nanos: 500000000 }
allergens: [PEANUTS, SOY, GLUTEN_FREE_CLAIM_FALSE]
nutrition: {
calories: { lowerAmount: 380, upperAmount: 420, unit: KCAL }
protein: { lowerAmount: 28, upperAmount: 32, unit: GRAM }
}
dietaryRestriction: [HALAL]
attributes: { isVegetarian: false, isVegan: false }
}This structure is what Google incorporates directly into the Knowledge Graph. When a user asks „Which peanut-free dishes does China Restaurant YUNG have?“, Google can answer immediately and precisely based on this data — because the data is read directly, not interpreted.
The chiwai Process: From Invoice to API Push
chiwai automates the entire journey from supplier invoices to GBP API push in a continuous workflow:
Phase 1 — Capture: The restaurant operator uploads supplier invoices or label photos into chiwai. AI automatically identifies: product name, ingredients, quantities.
Phase 2 — Analysis: chiwai calculates allergens (all 14 EU allergens) and nutrition facts (calories, macronutrients per serving) based on the German Federal Food Key and EAN databases.
Phase 3 — Structuring: A complete MenuItem dataset is created for every dish — compatible with Google Food Menus API requirements.
Phase 4 — Push: Structured data is transmitted directly via GBP FoodMenus v1 API to the restaurant’s Google Business Profile.
Phase 5 — Verification: chiwai checks whether the push was successful and reports errors or missing data to the operator.
The entire process runs without manual intervention from the restaurant operator. A menu change — a new dish, a price change, a modified recipe — automatically triggers a new push.
Which AI Systems Use GBP Data
After a successful GBP FoodMenus push, the following systems use the data:
Google Gemini: Accesses GBP data directly when users ask about restaurants in Google Search. Complete menu data enables Gemini to include specific dishes, prices and allergens in responses.
Google AI Overviews: Uses GBP data as a trustworthy source for restaurant-related queries. Restaurants with complete GBP menu data are cited more frequently as sources.
Google Maps: Displays menu data directly in the GBP panel when users click on a restaurant in Maps — with dishes, prices and allergens in the app.
Google Search Knowledge Panel: The information panel on the right side of search results is enriched with structured GBP data and can display individual dishes.
Google Assistant: Voice-based queries like „Hey Google, which gluten-free dishes does China Restaurant YUNG have?“ are answered directly from GBP menu data.
The Competitive Advantage: API Users Win
The adoption rate of the GBP Food Menus API among restaurants is below 1% globally. This means: virtually all of your competitors do not have this data at Google. Restaurants that activate the API push therefore have a massive competitive advantage for all AI-supported queries.
This advantage is time-limited. As more restaurants build structured data, competition for AI Overview positions will intensify. Early adopters build authority that later newcomers will find difficult to displace.
FAQ
Does using the Google Food Menus API cost anything?
The Google Food Menus API itself is free — Google provides it to restaurants and certified platforms without direct usage fees. The challenge lies not in API costs but in data preparation: menu data must be in the correct structured format, with allergen and nutrition data per dish. This preparation effort is substantial when done manually. chiwai handles exactly this process — data preparation, formatting and API push are included in the platform price.
Can I enter my menu directly in the GBP interface instead of using the API?
Yes, the GBP interface allows manual entry of dishes. The downside: the manual interface does not support structured allergen data, nutrition information or automatic updates for menu changes. For AI visibility you need precisely this structured data — which is why the API push is fundamentally superior to manual entry. Restaurants that combine both — basic manual data in the GBP interface plus structured depth data via API — have the most complete profiles.
What happens when I change my menu?
With chiwai, every menu change is automatically executed as a new API push. When a dish is removed, a price is changed or a new dish is added, chiwai updates the GBP profile automatically — typically within 24 hours of the change in the chiwai platform. Without this automated process there is a risk of outdated data: Google still shows dishes that no longer exist or incorrect prices — which leads to negative guest experiences and loss of trust.