Google Hotels Scraper API 💰$0.7/1k avatar

Google Hotels Scraper API 💰$0.7/1k

Pricing

from $0.40 / 1,000 results

Go to Apify Store
Google Hotels Scraper API 💰$0.7/1k

Google Hotels Scraper API 💰$0.7/1k

💰$0.7/1k — Scrape Google Hotels: nightly & total prices, ratings, reviews, deals, star class, coordinates, address, phone & website. One structured row per property (JSON/CSV). Track price changes across runs, enrich every row from Google's own data. API + MCP for AI agents.

Pricing

from $0.40 / 1,000 results

Rating

0.0

(0)

Developer

Black Falcon Data

Black Falcon Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 hours ago

Last modified

Share

What does Google Hotels Scraper API do?

Google Hotels Scraper extracts structured hotel listings from Google Hotels (google.com/travel/search) for any destination and date range. Every hotel carries the nightly price and the whole-stay total, rating, review count, star class, property type, and Google's own deal text. Each row also carries the property profile — exact coordinates, website, check-in/check-out times, star class, property type and photo gallery — at no extra charge and with no second lookup; the property-detail upgrade adds the full street address, phone and a Google Maps link. Search many destinations and date ranges in one run, run incrementally to track rate changes across runs, and export straight into a connected app via MCP.

New to Apify? Sign up free and use the included $5 monthly platform credit to test this actor.

Key features

  • 📍 Full property profile on every row — every hotel arrives with exact coordinates, website, check-in and check-out times, star class, property type and photo gallery — not just a name and a price. No extra lookup, no extra charge: it is part of the same result. Full street address, phone and Google Maps link come with the property-detail upgrade.
  • 💵 Nightly and total price — both the nightly rate and the total for the whole stay, in the currency you ask for, plus Google's own deal text ("23% less than usual") kept in its own field instead of glued to the hotel name.
  • ♻️ Incremental mode — recurring runs emit and charge only for hotels that are new or whose price, rating or cancellation terms changed. The first run builds the baseline; later runs emit only NEW / UPDATED records (UNCHANGED and EXPIRED are opt-in). Ideal for daily rate monitoring.
  • 🎯 Batch searches — search many destinations and date ranges in one run. Results are de-duplicated on Google's own property identity, so a hotel matching several searches is returned — and billed — once.
  • 🧹 Empty-field stripping — drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards that already handle missing fields gracefully.
  • 🔌 MCP connectors — export results into a connected app via Apify's MCP connectors — a clean run-summary, no glue code or AI. Opt in with the App connector field; more destinations open up as Apify's catalog grows.

What data can you extract from Google Hotels?

Each hotel record includes identity (propertyToken, name, title, sourceUrl), the stay you searched (searchQuery, checkIn, checkOut, nights), pricing (priceNightly, priceTotal, priceDisplay, currency, dealText), and reputation (rating, reviewCount, amenityHints). Every record also carries the property profile: latitude, longitude, countryCode, website, checkInTime, checkOutTime, hotelClass and hotelClassLabel (for example 3 and "3-star tourist hotel"), propertyType and propertyTypeTags, thumbnailUrl and the photo gallery — plus a scrapedAt timestamp. The property-detail upgrade (includeReviews) fills addressLine, phone and mapsUrl from each property page. Incremental runs add a changeType of NEW / UPDATED / UNCHANGED / EXPIRED.

Input

Configure the actor through the input schema in Apify Console.

