Google Hotels by City: names, ratings, review counts, price avatar

Google Hotels by City: names, ratings, review counts, price

Pricing

$4.00 / 1,000 hotel listeds

Go to Apify Store
Google Hotels by City: names, ratings, review counts, price

Google Hotels by City: names, ratings, review counts, price

The hotel landscape of a city from Google Hotels, up to 200 cities per run: hotel name, Google rating, number of reviews, indicative nightly price and currency, in Google's own order. No dates, no booking, no personal data: the market overview, not the rate search. Pay per delivered hotel.

Pricing

$4.00 / 1,000 hotel listeds

Rating

0.0

(0)

Developer

Steadydata Team

Steadydata Team

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

31 minutes ago

Last modified

Share

The hotel landscape of a city from Google Hotels, up to 200 cities per run: hotel name, Google rating, number of reviews, indicative nightly price and currency, in Google's own order. No dates, no booking, no personal data: the market overview, not the rate search. Pay per delivered hotel.

Why this scraper

  • Only delivered results are charged. Inputs that fail come back as clear error records at no cost.
  • Measured on the real city page: 20 hotels per city, 20 of 20 with a rating and a review count, 20 of 20 with an indicative price (Amsterdam, 15 September 2026).
  • Pay per hotel, nothing else. No setup fee, no per-page fee: the alternative in the Store charges $0.02 per page plus a per-run fee. Here a city that fails costs nothing.
  • Unknown cities are refused, not invented. When Google does not know the place it answers with a generic list without prices. This actor recognises that and returns an UNKNOWN_CITY error record instead of ten resorts labelled with your city.

Who this is for

Market and destination research: which hotels dominate a city on Google, how they are rated, how many reviews they carry and at what indicative price level. Hotel groups benchmarking a city, travel marketplaces sizing supply, analysts tracking review counts over time. Runs for up to 200 cities in one go.

Who this is not for

  • You need rates for specific dates or guests. This actor reads Google's city page, which has no date input; priceFrom is Google's indicative nightly price for its default dates and is marked as such in priceNote. Date-specific rate search is a different Google route that its robots.txt does not allow, so it is deliberately not offered.
  • You need more than about 20 hotels per city. The city page shows one screen of hotels in Google's own order; there is no pagination on this route.
  • You need addresses, phone numbers or booking links. Not delivered.

Input example

{
"cities": [
"Amsterdam",
"Lisbon"
],
"maxHotelsPerCity": 20,
"country": "US",
"language": "en"
}

Output fields

  • city
  • position
  • name
  • rating
  • reviewCount
  • priceFrom
  • currency
  • priceNote
  • country

priceFrom is the indicative price for Google's default dates and currency states which currency that is, read from the page itself; it is usually USD and does not follow the country field. position is Google's order on the page.

Output example

{
"city": "Amsterdam",
"position": 2,
"name": "Leonardo Eden Hotel Amsterdam City Center",
"rating": 4.1,
"reviewCount": 4234,
"priceFrom": 121,
"currency": "USD",
"priceNote": "indicative price for Google's default dates; set no dates on this route",
"country": "US",
"status": "ok"
}

Error codes: INVALID_CITY (empty city or a bad country code), UNKNOWN_CITY (Google does not know the place and answered with a generic list), BLOCKED (consent or bot wall; the actor retries on a fresh exit first), NO_HOTELS, FETCH_FAILED. None of them is charged.

Pricing

Pay per event: one hotel-listed event per delivered result. No charge for inputs that fail, no separate platform-usage surcharge.

Free Apify plan: this actor delivers up to 25 rows per run for accounts on the Apify free plan, and then stops with a message. That limit is set by us, not by Apify. It exists so the actor keeps paying for itself for the people who do pay. Any paid Apify plan runs it at full size, billed per delivered row, with failed rows never charged.

FAQ

Why is the price called indicative? Google's city page shows a nightly price for its own default dates. It is a level, not a quote for your dates. Date-specific rates live on a Google route that its robots.txt does not allow, so this actor does not go there.

Why only about 20 hotels per city? That is one city page in Google's order; there is no pagination on this route. For a full inventory of a city you need a different source.

What happens with a place Google does not know? You get an UNKNOWN_CITY error record and no charge. Google itself would show a generic list of resorts without prices; we do not pass that off as your city.

Which currency do I get? Whichever one Google prices the page in, and every row states it in currency, read from the price itself. That is usually USD. The country you set steers which hotels Google shows, not the currency: Google decides that from where the request comes out, and this actor rotates its exits to stay unblocked. Rows without a price carry no currency. So always read currency instead of assuming one, and convert if you need a single currency across cities.

Are ratings and review counts exact? They are what Google shows on the card at run time: rating with one decimal, review count as a whole number.

Is personal data collected? Maintained daily: every actor in this portfolio runs a live check each morning and a content check against known facts each week. Report a problem through the Issues tab.

What happens when the source changes? Sources change from time to time; that is the nature of this work. The actor is monitored daily and fixed fast, and while it is broken you are not charged, because only delivered results cost anything.

rating and reviewCount are empty for a hotel that has no reviews yet on Google (1 of 20 Amsterdam hotels on 16-09-2026).