Zomato menus and listings on any food site.

Many restaurant operators mix these up, so let us be precise. A Zomato reviews widget shows your star rating, individual customer reviews, and the Reviews count. It exists to build trust on a single restaurant page using social proof. A Zomato feed widget (this one) does something different: it shows live menu items, the full restaurant listing record (cuisine type, price for two, opening hours, location pin, neighborhood, average waiting time, parking notes), and the customer-uploaded food photo gallery, optionally aggregated across multiple restaurants in one feed. The feed widget is the right choice when your goal is to display what is on the menu, surface dish photos in a discovery layout, build a city guide of many restaurants, or earn placements in Google's food and dish-level rich results. The reviews widget answers the question is this place good. The feed widget answers the question what should I order and what does it cost. Most chains and editorial sites need both widgets eventually: reviews for the trust story, the feed for the menu and discovery story. They install side by side, and Poper bundles them with the same one-line snippet so you do not pay double, do not load two scripts, and do not duplicate Schema.org data. As a rule of thumb: if you operate fewer than 5 restaurants, start with reviews. If you operate 5 or more outlets, run a food blog covering 20 plus restaurants per post, or publish destination guides, start with the feed widget. Most chains add the second widget within 60 days of installing the first.

Zomato closed its public Developer API to new partners in 2020. If you applied after that date, you were almost certainly told that the program is deprecated and not accepting new applications. Menu and listing data face an extra wrinkle: even legacy partners have rate-limited menu refresh, and Zomato actively discourages bulk menu mirroring outside its own delivery and aggregation surface. Three honest paths exist for a Zomato feed widget today. First, legacy partner API access for tools that secured keys before the cutoff. Second, the official Zomato single-restaurant embed, which is a static iframe with no menu data, no aggregation, and no customization. Third, compliant scraping that respects robots.txt, observes rate limits, caches aggressively at a CDN edge, and never violates Zomato's terms of service. Poper supports the path available for your region and listing type, and the dashboard tells you which one is active. We do not promise live menu sync we cannot honestly deliver. If your only option is a daily-refresh cached feed plus the static official widget, we tell you upfront. If Zomato reopens API access in your market, we ship support within a release cycle.

Google's food and recipe carousels are a high-intent, low-competition real estate that most restaurant websites never claim, because adding the schema by hand is tedious and brittle. The required JSON-LD is a Restaurant entity (with name, address, servesCuisine, priceRange, telephone, openingHours) plus a Menu entity (with hasMenuSection for each category like Starters, Mains, Desserts, Beverages) plus a MenuItem for every dish (with name, description, offers.price, offers.priceCurrency set to INR or AED or IDR for the relevant market, image, suitableForDiet for vegan or halal or jain dishes, and nutrition where available). Done correctly, queries like best paneer tikka in Connaught Place, top butter chicken Bandra, biryani delivery near me, or shawarma Karama Dubai can surface your individual dishes with photo, price, and a link directly into your menu page. For Indian metros and Gulf cities where cuisine-plus-locality search volume is enormous and growing 30 percent year over year (per Google India insights), the upside is real and largely uncontested today. Adding the schema by hand requires a developer to maintain a JSON-LD block per dish, refresh it every time the menu changes, and validate it after every Google crawl rule update. Most restaurant operators try this once, watch it break inside 6 weeks, and give up. Poper auto-injects MenuItem schema for every dish in your embedded feed on every plan including Free, refreshes it on the same cadence as the menu data, and validates against Google's Rich Results Test on every deploy. Within 1 to 4 weeks of crawling, dishes commonly start appearing in carousels for branded plus generic queries. Track the lift in Google Search Console under Performance, filter by Search appearance, and look for Recipe or HowTo entries growing.

Zomato's official widget embeds one restaurant at a time. That works for a single restaurant page. It does not work when a food blogger wants to feature 50 best vada pav joints in Mumbai, when Time Out wants a city-guide of 200 vetted restaurants per metro, when a travel site wants to embed every restaurant on a Goa beach itinerary, when a chain like Theobroma, Chai Point, or Wow! Momo wants to surface all 80 plus outlets on their about page, or when a corporate cafeteria aggregator wants to show what 30 partner restaurants are serving today. Aggregation is where the Poper Zomato feed widget unlocks an entirely new content surface. Connect listings in bulk via CSV upload (one Zomato URL per row, or a name plus city pair if URLs are not handy), assign filter tags (cuisine, neighborhood, price range, vegan, halal, jain, gluten-free, alcohol-served, dog-friendly, parking, valet), and the widget renders the combined feed with optional filtering controls for visitors. The City Guide layout was built specifically for this use case and pairs naturally with destination-style editorial content. Multiple sort modes ship out of the box: by rating, by price, by recently updated menu, by alphabetical, by distance from a viewer-supplied location, or by editor-pinned ranking. The bulk import is one of the biggest reasons food media outlets switch from manually maintained restaurant directories (which go stale within weeks because menus change and outlets close) to a Zomato feed widget (which never goes stale because menu and listing data refresh from Zomato on a 30-minute or 6-hour cadence). For chain operators, the aggregated AggregateRating in the Schema.org markup also covers the brand as a whole, which tends to outrank individual outlet pages in branded searches and helps you reclaim your own brand SERP from Zomato itself, Swiggy listings, and third-party blog roundups.

Zomato has evolved well beyond restaurant discovery. The 2017 launch of Zomato Gold (rebranded to Zomato Pro and then folded into the broader Zomato ecosystem) reshaped the dine-in subscription economy in India and rewired what kinds of dishes get photographed: subscribers tend to favor visually distinct, share-worthy plates that stack a photo gallery in your favor over time. The 2021 IPO at INR 9,375 crore made Zomato the first Indian unicorn to list publicly, putting structural pressure on the platform to maintain high-quality menu data, crack down on fake or stale photos, and tighten restaurant verification. Hyperpure, Zomato's B2B ingredient supply arm, now stocks tens of thousands of restaurants and cloud kitchens, increasing the importance of supply-chain storytelling on restaurant brand sites. For Zomato feed widget operators in 2026, four implications matter. First, the customer food-photo library is deeper and more current than ever, particularly across India and the Middle East where uploading dish photos is a default behavior of every diner with a smartphone. The photo mosaic and magazine layouts capitalize on this directly, surfacing fresh customer photography that no studio photographer could match for authenticity or volume. Second, menu data is more reliable post-IPO, but cloud kitchens, virtual brands, and dark-store restaurants now rotate menus more aggressively (sometimes weekly), so a real-time feed beats a manually copied menu page every time. Third, Hyperpure-related sourcing claims pair beautifully with menu items in Schema.org descriptions (think organic, farm-to-table, ethically sourced) to tell a complete supply-chain story that Google and conscious diners both reward. Fourth, the Indian quick-commerce convergence (Blinkit is owned by Zomato, Instamart by Swiggy, Zepto independent) means a restaurant brand site now competes with grocery and ready-meal delivery for the same dinner-decision query. A modern Zomato feed widget on a 2026 website is not just a menu list. It is a live, photo-rich, schema-marked storefront that pulls Zomato's structural data advantage directly into your own domain, helping your brand site win the dinner-decision query against quick-commerce, third-party blogs, and Zomato itself.