Google Hotels Price Monitor

Track hotel prices on Google Hotels for any dates, and get only what changed since your last run: price increases, drops, sold-out hotels and hotels back in stock.

Built for scheduled monitoring: set it to run daily, and use rolling dates such as "7, 14 and 30 days from today" so the dates move forward automatically.

Who it's for

• Hotels and riads watching competitors' rates before adjusting their own.
• Travel agencies and tour operators tracking prices for upcoming stays.
• Analysts building price history for a destination.

What you get

For each hotel and check-in date:

Field	Example
hotelName	Savoy Le Grand Hotel Marrakech
checkIn / checkOut / nights	2026-12-02 / 2026-12-04 / 2
price / currency / priceText	1993.14 / MAD / "MAD 1,993"
previousPrice / priceChange / priceChangePct	2134.63 / -141.49 / -6.63
changeType	new, up, down, unchanged, sold_out, back_in_stock, currency_changed
stars / hotelClass	5 / "5-star hotel"
rating / reviewCount	4.1 / 3957
latitude / longitude / countryCode	31.618 / -8.010 / MA
googleUrl / entityId	Link to the hotel on Google Hotels
trackedHotel / matchScore	The name you entered and how closely the result matched it (0.75 to 1.0)

A summary of every run (lookups, failures, hotels not found) is saved as OUTPUT_SUMMARY in the run's key-value store.

How to use it

Track specific hotels. Add them under Hotels to track, with the city for accuracy:

{
  "hotels": ["Savoy Le Grand Hotel Marrakech", "La Mamounia Marrakech", "Riad Qodwa Marrakech"],
  "checkInDaysAhead": [7, 14, 30],
  "nights": 2,
  "onlyChanges": true,
  "monitorName": "marrakech-competitors"
}

Track a whole destination. Use Destination searches, for example hotels in Marrakech or 5 star hotels in Paris. Each search returns up to about 20 hotels per date.

Monitor daily.

1. Run it once, to record today's prices.
2. Create a Schedule in Apify Console (for example every morning at 7:00).
3. Turn on Only output changes, and keep the same Monitor name, so each run compares against the previous one. Minimum change (%) (default 1%) filters out the cent-level drift caused by Google's live currency conversion.
4. Optionally, connect an integration (email, Slack, Google Sheets, webhook) to get the changes delivered.

Currency and proxy

Google picks the currency from the visitor's location, so the proxy country decides the currency: US gives USD, GB gives GBP, and so on. Don't use EU proxy countries, because Google shows them a cookie-consent page instead of prices. Residential proxies are the most reliable option.

Reliability

• No browser is used: each lookup is a single fast page request.
• A blocked or empty page is retried with a fresh proxy session.
• Results are only kept if Google applied your dates, so prices are never silently mixed up with other dates.
• If Google changes its page layout, the run fails with a clear message instead of returning wrong data.

Limitations

• The price is the lowest nightly price shown on Google Hotels for that stay, not a breakdown per booking site.
• Destination searches cover Google's first results page (up to about 20 hotels).
• When a named hotel has no availability for a date, Google often shows no hotel list. The hotel is then listed under trackedHotelsNotFound in the run summary.
• Google's results vary slightly between requests. Check matchScore the first time you track a new hotel.

Pricing

Pay per use:

• Search page: charged once per Google results page checked.
• Hotel price: charged per result row.

With Only output changes turned on, unchanged prices are not output and not charged as rows.

Questions or problems

Open an issue in the Issues tab. Layout changes on Google's side are usually fixed within a few days.