Free Hotel Review Checker — Hotel Reputation, Rating Comparison
Pricing
Pay per usage
Free hotel reputation check by name or URL: hotel ratings on six review sites — Google Hotels, Tripadvisor, Booking.com, Agoda, Hostelworld, Despegar. One row per hotel per site: rating, 0-5 score, review count, star rating, ranking, sub-scores; summary row: rating comparison. 10 hotels per run.
error status. Row keys are unchanged and the run is still free.Validated search terminology against Google Ads Keyword Planner and Store shelves. Added localized usage guidance and bounded examples; retained existing English phrases. Clarified locale limitations where measured. No runtime, output fields, defaults, or pricing changed.
No behaviour, output or price changed; the same inputs return the same rows, and the actor is still free.
hotelNames, startUrls, sources, language, country, then pacing and proxy); every description now carries a literal example, its default and what empty means; startUrls was cut from 543 to under 500 characters so the agent view no longer truncates it; country says it is the market, not the hotel's country; hotelNames names the comp-set request. Nothing was renamed, removed or re-defaulted.ok | not_found | unsupported | skipped | error), and the other-language nouns.error status. The score, review count, ranking and six sub-scores are read from the new shape (and the old one); row keys are unchanged and the run is still free.curl_cffi is pinned to >=0.16.2 so the image always resolves a build that carries the Safari profile.Business category has no Store page).First release. Free: there is no pay-per-event pricing and no charging call anywhere in the actor.
reputation row per hotel per review site — Google Hotels, Tripadvisor, Booking.com, Agoda, Hostelworld and Despegar — carrying the headline score on the site's own scale, the same score on a shared 0-5 scale, the review count, the star class, the city and the property URL.ranking, ranking_position and ranking_of; the free sub-scores are kept where a site publishes them (Tripadvisor's six, Hostelworld's seven, Despegar's six).summary row per hotel across sites: the mean on the 0-5 scale, the kindest and harshest site, the spread between them, the total reviews found and which site had nothing.status row per hotel per site, ok | not_found | unsupported | skipped | error, always with a reason. A refusal is an error; a genuinely absent property is not_found; the two are never merged.hotelNames, ideally Name, City) resolved through each site's own autocomplete or typeahead, or by property URL (startUrls) on any of the six. A URL's own site is read first and the name it returns is what the other sites are then searched by.dest_type: hotel plus country match, Despegar's canonical-id check) and a uniform word-overlap score reported as matched_confidence. Below 0.6 the site is reported not_found with the score that failed, never guessed at.skipped with a clear message and never fetched) and at most one lookup request plus one aggregate request per site per hotel. No paging anywhere.proxyConfiguration says, because both refuse datacenter ranges; the other four run on datacenter. An account without residential access gets a warning and the configured proxy.reviews_scraper, and the dataset ships nine views: an overview, one per site, the cross-source summary and the status list.