TripAdvisor Reviews Scraper — Search, Cruises & Monitor

Why use this Actor?

TripAdvisor reviews scraper for hotels, restaurants, attractions, airlines and cruises. Use direct URLs, location IDs or place/brand/destination search; export ratings, reviewer/trip data, subratings, owner replies, photos and LLM-ready Markdown, then filter and monitor new reviews.

What you can do

• TripAdvisor place URLs — Direct TripAdvisor Hotel, Restaurant, Attraction/Activity, Airline or Cruise review URLs. Can be combined with location IDs and search discovery.
• Maximum reviews per place — Maximum matching paid review rows emitted for each unique TripAdvisor place.
• Maximum total reviews — Hard result cap across all places for predictable runtime and spend.
• Ratings — Optional 1-5 rating filter. Empty means all ratings.
• Review languages — Optional ISO language codes such as en, it, de, fr. Each language is fetched as a separate source slice for better coverage.
• Published after — Optional inclusive lower boundary: YYYY-MM-DD or ISO 8601.
• Published before — Optional inclusive upper boundary: YYYY-MM-DD or ISO 8601.
• Review text contains — Optional case-insensitive keyword across title and review text. Filtered rows are not billed.
• Traveler types — Optional TripAdvisor traveler types such as COUPLES, FAMILY, FRIENDS, SOLO, BUSINESS.
• Minimum helpful votes — Only emit reviews with at least this many helpful votes.
• Owner/management reply — Return any reviews, only reviews with a management reply, or only reviews without one.
• Output order — Preserve TripAdvisor source order or sort collected matching rows before output.

Best for

• Travel reputation monitoring.
• Hotel and restaurant research.
• Destination intelligence.
• Review datasets.

FAQ

What is this Actor for?
It is designed for travel reputation monitoring, hotel and restaurant research, destination intelligence.

Can I run it on a schedule?
Yes. You can schedule Actor runs on Apify and send the resulting dataset into automations, webhooks, storage, or downstream APIs.

How do I control cost and run size?
Use the input limits and filters shown in the Actor input form. The Actor applies bounded defaults and hard caps so large jobs remain predictable.

Search keywords

tripadvisor reviews scraper, tripadvisor review scraper github, tripadvisor review scraper free, apify tripadvisor reviews scraper, can tripadvisor reviews be traced, can tripadvisor reviews be trusted, tripadvisor reviews api, get tripadvisor reviews api, tripadvisor review express api, tripadvisor do a review, tripadvisor write a review, tripadvisor make a review, are tripadvisor reviews reliable, tripadvisor

Extract public TripAdvisor reviews for hotels, restaurants, attractions/activities, and airlines into clean structured records for hospitality analytics, reputation monitoring, destination research, competitor analysis, customer-experience workflows, and AI/LLM pipelines.

The Actor uses TripAdvisor's current public review data flow directly instead of rendering every review page in a browser. This keeps runs fast and inexpensive while still returning rich review, traveler, place, photo, and management-response metadata.

What you get

Successful review rows can include:

• TripAdvisor rating, title, full review text, language, published and created dates
• reviewer display name, username, verification state, profile URL, avatar, hometown, and contribution count
• traveler type and stay date
• helpful-vote count
• owner/management response and response date when exposed
• public review photos and photo URLs
• additional sub-ratings when exposed
• place ID, name, place type, category, canonical source URL, and review URL
• stable review IDs for deduplication
• scan/runtime metadata for reproducible pipelines

Optional free place_summary rows include TripAdvisor's total public review count and place metadata.

Supported TripAdvisor URLs

• Hotel review pages
• Restaurant review pages
• Attraction and activity review pages
• Airline review pages
• localized TripAdvisor domains such as .it, .co.uk, and others

Input example

{
  "placeUrls": [
    "https://www.tripadvisor.com/Attraction_Review-g274772-d2725527-Reviews-Krawl_Through_Krakow_Pub_Crawl-Krakow_Lesser_Poland_Province_Southern_Poland.html"
  ],
  "maxReviewsPerPlace": 500,
  "maxTotalReviews": 5000,
  "ratings": [],
  "languageCodes": [],
  "reviewedAfter": "",
  "reviewedBefore": "",
  "containsText": "",
  "tripTypes": [],
  "minHelpfulVotes": 0,
  "ownerReply": "any",
  "sortOutput": "source",
  "includePlaceSummary": true,
  "maxPagesPerPlace": 150,
  "autoProxyFallback": true,
  "proxyConfiguration": {"useApifyProxy": false}
}

Filters

Filtering happens before paid review rows are emitted. You can combine:

• 1-5 rating selection
• ISO review-language codes
• inclusive date boundaries
• case-insensitive text keyword
• traveler types such as COUPLES, FAMILY, FRIENDS, SOLO, and BUSINESS
• minimum helpful votes
• management-reply presence

When one or more languages are selected, the Actor fetches language slices separately to improve coverage before deduplicating stable review IDs.

Reliability design

The Actor includes:

• strict TripAdvisor URL validation
• duplicate-place removal
• direct-first HTTP mode
• optional automatic Apify Proxy fallback
• bounded retries and timeouts
• deep offset pagination using TripAdvisor's current public review flow
• global review-ID deduplication per place
• bounded per-place and global result limits
• expanded scan windows when post-filters are active
• diagnostic rows instead of crashing a multi-place batch
• maximum-charge handling for pay-per-event runs

Output row types

review

A successful, billable TripAdvisor review.

place_summary

An optional free aggregate row for the place.

status

A free informational row when the source works but no review matches the selected filters inside the scan window.

error

A free diagnostic row for invalid input, unavailable source data, rate limiting, network errors, or another per-place failure.

Pricing

Launch pricing target: $0.00039 per successfully emitted review, about $0.39 per 1,000 TripAdvisor reviews, plus the small Actor-start event shown by Apify.

Only successful review rows trigger the paid review event. Summary rows, status rows, errors, retries, duplicates, and filtered-out reviews are free.

Spend controls

Use maxReviewsPerPlace, maxTotalReviews, maxPagesPerPlace, and Apify's maximum-total-charge setting to bound runtime and spend.

Source behavior

TripAdvisor controls the public review schema, pagination behavior, and optional fields. Some reviews do not have photos, management replies, traveler details, hometown data, or sub-ratings. Missing data is returned empty rather than invented.

Responsible use

This Actor reads public review/profile information. Use reviewer names, text, travel details, photos, and responses in accordance with applicable privacy, copyright, data-protection requirements, and TripAdvisor's applicable terms. Do not use the output to harass, deanonymize, or build sensitive profiles of reviewers.

Support

For a reproducible issue, provide the public TripAdvisor URL, relevant filters, proxy mode, and Apify run ID. Never include API tokens, proxy passwords, or private credentials.

Extended capabilities

• Scrape supported TripAdvisor hotel, restaurant, attraction, and cruise review URLs.
• Apply rating, language, text, country, date, helpfulness, and owner-response filters before output.
• Preserve location summaries, distribution intelligence, monitoring state, and bounded pagination diagnostics.