Agoda Reviews Scraper

Scrape public Agoda hotel reviews, ratings, traveler metadata, and property context for travel SEO and hotel reputation workflows.

Data fields

FieldTypeDescription
hotelUrlstring | nullSource Agoda hotel page when a URL input was supplied.
propertyIdintegerAgoda hotel or property identifier.
hotelNamestring | nullHotel name returned by Agoda review data.
citystring | nullBest-effort city parsed from the Agoda hotel URL.
countrystring | nullBest-effort country code parsed from the Agoda hotel URL.
overallRatingnumber | nullHotel-level Agoda rating when available.
overallRatingTextstring | nullAgoda label for the hotel-level rating when available.
totalReviewsinteger | nullHotel-level review count when Agoda returns it.

Input preview

hotelUrlsAgoda hotel URLs
propertyIdsAgoda property IDs
maxReviewsPerHotelMaximum reviews per hotel
sortReview sorting
languageLanguage / locale
currencyCurrency

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

Export public Agoda hotel reviews, ratings, traveler metadata, and property context.

Use this actor when you need a repeatable CSV, JSON, Excel, or API export of Agoda guest reviews for hotel reputation monitoring, travel SEO, hospitality research, competitor analysis, or AI-agent workflows.

At a glance

  • Input: Agoda hotel URLs or property IDs.
  • Output: Hotel name, city, country, overall rating, review text, review rating, stay date, traveler type, room type, reviewer metadata, helpful votes, and scrape time.
  • Sorting: Choose Agoda review sorting where supported.
  • Best for: Hotel review exports, reputation monitoring, travel content analysis, and Agoda API alternative workflows.
  • Proxy optional: Start without proxy for low-cost tests; enable Apify Proxy if Agoda throttles the run.

What can it do?

  • Export Agoda hotel reviews: Save public review titles, text, ratings, dates, stay dates, and traveler context.
  • Collect property context: Include hotel name, city, country, overall rating, rating text, and total review count when available.
  • Analyze review segments: Use traveler type, room type, reviewer country, length of stay, and helpful votes.
  • Run multiple hotels: Process several hotel URLs or property IDs in one run.
  • Use as an Agoda reviews API alternative: Run from the Apify UI, API, schedules, webhooks, or the official Apify MCP server.

Common workflows

  • Reputation monitoring: Track new public reviews for one or more hotels.
  • Competitor research: Compare guest sentiment and rating patterns across nearby properties.
  • Travel SEO: Build review datasets for destination pages, hotel summaries, or content research.
  • Hospitality analytics: Export traveler type, stay date, room type, and reviewer country fields.
  • AI-agent summaries: Let an agent collect review rows before summarizing guest themes.

Input example

{
  "hotelUrls": [
    { "url": "https://www.agoda.com/example-hotel/hotel/example-city.html" }
  ],
  "propertyIds": [],
  "maxReviewsPerHotel": 100,
  "sort": "recent",
  "language": "en-us",
  "currency": "USD",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output example

{
  "hotelUrl": "https://www.agoda.com/example-hotel/hotel/example-city.html",
  "propertyId": "123456",
  "hotelName": "Example Hotel",
  "city": "Bangkok",
  "country": "Thailand",
  "overallRating": 8.7,
  "overallRatingText": "Excellent",
  "totalReviews": 2450,
  "reviewId": "987654321",
  "reviewTitle": "Great location",
  "reviewText": "Clean room and friendly staff.",
  "rating": 9.2,
  "ratingText": "Exceptional",
  "reviewDate": "2026-06-20",
  "stayDate": "2026-06",
  "travelerType": "Couple",
  "roomType": "Deluxe Room",
  "reviewerName": "Anna",
  "reviewerCountry": "Portugal",
  "lengthOfStay": "2 nights",
  "helpfulVotes": 3,
  "provider": "Agoda",
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

Tips for best results

  • Prefer full Agoda hotel URLs when available.
  • Use property IDs for stable repeated runs.
  • Keep maxReviewsPerHotel moderate when testing a new hotel or market.
  • Use the same language and currency for comparable scheduled runs.
  • Enable proxy if Agoda throttles or blocks the target page.

Limits and caveats

  • The actor exports public Agoda review data. It does not access private booking or account data.
  • Some hotels may hide or delay review fields depending on region, language, or availability.
  • Agoda can change review sorting, pagination, and page structure.
  • Reviewer names and countries can be missing or partially anonymized.

API usage

curl "https://api.apify.com/v2/acts/fetch_cat~agoda-reviews-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "hotelUrls": [{ "url": "https://www.agoda.com/example-hotel/hotel/example-city.html" }],
    "maxReviewsPerHotel": 100,
    "language": "en-us"
  }'

MCP and AI agents

You can run this actor through the official Apify MCP server at https://mcp.apify.com.

For a focused single-actor tool, use:

https://mcp.apify.com?tools=fetch_cat/agoda-reviews-scraper

Agent-friendly inputs are hotelUrls, propertyIds, maxReviewsPerHotel, sort, language, currency, and proxyConfiguration.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.

Common questions

Questions and answers reused from the canonical actor README.

Does it require an Agoda account?

No. It extracts public review data.

Can I export to CSV or Excel?

Yes. Download the Apify dataset as CSV, Excel, JSON, XML, RSS, or through the Dataset API.

Can I scrape several hotels in one run?

Yes. Add multiple hotel URLs or property IDs.

Why are some fields empty?

Agoda does not expose every review field for every hotel, locale, or review.