Google Hotels Scraper | Nightly Prices & Ratings
Pricing
from $1.00 / 1,000 hotel returneds
Google Hotels Scraper | Nightly Prices & Ratings
Extract first-page Google Hotels results by city or area: nightly prices before and after taxes, guest ratings, review counts, hotel class, coordinates, and official websites. Set dates, adults, and currency. About 18-20 hotels per location. $1/1,000 hotels returned, plus a small run-start fee.
Pricing
from $1.00 / 1,000 hotel returneds
Rating
0.0
(0)
Developer
GridForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
17 hours ago
Last modified
Categories
Share
Google Hotels Scraper: Nightly Prices, Ratings & Locations
Extract the first page of Google Hotels results for cities or areas and turn it into structured hotel data. Research displayed nightly prices before and after taxes alongside guest ratings, review counts, hotel class, coordinates, and official websites.
Coverage: approximately 18-20 hotels per location, depending on the response. Price: $1 per 1,000 hotel results, plus the configured run-start fee.
Quick start
- Add one or more cities, neighborhoods, or areas.
- Set check-in and check-out dates if you want a particular stay. Supply both dates together.
- Choose the number of adults, currency, and Google country.
- Start the Actor, inspect the output, and export JSON, CSV, or Excel, or retrieve the dataset through the Apify API.
Example input
{"locations": ["Times Square, New York"],"checkIn": "2026-12-05","checkOut": "2026-12-08","adults": 2,"currency": "USD","country": "us"}
This is an input example, not a recorded result or a promise of availability or price.
What can I extract?
| Field | Meaning |
|---|---|
name | Hotel name |
pricePerNight | Displayed nightly price before taxes, when available |
pricePerNightWithTaxes | Displayed nightly price including taxes, when available |
rating | Guest rating |
reviewCount | Number of reviews; not the text of individual reviews |
hotelClass | Hotel star classification; separate from guest rating |
latitude, longitude | Hotel coordinates |
checkIn, checkOut | Check-in/out information, when returned |
website | Official hotel website, when supplied |
Fields can be missing when Google does not return them. Inspect a sample before building downstream transformations.
Input reference
| Field | Default | Purpose |
|---|---|---|
locations | Required | Array of city, neighborhood, or area queries |
checkIn | Empty | Optional check-in date; use an unambiguous YYYY-MM-DD value |
checkOut | Empty | Check-out date; supply it when setting check-in |
adults | 2 | Adult guests; supported input range is 1-12 |
currency | USD | Three-letter currency code, such as USD or EUR |
country | us | Two-letter Google country code, such as us or gb |
proxyConfiguration | Apify proxy enabled | Proxy configuration used by the Actor |
If dates are left empty, Google chooses its default dates. Set both dates for repeatable research inputs.
Pricing and billing unit
- $0.001 per hotel returned ($1 per 1,000 hotel-result events).
- The current pricing configuration also includes a $0.00005 Actor Start event, defined per GB of Actor memory with a minimum of one event. At the default 1 GB, this is $0.00005 per run.
- A failed location does not incur a hotel-result event charge, but the start event can still apply.
- Example at 1 GB: 18 returned hotels have $0.01805 in configured event charges. This arithmetic is not a measured invoice. Confirm the live Pricing tab before running; the authenticated console currently shows that users do not pay platform usage costs.
Scope and limitations
This Actor fetches the first page, not every hotel in a city. Narrower neighborhood queries can help explore different areas, but do not guarantee complete coverage and can return overlapping properties.
Prices reflect what Google displays for the search and can change. A displayed rate is not a reservation, guaranteed bookable price, or verified checkout total. Missing prices do not by themselves prove a hotel is sold out.
This version does not promise pagination, individual guest-review text, a price ladder across booking providers, room-level inventory, amenities, or booking links. reviewCount is a count, not a collection of reviews.
The Actor retries transient request failures. Upstream changes and rate limits can still cause errors; no guaranteed success rate is claimed.
Repeatable price research
Use consistent dates, guest count, currency, country, and location text when comparing runs. Retain each run's timestamp in your analysis. To monitor changing prices, configure an Apify schedule and compare successive datasets; scheduling does not remove per-run charges.
Use the Actor's API tab for current authenticated request examples. An Apify token is required for API execution; no Google API key is supplied in the input.
Not affiliated with or endorsed by Google.
Output example (illustrative)
{"name":"Example Hotel","pricePerNight":"$120","pricePerNightWithTaxes":"$145","rating":4.2,"reviewCount":250,"hotelClass":4,"latitude":40.75,"longitude":-73.99,"website":"https://example.com"}
Values illustrate the record shape; this is not an actual offer or observed rate.
FAQ
Does it return every hotel in a city? No. It returns the first page, about 18-20 hotels per location. More specific location searches can increase coverage but may overlap.
Does it include review text or all booking-provider prices? No. This version includes review counts and displayed hotel prices.
Is a failed run free? Failed locations have no hotel-result charge, but the configured run-start event can still apply.