Booking.com review analysis tool
The tool takes one input: a supported Booking.com property link. You do not need an account or proof of ownership. The link is resolved on the server, the property is verified, and the analysis dashboard opens while public reviews are collected in the background.
Which links work
Short links from Booking.com's own share menu and direct property-page addresses are both supported.
- booking.com/Share-… short links
- booking.com/hotel/…/…-html addresses
How links are resolved safely
Short links are followed one hop at a time on the server. Every hop is re-checked: only https is accepted, private IP ranges, localhost and cloud metadata addresses are refused, and the number of redirects is capped. A redirect cannot steer the request into an internal network.
How collection proceeds
The collector runs in a separate, isolated process; the main web process never executes script from a source page. The visible review list is advanced at a controlled rate, duplicates are removed by source review id, and progress is checkpointed so an interruption does not restart the job.
What happens when access is blocked
On a 429, a 403, a CAPTCHA, a sign-in prompt or a robot block, the job moves to `blocked` and stops. None of those protections is ever bypassed; the dashboard states why the job stopped and how many reviews had been collected by then.
Method
Every number on this page comes from the analysis pipeline nalyzed runs over publicly visible Booking.com reviews: normalisation, language detection, personal-data redaction, accommodation-taxonomy topic classification and aspect-level sentiment. Results are stored with their evidence quote, sample size and confidence score; a result whose evidence does not appear verbatim in the source review is not published. When collection does not finish, coverage is shown as `partial` and no screen claims that every review was analysed.