Tripadvisor Reviews Scraper avatar

Tripadvisor Reviews Scraper

Under maintenance

Pricing

from $0.55 / 1,000 reviews

Go to Apify Store
Tripadvisor Reviews Scraper

Tripadvisor Reviews Scraper

Under maintenance

Extract Tripadvisor reviews from hotel, restaurant, and attraction pages: ratings, full review text, dates, reviewer profiles, and owner responses. Paste listing URLs, set a limit, and export to JSON, CSV, or Excel. Useful for sentiment analysis, market research, and reputation monitoring.

Pricing

from $0.55 / 1,000 reviews

Rating

0.0

(0)

Developer

Automly

Automly

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Categories

Share

⭐️ What does Tripadvisor Reviews Scraper do?

Tripadvisor Reviews Scraper extracts reviews, ratings, review dates, reviewer profiles, and owner responses from public Tripadvisor hotel, restaurant, and attraction pages. Paste one or more listing URLs, set how many reviews you want per listing, and download the results as JSON, CSV, or Excel — no Tripadvisor account, no login, no browser automation.

Tripadvisor has no public reviews API, so if you need review data for sentiment analysis, reputation monitoring, competitor research, or hospitality market studies, scraping the public pages is the practical route. This actor does it with plain HTTP requests instead of a headless browser, which keeps runs fast (a 40-review run finishes in about 14 seconds) and compute costs low.

🧳 What data can I extract?

⭐️ Star rating per review📝 Review title + full text (not snippets)
📅 Published date and visit date🧑 Reviewer name, location, profile URL
💬 Owner / management responses with dates👍 Helpful votes and trip type
🏨 Listing name, type, and URL on every row🔗 Direct link to each review

🎯 Why scrape Tripadvisor reviews?

  • 📊 Sentiment analysis — build datasets of real guest opinions for NLP and brand monitoring
  • 🕵️ Competitor research — see what guests praise and complain about at rival hotels and restaurants
  • 📈 Reputation monitoring — track new reviews and rating trends over time with scheduled runs
  • 🏨 Hospitality market studies — compare review volume and sentiment across a whole neighborhood
  • 💬 Response auditing — check how (and how fast) managements respond to negative reviews

⬇️ How to use

  1. Open Tripadvisor Reviews Scraper in Apify Console and click Try for free.
  2. Paste one or more Tripadvisor listing URLs into Start URLs. Any public listing page works — hotels, restaurants, or attractions. Copy the URL straight from your browser, for example:
    • Restaurant: https://www.tripadvisor.com/Restaurant_Review-g60763-d425787-Reviews-Katz_s_Delicatessen-New_York_City_New_York.html
    • Hotel pages start with Hotel_Review-..., attractions with Attraction_Review-...
  3. Set Maximum reviews per URL (default 50, up to 500 per run).
  4. Leave Use Apify Proxy switched on. Tripadvisor blocks most datacenter IPs, so residential proxy is strongly recommended — add RESIDENTIAL to Proxy groups if your plan includes it.
  5. Click Start. Progress and any blocked-page warnings show up in the log.
  6. When the run finishes, open the Output tab for a clean review table, or download everything from the Dataset tab as JSON, CSV, or Excel.

⚙️ Input parameters

These match the actor's input schema. Only startUrls is required.

ParameterTypeRequiredDescription
startUrlsarrayYesTripadvisor listing or review page URLs to scrape.
maxReviewsPerUrlintegerNoMaximum reviews to save per start URL. Default 50, max 500.
includeReviewerProfilebooleanNoInclude public reviewer profile URLs. Default true.
includeOwnerResponsesbooleanNoInclude owner/management responses when visible. Default true.
sortBystringNoOptional Tripadvisor sort parameter appended to compatible URLs.
languagestringNoOptional locale hint for requests, e.g. en-US.
requestTimeoutSecsintegerNoPer-request timeout in seconds. Default 30.
useApifyProxybooleanNoRoute requests through Apify Proxy. Default true.
proxyGroupsarrayNoApify Proxy groups, e.g. ["RESIDENTIAL"]. Empty = automatic pool.

Example input:

{
"startUrls": [
"https://www.tripadvisor.com/Restaurant_Review-g60763-d425787-Reviews-Katz_s_Delicatessen-New_York_City_New_York.html"
],
"maxReviewsPerUrl": 100,
"useApifyProxy": true,
"proxyGroups": ["RESIDENTIAL"]
}

