Restaurant data
Restaurant data covers locations, opening hours, menus, item prices, ratings and delivery availability for restaurants and chains. Zenrows collects it from chain websites, store locators, Google Maps, Yelp, Tripadvisor and delivery apps, protected and JavaScript-heavy pages included, and returns structured menu and location records for competitive intelligence and market analysis.
Updated
{
"brand": "Example Pizza Co.",
"store_id": "ld-0417",
"address": "12 Example High Street, Leeds LS1 0XX, UK",
"lat": 53.7974,
"lng": -1.5438,
"status": "open",
"first_seen": "2026-09-02",
"hours": { "mon_thu": "11:00-23:00", "fri_sat": "11:00-00:00", "sun": "12:00-22:00" },
"services": ["dine_in", "collection", "delivery"],
"currency": "GBP",
"menu": [
{ "category": "Pizzas", "item": "Margherita, large", "price": 15.99, "calories": 2010, "new": false },
{ "category": "Pizzas", "item": "Spicy honey pepperoni, large", "price": 18.49, "calories": 2380, "new": true },
{ "category": "Sides", "item": "Garlic bread", "price": 5.49, "calories": 640, "new": false },
{ "category": "Deals", "item": "Two large pizzas and a side", "price": 32.0, "calories": null, "new": false }
],
"rating": { "source": "google_maps", "score": 4.3, "count": 1286 },
"scraped_at": "2026-10-17T04:30:00Z"
}
first_seen and new come from diffing runs.What restaurant data teams collect
Brands, suppliers, delivery platforms and analysts share one unit, a location with its menu and rating, and ask different questions.
| Job | Data you collect | Typical sources |
|---|---|---|
| Competitor menu and price tracking | Items, sizes, prices, deals, calories per location | Chain sites, ordering pages |
| Store openings and closures | Locations, address, coordinates, status, first and last seen | Store locators, |
| New product launches | Items added or removed, limited-time offers | Chain menus diffed weekly |
| Site selection and white space | Density by cuisine and brand per trade area or postcode | |
| Reputation and ratings | Score, review count, recent reviews, cuisine tags | |
| Delivery presence | Which locations deliver, on which apps, at what price | Uber Eats, DoorDash, Grubhub, Deliveroo (see food delivery data scraping) |
| Sales leads for suppliers | Independents: cuisine, size, contact page |
Why restaurant menu scraping breaks
One menu is easy.
Across hundreds of stores, prices vary, ordering widgets draw menus in the browser, and rating directories are protected.
Empty HTML until a JavaScript ordering app loads
Adaptive Stealth Mode renders the full menu when needed
The same item costs more at an airport or city centre
Fetch each store's menu; store_id on every price
Spread over city, region pages and map tiles
Crawl follows the locator, keeping matching store pages
CAPTCHAs from protections like DataDome
Zenrows' stealth gets through DataDome, Cloudflare and similar
Independents post a scanned menu, not HTML
Output filters collect PDF links; screenshots capture images
Per-chain selectors break on redesigns
Extract returns items and prices, no per-brand selectors
How to collect restaurant data with Zenrows
- Map the locations: crawl each locator for
/restaurants/or/locations/pages. - Fetch each menu in Adaptive Stealth Mode, rendering widgets and passing protection when needed.
- Structure the menu with Extract across brands, or CSS selectors for one brand.
- Add ratings from Google Maps, Yelp or Tripadvisor by name and address.
- Diff every run to flag openings, closures, launches and price changes.
# Collect every store page from a chain's locator
curl -X POST "https://api.zenrows.com/v1/crawls" \
-H "X-API-Key: YOUR_ZENROWS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "STORE_LOCATOR_URL",
"max_items": 2000,
"max_pages": 2000,
"include_patterns": ["/restaurants/"],
"exclude_patterns": ["/careers/", "/news/"]
}'
# Omitting output_format returns URLs only. Read them with
# GET https://api.zenrows.com/v1/crawls/{crawl_id}# pip install requests
import json
import requests
# Example selectors: match them to the brand's menu page
params = {
"apikey": "YOUR_ZENROWS_API_KEY",
"url": "STORE_MENU_URL",
"mode": "auto", # Adaptive Stealth Mode renders the ordering widget when needed
"css_extractor": json.dumps({
"category": ".menu-section h2",
"item": ".menu-item .item-name",
"price": ".menu-item .item-price",
"calories": ".menu-item .item-kcal",
}),
}
menu = requests.get("https://api.zenrows.com/v1/", params=params).json()
print(menu)npx -y @zenrows/cli init
# Every store page behind a chain's locator
zenrows crawl create STORE_LOCATOR_URL --include-patterns /restaurants/ --max-pages 1000 --follow
# Structured menu items from any brand's menu page, no selectors
zenrows extract STORE_MENU_URL --autoparse# Connect once
claude mcp add zenrows -e ZENROWS_API_KEY=YOUR_ZENROWS_API_KEY -- npx -y @zenrows/mcp
# Then ask:
Use Zenrows to extract every item, price and calorie count from STORE_MENU_URL, grouped by menu section, then add the same store's Google Maps rating and review count. Return one JSON record with the store address.Which Zenrows product fits
- List every location of a chain CrawlFollows the store locator and returns store URLs
- Read one menu with your own fields FetchRenders the widget, returns your CSS selector fields
- Collect menus across many brands ExtractItems and prices as JSON, no per-brand selectors
- Pull menus or ratings from terminal or cron CLIOne command, ready to pipe
What success looks like
| Measure | What good looks like | How to check it |
|---|---|---|
| Location coverage | Stores per brand match the brand's locator | Unique store_id per brand against the locator total |
| Menu completeness | A current, fully priced menu per location | Unpriced items per brand per run |
| Change detection lead time | Openings, closures and launches within one refresh | first_seen against the brand's announcement date |
| Per-location price fidelity | Local price differences kept | Hand-check stores across areas |
| Stakeholder trust | Marketing, property and operations use the feed unchecked | Corrections requested per month |
Restaurant data FAQ
-
Structured information on restaurants and chains: names, brands, addresses, coordinates, hours, cuisine, priced menus with calories, delivery or collection, ratings and reviews. Brands, food suppliers, delivery platforms, investors and real estate teams use it for pricing, site selection, sales and market analysis.
-
Get each menu URL from the store locator and fetch it with Adaptive Stealth Mode, which renders most chains' ordering widgets. Read items and prices with CSS selectors or Extract, per location: many chains price by store.
-
Best from the brand's own site and ordering pages, where prices are set. Uber Eats and DoorDash menus can carry a mark-up. Google Maps, Yelp and Tripadvisor add ratings, hours and photos, not priced menus.
-
Yes. Menus render with JavaScript and depend on the address: set it first, with page actions or a Browser session. See food delivery data scraping for address-based pricing, fees and delivery times.
-
Crawl each locator on a schedule, storing store IDs with first and last seen dates. A new ID is an opening; one missing two runs in a row, a likely closure. Google Maps flags some closures too.
-
Crawl each chain's store locator (address, hours, services, store ID) and extract matching store pages as JSON. For independents, search Google Maps or Yelp by city and cuisine, add coordinates and ratings, deduplicate by address.
-
Menus, prices, addresses and hours are public and widely collected for research. Do not republish reviews or photos; reviewer names are personal data. Check site terms and your use with your legal team.