Key parameters:

  • destination — Where to search — a city, an area, or a landmark (e.g. Paris, or hotels near Times Square, New York).
  • checkIn — Check-in date (YYYY-MM-DD).
  • checkOut — Check-out date (YYYY-MM-DD). Must be after check-in.
  • adults — Number of adult guests. (default: 2)
  • childrenAges — One age (0–17) per child — Google Hotels prices each child by age, so the list is also the number of children. Leave empty for adults only.
  • market — Point-of-sale country (e.g. us, gb, de, jp). Google prices by this location, so it also decides the currency you see — the currency each hotel was priced in is reported on every record. There is no separate currency control: Google Hotels ignores one. (default: "us")
  • language — Language code (e.g., en, de, fr). (default: "en")
  • searches — Search several destinations or date ranges in one run. Each entry takes the same fields as a single search: destination, checkIn, checkOut, and optionally market / language.
  • minPrice — Only keep hotels priced at or above this amount per night. In the currency Google prices the search in (see each record's currency). Leave empty for no lower bound.
  • maxPrice — Only keep hotels priced at or below this amount per night. Leave empty for no upper bound.
  • minRating — Only keep hotels with a guest rating at or above this value (0–5).
  • minHotelClass — Only keep hotels of at least this star class (1–5).
  • ...and 17 more parameters

Input examples

Hotels in a city for a date range — Search a destination for a specific stay. Returns every hotel on the results page with price, rating, and full property details.

→ Hotel records with nightly and total price, rating, review count, star class, property type, coordinates, website, and check-in/check-out times (full address and phone come with the property-detail upgrade).

{
"destination": "Paris",
"checkIn": "2026-08-01",
"checkOut": "2026-08-03",
"adults": 2,
"maxItems": 20
}

Hotels near a landmark — The destination is free text, so an area or a landmark works as well as a city name.

→ Hotel records for properties Google associates with that area, each carrying exact coordinates (full address via the property-detail upgrade).

{
"destination": "hotels near Times Square, New York",
"checkIn": "2026-09-10",
"checkOut": "2026-09-12",
"maxItems": 20
}

Rate monitoring (incremental) — Re-run on a schedule to detect rate changes. Each run compares against the previous snapshot and emits only what changed.

→ Records tagged NEW / UPDATED / UNCHANGED / EXPIRED — only new and changed hotels are pushed and charged.

{
"destination": "Barcelona",
"checkIn": "2026-08-01",
"checkOut": "2026-08-08",
"incremental": true
}

Several cities in one run — Batch multiple destinations and date ranges. Results are de-duplicated on Google's own property identity across searches.

→ One row per hotel across all searches, each tagged with the search that found it.

{
"searches": [
{
"destination": "Paris",
"checkIn": "2026-08-01",
"checkOut": "2026-08-03"
},
{
"destination": "Rome",
"checkIn": "2026-09-10",
"checkOut": "2026-09-14"
}
],
"maxItems": 40
}

Local market and currency — Set the point-of-sale market and language to see rates as a local traveller would. Google prices by market, so the market also decides the currency — each record reports the currency it was priced in.

→ Hotel records priced from the requested point of sale, in that market's local currency.

{
"destination": "Tokyo",
"checkIn": "2026-10-05",
"checkOut": "2026-10-09",
"market": "jp",
"language": "en"
}

Family stay with children — Add a child's age (0–17) for each child — Google prices each child by age, so the list of ages is also the number of children. Adults-only searches leave it empty.

→ Hotel records priced for the exact party — the ages change the nightly and total price the same way they do on Google Hotels.

{
"destination": "Orlando",
"checkIn": "2026-12-20",
"checkOut": "2026-12-27",
"adults": 2,
"childrenAges": [
5,
9
]
}

Output

Each run produces a dataset of structured flight records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example flight record

{
"propertyToken": "ChkIjqiq6fm0zNFYGg0vZy8xMWc2bWMwcnZxEAE",
"title": "Best Western 11BAUER Paris Saint-Ouen",
"sourceUrl": "https://www.google.com/travel/hotels/entity/ChkIjqiq6fm0zNFYGg0vZy8xMWc2bWMwcnZxEAE",
"scrapedAt": "2026-07-16T09:00:00.000Z",
"searchQuery": "Paris 2026-08-01 to 2026-08-03",
"checkIn": "2026-08-01",
"checkOut": "2026-08-03",
"nights": 2,
"name": "Best Western 11BAUER Paris Saint-Ouen",
"priceNightly": 68,
"priceTotal": 172,
"priceDisplay": "$68",
"currency": "USD",
"rating": 4.7,
"reviewCount": 138,
"amenityHints": [
"Free Wi-Fi",
"Air conditioning",
"Restaurant"
],
"latitude": 48.9120795,
"longitude": 2.3364507999999997,
"addressLine": "Saint-Ouen-sur-Seine, France",
"website": "http://www.hotel-11bauer.com/",
"checkInTime": "3:00 PM",
"checkOutTime": "11:30 AM",
"hotelClass": 3,
"hotelClassLabel": "3-star tourist hotel",
"propertyType": "Hotel",
"propertyTypeTags": [
"gcid:hotel"
],
"thumbnailUrl": "https://lh3.googleusercontent.com/gps-proxy/ALd4DhEauwvvFfNG7uucsIFhE3prTODLAKSQsj8-ujJxtfFKW9dvhszYfG8CimyVR1o39bpmzzAiWPG6z0o3BB0eR7OHuzMd8rEqqO99CpEugvPuNmIS_D_lFOyVcOIrW_4mppDtOO05k05rA42szPosTC1q...",
"mapsUrl": "https://maps.google.com/maps?hl=en&gl=US&um=1&ie=UTF-8&fb=1&sa=X&ll=48.9120795,2.3364508&z=12&ftid=0x0:0x58a331a79d2a940e&q=Best+Western+11BAUER+Paris+Saint-Ouen",
"countryCode": "FR",
"trackedHash": "6e28c2a8a482dfdb964a2e24d35788c2c28cd812"
}

Incremental fields

When incremental is enabled, each record carries a changeType field — one of NEW, UPDATED, UNCHANGED, or EXPIRED — computed by comparing against the previous run's snapshot (keyed per search, or by your own stateKey). A hotel counts as UPDATED when its price, rating, or review count changed; renames and other cosmetic edits do not trigger it. Default output includes NEW and UPDATED; set emitUnchanged: true to also receive UNCHANGED. EXPIRED records are emitted as lightweight tombstones when a previously seen hotel drops out of the results, and are never charged.

How to scrape Google Hotels

  1. Go to Google Hotels Scraper API in Apify Console.
  2. Configure the input.
  3. Set maxItems to control how many results you need.
  4. Click Start and wait for the run to finish.
  5. Export the dataset as JSON, CSV, or Excel.

Use cases

  • Monitor nightly rates for the hotels and dates you care about and detect price drops across runs.
  • Build a hotel dataset with coordinates for mapping and market research — add full address and phone via the property-detail upgrade for lead generation.
  • Compare accommodation prices across several cities or date ranges in a single run.
  • Benchmark a property against its local competitors on price, rating, review count, and star class.
  • Feed structured hotel data into travel analytics, dashboards, or LLM pipelines via MCP export.

How much does it cost to scrape Google Hotels?

Google Hotels Scraper API uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

  • Run start: $0.005 per run
  • Per flight (primary event): $0.0007

You are billed only for the events your run actually triggers. Prices below are the Free plan tier; higher Apify plans (Bronze → Diamond) pay progressively less per event, down to roughly 5× lower on the top tier.

EventPrice (Free tier)Charged when
Run start$0.005 (one-time)Charged once when the run starts (scales with memory, minimum one).
Result (primary)$0.0007Charged per hotel returned.
Property details$0.003Opt-in add-on. Charged once per hotel whose full property detail is collected: street address, phone, Google Maps link, room types, neighborhood write-up, rated landmarks, and the upgraded review summary (rating breakdown, per-category sentiment, sources and highlights). Only billed when 'Include full property details' is enabled and the detail page returns data.

Example costs (primary event only — other events above add cost when they fire):

  • 10 results: $0.012
  • 25 results: $0.022
  • 100 results: $0.075
  • 200 results: $0.14
  • 500 results: $0.35

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of flights that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 250 results per run, daily polling (30 runs/month). Event-pricing examples scale linearly with result count.

Numbers below are for the primary Result event. Other events (Property details) are billed separately when they fire.

Churn rateFull re-scrape run costIncremental run costSavings vs full re-scrapeMonthly cost after baseline
5% — stable niche query$0.18$0.01$0.17 (92%)$0.41
15% — moderate broad query$0.18$0.03$0.15 (83%)$0.94
30% — high-volume aggregator$0.18$0.06$0.12 (68%)$1.72

Full re-scrape monthly cost at daily polling: $5.40. First month with incremental costs $0.58 / $1.09 / $1.85 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage (compute and proxies) is billed separately by Apify based on actual consumption. Incremental runs consume less on result processing, though fixed per-run overhead stays the same.

FAQ

How many results can I get from Google Hotels?

The number of results depends on the search query and available flights on Google Hotels. Use the maxItems parameter to control how many results are returned per run.

Does Google Hotels Scraper API support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed flights on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Google Hotels Scraper API with other apps?

Yes. Google Hotels Scraper API works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Google Hotels Scraper API with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Google Hotels Scraper API through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use excludeEmptyFields to keep payloads manageable for LLM context windows.

This actor extracts publicly available data from Google Hotels. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

  1. Sign up — $5 platform credit included
  2. Open this actor and configure your input
  3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Disclaimer

General

This actor is a data and analytics tool. It does not sell, book, or reserve accommodation, and it is not affiliated with, endorsed by, or acting on behalf of any hotel, booking site, travel agency, or Google. It uses no hotel or agency logos, brand artwork, or affiliation claims, and reproduces only factual property names as publicly displayed. You are solely responsible for how you use the data this actor provides. Prices, ratings, availability, and other values are sourced from publicly displayed Google Hotels data; they are indicative, point-in-time, and not guaranteed. Verify all rates, taxes and fees, cancellation terms, and availability directly with the property or seller before booking. Use is at your own risk.

Prices and fees

Nightly and total prices are the figures Google Hotels publicly displays for the dates and occupancy you searched. They may exclude local taxes, resort or cleaning fees, and other charges added at checkout, and they change frequently — a price returned by this actor may differ from the price you are offered at booking time. This actor reports prices only; it gives no booking advice.

Property information

Coordinates, addresses, phone numbers, websites, check-in and check-out times, star class, and property type are reproduced as published by Google Hotels. They may be incomplete, outdated, or wrong, and this actor does not independently verify them. Contact details are provided as published business contact information. If you use them to contact properties, you are responsible for complying with all applicable marketing, privacy, and electronic-communications laws (including GDPR and equivalent regimes) in your jurisdiction and theirs.