⬆️ Output example

Each review becomes one dataset item. This is real output from a run against the Katz's Delicatessen page:

{
"sourceUrl": "https://www.tripadvisor.com/Restaurant_Review-g60763-d425787-Reviews-Katz_s_Delicatessen-New_York_City_New_York.html",
"listingName": "Katz's Deli",
"listingType": "FoodEstablishment",
"reviewId": "1067274741",
"reviewTitle": "Go for the Pastrami - not for the social media post",
"reviewText": "OK, the Pastrami Tour roles on to continue to introduce the kid to the classics. This time, right to The Source...",
"rating": "5",
"publishedDate": "July 6, 2026",
"visitDate": "Jun 2026",
"reviewerName": "herb v",
"reviewerLocation": "West Amwell, New Jersey",
"reviewerProfileUrl": "https://www.tripadvisor.com/Profile/mastiffdad",
"helpfulVotes": "0",
"rank": "1"
}

Other fields you may see per item: listingUrl, reviewUrl, tripType, ownerResponseText, ownerResponseDate, and scrapedAt. Fields that aren't publicly visible on a given review are simply omitted — the actor never fills gaps with invented values.

💰 How much does it cost to scrape Tripadvisor reviews?

The actor runs on pay-per-usage pricing, and because it uses lightweight HTTP requests instead of a headless browser, usage stays small. Measured on real runs:

  • 1,000 reviews ≈ 0.37 compute units ≈ $0.15 in compute on the Apify Starter plan
  • Residential proxy traffic adds roughly 0.011 GB per 1,000 reviews ≈ $0.09
  • All-in: about $0.25 per 1,000 reviews on the Starter plan

Very small runs cost slightly more per review because the first page of each listing is always fetched; larger runs come in a bit cheaper per 1,000. The Apify free plan's monthly credit is enough to scrape several thousand reviews at no cost, so you can test before committing to anything.

🏨 Need hotel prices and inventory, not reviews?

Pair this actor with Booking.com Hotel Scraper — it extracts hotel names, nightly prices, guest ratings, and room types for a destination and dates. Together they give you both sides of the picture: what places charge and what guests say.

❓ FAQ

Do I need a proxy?

In practice, yes. Tripadvisor blocks most datacenter IP ranges outright. Keep Use Apify Proxy enabled and use the RESIDENTIAL proxy group for reliable results. The actor also recovers from blocks on its own: when a request returns HTTP 403 it rotates to a fresh proxy session with a different browser fingerprint and retries.

Which Tripadvisor URLs can I use?

Any public listing page: Hotel_Review-..., Restaurant_Review-..., or Attraction_Review-... URLs. Just copy the address from your browser while viewing the listing. Direct review-page URLs work too.

How many reviews can I scrape per run?

Up to 500 per start URL, and you can pass many URLs in a single run. Pagination is handled automatically. For larger ongoing collections, split listings across runs or set up a schedule.

What formats can I export?

The dataset can be downloaded as JSON, CSV, Excel, XML, or HTML from Apify Console, or fetched programmatically. The Overview table in the Output tab shows listing name, review title, rating, date, reviewer, and text at a glance.

Can I integrate it with other apps?

Yes. Through Apify integrations it connects to Google Sheets, Zapier, Make, Slack, LangChain, and more. Webhooks can notify your systems whenever a run finishes — the usual setup for reputation monitoring is a daily scheduled run plus a webhook into Slack.

Can I run it via API, MCP, or on a schedule?

Yes. Every actor on Apify is callable via a REST API, the official JavaScript and Python clients, or the CLI — see the API tab for ready-made code. AI agents can call it through the Apify MCP server. The built-in scheduler handles recurring runs (daily or weekly review monitoring).

Why did my run return zero reviews?

Almost always one of two things: the URL isn't a listing/review page (search results and forum pages aren't supported), or Tripadvisor served a block page to your proxy IP. The run log tells you which. Switching to the RESIDENTIAL proxy group fixes the second case in nearly every run we've seen.

Does it also scrape hotel prices or listing details?

No — this actor is focused on doing reviews well. Basic listing context (name, type, URL) is attached to every review so you can join the data with other sources. For prices and inventory, use Booking.com Hotel Scraper.

Questions or a page variant that doesn't parse? Open an issue on the actor page and include the URL — markup changes get fixed quickly.