Booking.com Reviews Scraper

What does Booking.com Reviews Scraper do?

Booking.com Reviews Scraper collects the guest reviews of any hotel, apartment, hostel or other property on Booking.com: the review score, title, liked and disliked text, review date, language, reviewer name and country, traveler type, room, number of nights, stay month, helpful votes and the property's response. Every row also carries the property's overall score, review count and category scores (staff, facilities, cleanliness, comfort, value for money, location and free WiFi).

Paste a property link from Booking.com, or just its property ID, and click Start. The prefilled example saves 30 reviews of The Savoy in London in a few seconds. Because it runs on the Apify platform, you also get API access, scheduled runs, integrations (Google Sheets, Make, Zapier, webhooks), run monitoring and automatic proxy rotation.

Why scrape Booking.com reviews?

• Reputation monitoring: follow what guests say about your hotel or your competitors, every day.
• Competitor benchmarking: compare scores, category scores and complaints across the properties in a city.
• Guest experience research: find what guests love and what they complain about, by traveler type, season or language.
• Response tracking: see which reviews a property answered, and how.
• Sentiment analysis and AI datasets: liked and disliked texts come in separate fields, ready for analysis or model training.

How to scrape Booking.com reviews

1. Open the property on Booking.com and copy the address from your browser, for example https://www.booking.com/hotel/gb/the-savoy.html. Any language version works, and so do links with dates or other search settings.
2. Paste it into Properties, one property per line. You can also paste property IDs, such as 280149.
3. Set Max reviews per property and the Sort by order.
4. Optionally, pick filters: traveler type, review score, languages, time of year, or only reviews newer than a date.
5. Click Start, then download the reviews when the run finishes.

Input

Everything is set on the Input tab. In JSON, the input looks like this:

{
    "property_urls": [
        "https://www.booking.com/hotel/gb/the-savoy.html",
        "booking.com/hotel/de/adlon-kempinski-berlin.de.html",
        "39326"
    ],
    "max_reviews_per_property": 100,
    "sort": "newest",
    "traveler_type": "couples",
    "score_band": "all",
    "languages": ["en", "de"],
    "time_of_year": "all",
    "newer_than": "30 days",
    "skip_reviews_without_text": false
}

