Google Hotels Prices Scraper
Pricing
from $0.63 / 1,000 hotel rows
Hotel prices from Google Hotels for any city or hotel, any dates and guests. Optional prices from every booking site and a price-change monitor. Fast, no browser, low cost.
One per line. A city, area, neighborhood or landmark, written the way you would type it into Google Hotels: Paris, Hotels in Times Square, New York, Lisbon, Portugal. Each place returns its hotels, about 20 per page of results, with the price for your dates and guests.
Optional. One hotel per line, with the city to avoid mix-ups: Fairmont Austin Texas. Each name is looked up first and then priced with the full list of booking sites (Booking.com, Expedia, the hotel's own site and more). A name that matches more than one hotel is skipped with a warning; add the city or use a hotel token.
Optional. Google hotel tokens (they start with Ch), one per line. The entityToken field of every result is one, so you can price the same hotels again without a name lookup. This saves one request per hotel.
Optional. First night of the stay as YYYY-MM-DD. Leave empty to use "Check-in in N days" below, which keeps scheduled runs looking ahead.
Used when "Check-in date" is empty: the stay starts this many days from the day of the run. Google shows prices up to about 330 days ahead.
Optional. Last morning of the stay as YYYY-MM-DD. Leave empty to use "Nights" below.
Length of the stay when "Check-out date" is empty. 1 to 30 nights.
Optional. To price many start dates in one run, set the last check-in date as YYYY-MM-DD. The run prices one stay per date from the check-in date to this one, so the same hotels come back once per date. Up to 62 dates. Each date repeats the search, so cost and requests grow with the number of dates.
For a date range: price every N-th check-in date. 7 prices the same weekday each week.
Number of adults. Google shows the price for one room that fits all guests.
Optional. One age per line, from 0 to 17. Children can change the price and which hotels are shown.
Three-letter code for the prices, for example USD, EUR, GBP. Google converts the price when the hotel does not sell in this currency.
Two-letter country code, for example us, de, jp. Google shows the prices a visitor from this country sees, and which booking sites it lists. Outside the US this works best with a residential proxy in the same country (see Advanced).
Language of hotel descriptions and labels, for example en, de, pt-BR.
Stop after this many matching hotels for each place and each date. If you leave it empty, 20 hotels are returned. Google lists about 490 to 550 hotels per place and date, so 500 is the most you can ask for, and a big city may return slightly fewer. A page of results holds about 20 hotels, and 500 hotels take about 25 requests. You are charged per hotel returned, so this also caps the cost.
Keep only hotels with at least this star class. 0 keeps everything. Vacation rentals have no star class and are dropped when this is above 0.
Keep only places whose Google guest rating is at least this value, on the 5-point scale. For example 4.2. 0 keeps everything.
Optional. Drop hotels cheaper than this per night, in your currency.
Optional. Drop hotels more expensive than this per night, in your currency.
Which kinds of places to keep. Google Hotels lists both hotels and vacation rentals for most cities.
[ "hotel", "vacation_rental"]For every hotel returned, also fetch the price on each booking site Google lists (about 10 to 40: Booking.com, Expedia, Hotels.com, the hotel's own site and more), with the cheapest site and the official-site price pulled out. Costs one extra request and one "provider-prices" charge per hotel. Hotels named in "Hotels by name" or "Hotel tokens" always include them.
With booking-site prices on, also return the Google link that opens each offer. Links are long, so they are off by default.
Remember the last price of every hotel and return only hotels that are new or whose price changed since the previous run with the same monitor name. Unchanged hotels are skipped and not charged. Schedule the run daily for a price-drop feed. The first run returns everything, as "new".
Name of the stored price history. Letters, digits and hyphens. Use a different name for each schedule so two schedules never share a history.
Stay compares a hotel only with its earlier price for the same check-in date and nights, which is right when your dates are fixed. Hotel compares with the last price seen for that hotel whatever the dates, which suits "N days from now" schedules.
Store today's prices as the starting point without returning or charging for any rows. Use it once to set a baseline.
Ignore price moves smaller than this percentage. For example 5 reports only changes of 5 percent or more. The baseline is only updated when a change is reported.
How long to wait between requests to Google when no proxy is used. With a proxy the pause is a quarter of this.
Hard limit on requests to Google for the whole run. The run stops and reports it when reached. Useful for tests.
Safety cap on residential proxy traffic, which is billed per gigabyte. The run stops when this is reached. Only matters when Google blocks the datacenter proxies and the run climbs to residential.
Optional. Leave empty and the run starts with a direct connection, then switches to Apify datacenter proxy and then to residential proxy only if Google blocks it. Pick a proxy here to force it from the start, for example a residential proxy in the country you set above.