Agoda Reviews Scraper
Pricing
from $0.05 / 1,000 review extracteds
Agoda Reviews Scraper
Scrape public Agoda hotel reviews, ratings, traveler metadata, and property context for travel SEO and hotel reputation workflows.
Pricing
from $0.05 / 1,000 review extracteds
Rating
0.0
(0)
Developer
Hanna Nosova
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 days ago
Last modified
Categories
Share
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.
Ready-to-run examples
Use these saved Store examples as starting points. Open any example to prefill the Actor input, then adjust URLs, keywords, limits, or filters for your own run.
- Export Agoda Business Traveler Reviews
- Export Agoda Family Traveler Reviews
- Agoda Seasonal Review Monitor
- Agoda Competitor Property Review Export
- Agoda Hotel Amenity Feedback Dataset
- Monitor Recent Negative Agoda Reviews
- View all ready-to-run examples (20 examples)
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"}
Input configuration
| Setting | JSON key | What to enter |
|---|---|---|
| Hotel URLs | hotelUrls | Public Agoda hotel page URLs. |
| Property IDs | propertyIds | Agoda property IDs when you already know them. |
| Maximum reviews per hotel | maxReviewsPerHotel | Review rows to save for each hotel. |
| Sort | sort | Review order to request when supported. |
| Language | language | Locale such as en-us. |
| Currency | currency | Currency code such as USD, EUR, or GBP. |
| Proxy configuration | proxyConfiguration | Optional proxy settings. |
Output fields
| Field group | Fields |
|---|---|
| Property | hotelUrl, propertyId, hotelName, city, country |
| Property ratings | overallRating, overallRatingText, totalReviews |
| Review identity | reviewId, reviewTitle, reviewDate, stayDate |
| Review content | reviewText, rating, ratingText |
| Traveler context | travelerType, roomType, reviewerName, reviewerCountry, lengthOfStay |
| Extra metadata | helpfulVotes, provider, scrapedAt |
Pricing
This Actor uses Apify pay-per-event pricing. The prices below come from the current Actor pricing configuration. Apify public plans map to Store discount tiers, so the table shows both the user-facing plan context and the pricing tier name. The final price shown in Apify depends on the user account plan and any custom agreement.
| Event | What is charged | Price |
|---|---|---|
start | One-time fee charged when a run starts. Covers fixed startup cost. | $0.005 |
| Event | What is charged | Free / no discount | Starter / Bronze | Scale / Silver | Business / Gold | Custom / Platinum | Custom / Diamond |
|---|---|---|---|---|---|---|---|
review | Charged per Agoda review extracted. | $0.09815 / 1,000 | $0.08535 / 1,000 | $0.06657 / 1,000 | $0.05121 / 1,000 | $0.03414 / 1,000 | $0.0239 / 1,000 |
Apify may also charge platform usage for compute, storage, proxies, or data transfer outside this Actor pricing. Check the Actor run and the Apify Pricing tab for the exact cost shown to your account.
Tips for best results
- Prefer full Agoda hotel URLs when available.
- Use property IDs for stable repeated runs.
- Keep
maxReviewsPerHotelmoderate 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.
FAQ
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.
Related actors
- Trip.com Hotels Scraper
- Airbnb Reviews Scraper
- ProductReview.com.au Scraper
- Google News Scraper
- Website Content Crawler Lite
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.
Changelog
0.2
- Clarified input settings, output fields, pricing, API usage, and Agoda public-data limits.
0.1
- Initial public release.
Privacy and data handling
This Actor runs with Apify limited permissions and only processes data needed for the documented run. It uses review lookup inputs and public review results to produce the output dataset and sends requests to public Agoda Reviews pages/endpoints; results are stored in Apify run storage for your account. FetchCat does not use your inputs or outputs for advertising, does not use them for model training, and does not retain them outside the Apify run except for transient support debugging when you explicitly share run details. You are responsible for using the Actor lawfully, respecting the target site's terms, and avoiding unnecessary personal or sensitive data in inputs.