Field	What it does
property_urls	Booking.com property links (any language or country version, with or without https://, including /reviews/ pages) or numeric property IDs. API callers can also send {"url": "..."} objects.
max_reviews_per_property	Stops after this many reviews for each property. Default: 100. Use a large number, such as 100000, for every review.
sort	newest (default), oldest, highest_score, lowest_score or most_relevant: Booking.com's own sort orders.
traveler_type	all (default), families, couples, groups_of_friends, solo_travelers or business_travelers.
score_band	all (default), wonderful (9+), good (7-9), fair (5-7), poor (3-5) or very_poor (1-3).
languages	Only reviews in these languages, as two-letter codes such as en, de or fr; regional codes such as pt-br count as their language. Empty for every language.
time_of_year	all (default), mar_may, jun_aug, sep_nov or dec_feb. Booking.com applies it to the month the review was posted.
newer_than	Only reviews posted on or after a date (2026-09-01) or within an age (30 days, 2 weeks, 6 months). Reviews are then read newest first.
skip_reviews_without_text	Leaves out reviews that are only a score, with no title or text. Default: off.
proxyConfiguration	Optional; leave it empty. The Actor connects through Apify's datacenter proxy and moves to residential proxies on its own if Booking.com keeps refusing.

Output

Each review becomes one row. Here is a real example:

{
    "review_id": "fa5226c5498799d3",
    "review_date": "2026-10-05T21:25:31+00:00",
    "rating": 9,
    "title": "Excellent welcome and service. A real experience !",
    "positive_text": "Real sense of grandeur !!",
    "negative_text": "Nothing !!",
    "language": "en",
    "reviewer_name": "Adam",
    "reviewer_country": "United Kingdom",
    "reviewer_country_code": "gb",
    "traveler_type": "Couple",
    "room_type": "Superior Queen Room",
    "nights": 1,
    "stay_month": "2026-09",
    "helpful_votes": 0,
    "hotel_response": "Dear Adam, How lovely to read about your Savoy experience! We are thrilled everything exceeded your expectations and you had such a wonderful time. …",
    "photo_urls": [],
    "property_id": 280149,
    "property_name": "The Savoy",
    "property_url": "https://www.booking.com/hotel/gb/the-savoy.html",
    "property_city": "London",
    "property_country_code": "gb",
    "property_score": 9.4,
    "property_review_count": 1433,
    "score_staff": 9.7,
    "score_facilities": 9.5,
    "score_cleanliness": 9.7,
    "score_comfort": 9.8,
    "score_value_for_money": 8.5,
    "score_location": 9.7,
    "score_free_wifi": 9.5,
    "scraped_at": "2026-10-10T12:22:20+00:00"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel. The Output tab has two views: Reviews and Property scores (the property fields on each row).

Data fields

Field	Description
review_id	Booking.com's ID of the review. Each review is saved once per run.
review_date	When the review was posted (UTC, ISO 8601).
rating	The guest's score, from 1 to 10.
title	The review's headline, when the guest wrote one.
positive_text	What the guest liked.
negative_text	What the guest disliked.
language	The review's language as Booking.com records it: a two-letter code such as en, or en-us, pt-br, es-ar, es-mx and zh-tw for Booking.com's regional versions. Text is in the guest's own language, not translated.
reviewer_name	The guest's display name, usually a first name.
reviewer_country / reviewer_country_code	The guest's country, and its two-letter code in lowercase.
traveler_type	Family, Couple, Group of friends or Solo traveler. Booking.com keeps business trips apart from the travel group, so reviews found with the Business travelers filter still show one of these.
room_type	The room or unit the guest stayed in.
nights	How many nights the guest stayed.
stay_month	The month the stay ended (2026-09), as Booking.com shows it; it shows no exact stay dates.
helpful_votes	How many people marked the review as helpful.
hotel_response	The property's public response to the review, when it gave one.
photo_urls	Photos the guest added to the review (often none).
property_id, property_name, property_url, property_city, property_country_code	The property the review belongs to.
property_score / property_review_count	The property's overall review score and number of reviews on Booking.com.
score_staff, score_facilities, score_cleanliness, score_comfort, score_value_for_money, score_location, score_free_wifi	The property's category scores, as shown on Booking.com. Empty when a property has no rating in that category.
scraped_at	When the row was saved.

How much does it cost to scrape Booking.com reviews?

The Actor uses pay-per-event pricing: you pay a small fixed amount for each review saved. See the Pricing tab for the exact price. Properties that return no reviews are never charged, reviews skipped by your filters are not saved or charged, and if you set a maximum cost for a run, the Actor stops as soon as it is reached.

It is fast, so the platform usage on top stays tiny: in our tests, every review of two big hotels (5,217 reviews) took about a minute. Apify's free plan includes monthly credit, enough to try the Actor on thousands of reviews.

Tips for scraping Booking.com reviews

• Filter before you scrape. Traveler type, score, language and time of year are applied by Booking.com itself, so you only read, and pay for, the reviews you want.
• Monitor new reviews by scheduling a daily run with Only reviews newer than set to 2 days; use review_id to skip reviews you already have.
• Analyze complaints with Sort by set to Lowest scores, or read the negative_text field of every review.
• Skip score-only reviews. Many guests leave a score without writing anything. Turn on Skip reviews without text if you only need text.
• Several languages at once work with Review languages; the other filters take one value at a time, as on Booking.com.
• Group by property with property_id when you scrape many properties in one run; the property fields repeat on every review row.

FAQ, disclaimers and support

How many reviews can I get for one property? Every review Booking.com shows for it, including properties with more than 10,000 reviews. Set Max reviews per property high enough. The number of reviews read may differ slightly from the count on the property page while new reviews arrive.

Why do some reviews have no text? Booking.com lets guests leave a score without writing anything. Those reviews are saved with empty text fields, unless you turn on Skip reviews without text.

Which links work? Property pages in any language (booking.com/hotel/<country>/<name>.html or .<language>.html), with any dates or search settings in the link, and the property's /reviews/ page. Search result pages, city pages and short share links (booking.com/Share-…) are not property pages: open the property, then copy its address.

What happens to properties that return nothing? Links that are not Booking.com properties, properties Booking.com does not know, closed properties whose reviews Booking.com no longer shows, properties without reviews, properties with no reviews matching your filters, and repeats of a property given twice in the same run are not saved as rows, so you are not charged for them. Each one is listed with its reason in the FAILED_INPUTS record of the run's key-value store, and the status message gives the counts. A run is marked failed only when nothing was saved because Booking.com could not be reached for any property.

Do I need a Booking.com account or my own proxy? No. The Actor reads only public reviews, without logging in, and connects through Apify Proxy on its own.

What about closed properties? Booking.com keeps the page of a property it no longer takes bookings for, but usually stops showing its reviews. Such properties are listed in FAILED_INPUTS as closed; when Booking.com still shows some of their reviews, the Actor saves them.

Is it legal to scrape Booking.com reviews? The Actor reads only reviews that anyone can see on Booking.com without an account. Reviews include guests' display names, countries and stays, which are personal data under rules such as the GDPR and CCPA: only collect what you need, store it securely, have a lawful reason to process it, and don't use it to contact or profile guests. Booking.com's terms of use restrict automated access, so you are responsible for how you use the data. If you are unsure, ask a lawyer.

Found a problem or need a custom solution? Open an issue on the Issues tab and we will look into it. Custom scrapers and review data feeds are available on request.