Booking Reviews Scraper

Extract hotel reviews from Booking.com into a clean, analysis-ready dataset. Collect structured review content, ratings, review dates, and traveler context for market research, reputation monitoring, and hospitality intelligence workflows.

Features

• Hotel Review Extraction — Collect reviews directly from a Booking hotel page.
• Pagination Support — Fetches multiple review pages up to your configured limits.
• Clean Output Records — Removes null and empty values from saved dataset items.
• Duplicate Filtering — Prevents duplicate reviews in the output.
• Structured Review Data — Returns normalized fields for analytics and reporting.

Use Cases

Hospitality Reputation Monitoring

Track guest sentiment over time for a specific property. Identify positive and negative feedback trends to improve service quality and guest experience.

Competitive Hotel Analysis

Collect review data from competitor properties and compare score patterns, complaint themes, and traveler feedback.

Travel Content Intelligence

Build review datasets for editorial, SEO, and destination insights. Understand what guests praise or criticize before publishing recommendations.

Product and Service Validation

Use guest feedback to validate room quality, amenities, and value perception before launching promotions or partnerships.

Input Parameters

This actor uses a direct Booking hotel URL input and automatically opens the reviews tab.

Parameter	Type	Required	Default	Description
startUrl	String	Yes	https://www.booking.com/hotel/gb/nobu-hotel-london-portman-square.html	Booking hotel page URL. The actor auto-normalizes it to the reviews tab URL.
results_wanted	Integer	No	20	Maximum number of unique reviews to save.
proxyConfiguration	Object	No	—	Proxy settings. Residential proxy is recommended for best reliability.

Output Data

Each item in the dataset contains:

Field	Type	Description
hotelName	String	Hotel name associated with the review.
hotelUrl	String	Booking hotel page URL.
reviewId	String/Number	Unique review identifier when available.
reviewTitle	String	Review headline/title.
reviewText	String	Main review text with positive/negative notes when available.
positive	String	Positive section text when provided by Booking.
negative	String	Negative section text when provided by Booking.
rating	Number/String	Review score.
publishedAt	String	Review publication date/time.
language	String	Review language code/name.
stayDate	String	Date of stay when available.
roomType	String	Room type when available.
travelerType	String	Traveler category when available.
reviewerName	String	Reviewer name.
reviewerCountry	String	Reviewer country name.
reviewerCountryCode	String	Reviewer country code.

Usage Examples

Basic Review Collection

{
	"startUrl": "https://www.booking.com/hotel/gb/nobu-hotel-london-portman-square.html",
	"results_wanted": 20
}

Large Collection (Internal Pagination)

{
	"startUrl": "https://www.booking.com/hotel/gb/nobu-hotel-london-portman-square.html",
	"results_wanted": 100
}

Run With Residential Proxy

{
	"startUrl": "https://www.booking.com/hotel/gb/nobu-hotel-london-portman-square.html",
	"results_wanted": 50,
	"proxyConfiguration": {
		"useApifyProxy": true,
		"apifyProxyGroups": ["RESIDENTIAL"]
	}
}

Sample Output

{
	"hotelName": "Nobu Hotel London Portman Square",
	"hotelUrl": "https://www.booking.com/hotel/gb/nobu-hotel-london-portman-square.html#tab-reviews",
	"reviewId": "123456789",
	"reviewTitle": "Excellent stay in a prime location",
	"reviewText": "Positive: Great location and very clean room. Negative: Breakfast options were limited.",
	"positive": "Great location and very clean room.",
	"negative": "Breakfast options were limited.",
	"rating": 8.9,
	"publishedAt": "2026-03-24",
	"language": "en-gb",
	"stayDate": "2026-03",
	"roomType": "Deluxe King Room",
	"travelerType": "couple",
	"reviewerName": "Emma",
	"reviewerCountry": "United Kingdom",
	"reviewerCountryCode": "gb"
}

Tips for Best Results

Use Direct Hotel URLs

• Provide a direct Booking hotel page URL with reviews tab when possible.
• Prefer stable hotel pages over redirected campaign links.

Keep Test Runs Small

• Start with results_wanted: 20 for fast validation.
• Increase limits only after confirming stable output.

Use Residential Proxies

• Residential proxy configuration improves reliability on protected pages.

Integrations

• Google Sheets — Export review datasets for team analysis.
• Airtable — Build searchable review intelligence tables.
• Make — Trigger automated sentiment workflows.
• Zapier — Connect review data to CRM and reporting tools.
• Webhooks — Send datasets to internal APIs.

Export Formats

• JSON — API and data engineering workflows.
• CSV — Spreadsheet and BI tools.
• Excel — Business reporting.
• XML — Legacy system integrations.

Frequently Asked Questions

Can I scrape multiple hotels in one run?

This actor currently runs one hotel target per execution.

Why are some review fields missing?

Some reviews do not include all optional attributes (such as room type or stay date). The actor removes null and empty values automatically.

Does the actor remove duplicate reviews?

Yes. Duplicate review records are filtered before saving results.

How many reviews can I collect?

You can control this with results_wanted. Pagination is handled internally based on your requested result count and available reviews.

Is proxy required?

Not always, but residential proxy is strongly recommended for consistency and lower blocking risk.

Support

For bug reports, improvements, or feature requests, use the Issues section in your project repository or contact support through the Apify Console.

Legal Notice

This actor is intended for legitimate data collection and analytics use. Users are responsible for complying with Booking terms, local laws, and applicable data usage policies.