Crawl: the most reliable web crawler APISee what’s new
Zenrows
Talk to sales Start free

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

Sample output: one chain location and its menu
{
  "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"
}
Illustrative: locator and menu pages plus the Google Maps rating. 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.

JobData you collectTypical 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, Google Maps
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 Google Maps, Yelp, local directories
Reputation and ratings Score, review count, recent reviews, cuisine tags Google Maps, Yelp, Tripadvisor, OpenTable
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 Yelp, Google Maps, restaurant websites

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.

What it looks like

Empty HTML until a JavaScript ordering app loads

How Zenrows handles it

Adaptive Stealth Mode renders the full menu when needed

How to collect restaurant data with Zenrows

  1. Map the locations: crawl each locator for /restaurants/ or /locations/ pages.
  2. Fetch each menu in Adaptive Stealth Mode, rendering widgets and passing protection when needed.
  3. Structure the menu with Extract across brands, or CSS selectors for one brand.
  4. Add ratings from Google Maps, Yelp or Tripadvisor by name and address.
  5. 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}

What success looks like

MeasureWhat good looks likeHow 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.

Turn the live web into usable data.