TripAdvisor restaurant URL discovery

Turn a TripAdvisor city restaurants page into a clean list of restaurant profile URLs — name when listed, ready to enrich.

Paste the listing URL from your browser (New York, Paris, London…). The Actor walks public pages and saves unique restaurant profiles.

No login. No API key. No TripAdvisor account.

Pair with TripAdvisor restaurant details to add phone, email, hours and ranking.

---

Also available

Actor	Use when
This Actor — discovery	You have a city / neighborhood listing URL and need profile links
TripAdvisor restaurant details	You already have Restaurant_Review URLs and need contacts
Booking Pro Host	Hotel / apartment host contacts on Booking.com

---

Who is this for?

You are…	Typical goal	Suggested setup
Outbound / SDR	Build a restaurant URL list for a city before enrichment	One city URL · Max listing pages 5
CRM / RevOps	Feed profile URLs into the details Actor	Discovery first, then details on the same url column
Market research	Sample restaurants in a destination	Max listing pages 1, then raise coverage
Agency / local SEO	Map competitors on TripAdvisor in one territory	Neighborhood or city listing URL
Data / ops	Recurring city snapshot	Scheduler · maxPages: 0 until the list ends

What you get by default: unique url, name when TripAdvisor lists it, the listing page it came from, pagination offset.

When to raise coverage: increase Max listing pages. Set 0 to keep going until a page has no new restaurants.

Typical yield: one New York listing page returns ~90 unique restaurant profile URLs.

---

Quick start

1. Open TripAdvisor → Restaurants → copy the city URL
2. Paste it in Restaurant listing URL(s)
3. Leave Max listing pages at 1 for a first run, then 5
4. Click Start
5. Export CSV/JSON, or pass url into TripAdvisor restaurant details

---

Ready-made examples

Sixteen city presets are saved as Console tasks (New York, Paris, London, Barcelona, Rome, Los Angeles, Miami, Chicago, Berlin, Amsterdam, Lisbon, Dubai, Tokyo, Singapore, Sydney, plus New York × 5 pages). They appear on the Store Examples tab after each task is published.

Until then, paste any city restaurants URL — New York is the Console prefill.

---

What does it produce?

Field	Meaning
url	Restaurant profile (Restaurant_Review)
name	Name when listed on the city page
listingPageUrl	The listing page this URL was collected from
pageOffset	Pagination offset (0, 30, …)

One row per unique restaurant URL. Dataset view: Restaurant URLs.

---

How much does it cost to scrape TripAdvisor restaurant URLs?

HTTP-only. You pay pay-per-event per unique restaurant URL — this is a URL list, not a full contact row. Official Tripadvisor listing scrapers charge about $2.90 / 1k (Bronze) to $5 / 1k (FREE) for richer listing rows. This Actor is $1 / 1k on FREE.

Scenario	FREE	Bronze	Silver	Gold
1 listing page (~90 URLs)	~$0.09	~$0.08	~$0.07	~$0.06
5 listing pages (~400 URLs)	~$0.40	~$0.36	~$0.32	~$0.28
1,000 URLs	$1.00	$0.90	$0.80	$0.70

Feed url into TripAdvisor restaurant details for emails and phones (billed separately). Residential proxy is not required by default.

---

Is it legal to scrape TripAdvisor restaurant listings?

This Actor only reads public city restaurant listing pages (the same HTML a visitor can open without an account). It does not log in.

You are responsible for TripAdvisor terms and privacy law when you enrich those URLs (phones and emails) with the details Actor. See Apify's guide to web scraping legality.

---

Input

Console: paste listing URL(s) and set Max listing pages.

{
  "startUrls": [
    "https://www.tripadvisor.com/Restaurants-g60763-New_York_City_New_York.html"
  ],
  "maxPages": 3
}

Parameter	Console	Default	Description
startUrls	Yes	—	City restaurants listing URLs
maxPages	Yes	5	Pages per URL (0 = until the list ends)
pageStep	Hidden	30	Restaurants per listing page
delayMsBetweenPages	Hidden	800	Pause between pages (ms)
resume	Hidden	false	Skip URLs already in the dataset
proxyConfiguration	Hidden	no proxy	Optional backup
verboseLogs	Hidden	false	Extra diagnostics
navigationTimeoutSecs	Hidden	60	Wait per page

---

Output example

{
  "url": "https://www.tripadvisor.com/Restaurant_Review-g60763-d425330-Reviews-Keens_Steakhouse-New_York_City_New_York.html",
  "name": "Keens Steakhouse",
  "listingPageUrl": "https://www.tripadvisor.com/Restaurants-g60763-New_York_City_New_York.html",
  "pageOffset": 0
}

---

How it works

1. You paste a public city restaurants URL
2. The Actor reads each listing page and collects unique restaurant profile links
3. Names are saved when TripAdvisor shows them
4. Pass url into TripAdvisor restaurant details for phone, email and hours

---

Local development

npm ci
node --test tests/*.test.js
apify run --input-file=./published-tasks/inputs/01-new-york-restaurant-urls.json

Requires Apify CLI.

---

FAQ

City listing or restaurant profile? This Actor needs /Restaurants-g… (or equivalent city list). Profile pages belong in the details Actor.

Do I need a proxy? Not for typical city pages. Pass proxyConfiguration in JSON only if a run returns no restaurants.

How many URLs per page? About 70–90 unique profiles on a New York page in recent runs.

---

Support

Issues tab, or corentin@outreacher.fr for a custom scraper or integration.