Tripadvisor Reviews Scraper

Extract hotel, restaurant, and attraction reviews from Tripadvisor using just a listing page URL. Get full review text, ratings, author profiles, stay dates, photos, and owner replies — ready for reputation monitoring, competitor benchmarking, or feeding an AI/BI pipeline.

Just paste a Tripadvisor URL, click Start, and download the results — no proxy or setup of any kind required. Runs on the Apify platform, so you get scheduling, API access, and webhooks out of the box.

What you get

• Review rating (1–5), title, and full text
• Original language and machine-translation flag
• Published date, stay date, and trip type (family, couples, business, ...)
• Author name, profile URL, avatar, verification status, and contribution count
• Helpful vote count and review photos
• Hotel/business owner replies (management response)
• Listing name, aggregate rating, and total review count
• Full raw API object for advanced/custom use

How to use Tripadvisor Reviews Scraper

1. Open this Actor and click Start
2. Add one or more Tripadvisor listing URLs under Listing URLs — hotel, restaurant, or attraction pages all work
3. Set Max reviews per listing (0 = scrape everything available)
4. Optionally restrict to specific review languages
5. Run and download results from the Dataset tab

No proxy setup needed — the Actor is pre-configured to route around Tripadvisor's DataDome bot protection automatically.

Supported URLs

Any Tripadvisor country domain works — tripadvisor.com, .com.tr, .co.uk, .de, etc. — as long as the URL contains a location id, e.g.:

• https://www.tripadvisor.com/Hotel_Review-g297550-d33877721-Reviews-Xanadu_Club_Makadi_Bay-Makadi_Bay_Hurghada_Red_Sea_and_Sinai.html
• https://www.tripadvisor.com.tr/Hotel_Review-g297550-d33877721-Reviews-...html
• https://www.tripadvisor.com/Restaurant_Review-g187147-d123456-Reviews-...html

Input

Field	Description
startUrls	Tripadvisor hotel/restaurant/attraction page URLs
maxReviews	Max reviews to scrape per listing (0 = all)
languages	Optional list of Tripadvisor language codes (e.g. en, tr, de) to only scrape reviews originally written in those languages
translateReviewsTo	Optional Tripadvisor language code to machine-translate review text into. Leave empty to get each review's original wording
ratings	Optional list of star ratings (1-5) to filter reviews by
since	Only scrape reviews published on or after this date (YYYY-MM-DD)
startPage	Review page to start from (20 reviews/page) — useful to resume a previous run
sortReviewsBy	RECOMMENDED (default), DATE (strict newest-first), RATING (highest rated first), or FAVORABLE_RATING (Tripadvisor's own "most helpful" ranking)

By default (no translateReviewsTo) text comes back exactly as the reviewer wrote it. Every review also reports language, originalLanguage, and isMachineTranslated regardless of this setting, so you can always tell what you're looking at. | customMapFunction | Optional JS function, e.g. (item) => ({ ...item, myField: 1 }), to transform each review before it's saved (transformation only, doesn't filter) |

Example input:

{
  "startUrls": [
    { "url": "https://www.tripadvisor.com/Hotel_Review-g297550-d33877721-Reviews-Xanadu_Club_Makadi_Bay-Makadi_Bay_Hurghada_Red_Sea_and_Sinai.html" }
  ],
  "maxReviews": 200
}

Output

Each dataset item is one review. You can download the dataset in JSON, CSV, Excel, HTML, and other formats from the Dataset tab.

{
  "reviewId": "1071537918",
  "reviewUrl": "https://www.tripadvisor.com.tr/ShowUserReviews-g297550-d33877721-r1071537918-....html",
  "rating": 5,
  "title": "Relaxing, friendly staff, wonderful beach, good location",
  "text": "I think I spent one of the best and most relaxing weeks of my life here...",
  "language": "en",
  "originalLanguage": "en",
  "isMachineTranslated": false,
  "publishedAt": "2026-08-04T00:00:00.000Z",
  "travelDate": "2026-07-31T00:00:00.000Z",
  "tripType": "FAMILY",
  "authorName": "Csenge O",
  "authorProfileUrl": "https://www.tripadvisor.com.tr/Profile/...",
  "authorContributions": 12,
  "helpfulVotes": 0,
  "photos": ["https://dynamic-media-cdn.tripadvisor.com/media/photo-o/..."],
  "managementResponse": {
    "text": "Dear Guest, thank you for your kind words...",
    "publishedAt": "2026-08-05T00:00:00.000Z",
    "authorName": "Xanadu Hotels",
    "authorRole": "Other"
  },
  "hotelName": "Xanadu Club Makadi Bay",
  "hotelRatingValue": 4.9,
  "hotelReviewCount": 292,
  "source": "tripadvisor"
}

Data table

Field	Description
rating	Review score, 1–5
title / text	Review headline and full body
publishedAt / travelDate	When the review was published / the stay took place
tripType	Family, couples, business, solo, friends
authorName / authorProfileUrl / authorContributions	Reviewer identity and activity level
photos	Array of review photo URLs
managementResponse	Owner/manager reply, if any
hotelName / hotelRatingValue / hotelReviewCount	Listing-level context on every row

How much does it cost to scrape Tripadvisor?

Tripadvisor reviews are lightweight to process — the Actor opens one browser session per listing and reuses it for all pagination requests, rather than a new page load per review. A typical run scraping a few hundred reviews from one listing uses a small fraction of the Apify free tier's compute units. No proxy costs are passed on to you.

Tips

• Tripadvisor is protected by DataDome bot detection. The Actor handles this internally with a pre-configured proxy — Datacenter proxies and no-proxy setups get blocked almost immediately, which is why proxy choice isn't exposed as an input.
• To scrape many listings efficiently, add them all to Listing URLs in one run instead of running the Actor multiple times.
• Use the languages filter if you only care about reviews in specific languages — it reduces the number of items returned, not the request count.

FAQ & limitations

• This Actor scrapes publicly available review data. Use responsibly and in line with Tripadvisor's Terms of Service and applicable law in your jurisdiction.
• Subratings (value, cleanliness, service, etc.) are included when Tripadvisor provides them for a given review, but not every review has them.
• Exact "published" dates are day-level (Tripadvisor doesn't expose time-of-day for reviews).
• Found a bug or need a custom field? Open an issue in the Actor's Issues tab, or reach out about a tailored scraping solution.