Google Travel Explore Scraper

Collect destination recommendations from public Google Travel Explore pages. A record can include trip settings, displayed flight prices and options, hotel or rental details, seasonal information, weather, and destination questions when those details are present on the page.

Google Explore controls its recommendations and prices. Dates, fares, hotel prices, and conditions can change, and missing facts are not estimated.

How to use

Provide one or more destination searches in queries, or use a public Explore URL in startUrls. Google chooses the departure context for a generated query; use an Explore URL configured with trip controls when you need a particular origin.

{
  "queries": ["New York"],
  "maxItems": 10,
  "page": 1,
  "maxPages": 5,
  "includeDestinationQuestions": true,
  "renderJavaScript": true
}

Input

Input	Description	Default
queries	Destination terms used to search Google Travel Explore.	—
startUrls	Public Google Explore URLs. URLs and queries can be combined; duplicates are removed.	—
maxItems	Maximum destination records across all inputs.	25
page / maxPages	Select a bounded window of ten destination cards within each response. This does not request more remote pages.	1 / 10
includeDestinationQuestions	Include visible question prompts and answer or citation text when present.	true
renderJavaScript	Use a standard browser to reveal destination cards and details that are not present in the initial page response.	false
proxyConfiguration	Optional Apify Proxy configuration for public Google pages.	—

Output

Each dataset item represents a destination recommendation. Available information can include:

• Trip context: destination, country, origin, trip type, passenger count, travel class, suggested date range, and trip duration.
• Flights: displayed destination-card fare, stops, duration, airline options, and price comparisons when shown.
• Stays: dates, accommodation choices, stay price, hotel count, and hotel options.
• Season and weather: peak/off-season periods, monthly weather, temperatures, and popularity labels.
• Destination questions: visible topics, prompts, and any available answer and citations.

Prices from destination cards, airlines, stays, and hotels remain in separate fields. Dates retain Google’s displayed precision; the Actor does not add an unstated year. A section that was not available may be null; an observed section with no entries may be an empty array.

Example dataset item:

{
  "destinationName": "Example destination",
  "destinationCountry": "Example country",
  "recommendationPosition": 1,
  "originName": "Example origin",
  "tripType": "round_trip",
  "passengerCount": 1,
  "travelClass": "economy",
  "dateWindowText": "1-week trip in the next 6 months",
  "tripDateRangeText": "Oct 18 – 27",
  "flightPriceText": "$250",
  "flightCurrencyCode": "USD",
  "flightStopsText": "1 stop",
  "flightDurationText": "3 hr 10 min",
  "stayPriceText": "$125 /night avg",
  "stayCurrencyCode": "USD",
  "peakSeasonRangeText": "Dec – Mar",
  "temperatureUnit": "F",
  "monthlyConditions": [
    {
      "monthName": "October",
      "weatherDescription": "Partly cloudy",
      "temperatureRangeText": "83° / 77°"
    }
  ],
  "destinationQuestions": [
    {
      "topic": "All",
      "question": "What is useful to know about this destination?",
      "answerText": null
    }
  ]
}

The Output tab shows the available result fields. Run summary information is available with the run output in Apify.

Limits and responsible use

Results depend on what Google Explore displays for the selected page and locale. Browser rendering can increase run time. The Actor does not sign in or bypass access checks.

Use public travel information responsibly and follow applicable privacy requirements and Google terms. This Actor is not affiliated with Google.