Google Flights Scraper

Search Google Flights for one-way or round-trip flight options and collect structured results without building a scraper.

📌 What is Google Flights Scraper?

Enter departure–destination pairs and your travel dates. The template runs in the cloud and returns one row per flight option, with 41 English-named output fields. Use airport codes such as SFO;SEA or unambiguous English city names such as Madrid;Milan.

💰 Pricing

$0.03 per 1,000 output rows. Requires an Octoparse Standard plan or above and sufficient account balance. Subscription and cloud usage limits still apply. This is a paid cloud template; it replaces the previous local OTD version.

📦 Output

Results include airlines, price and currency, departure and arrival airports and times, travel dates, duration, stops, route and result group. Additional columns include emissions, available booking information and JSON search context. Fields can be blank when the source response does not provide them.

Example from an actual test run; fares and availability change:

{
  "trip_type": "One way",
  "airlines": "Alaska",
  "price": "79",
  "currency": "USD",
  "route": "SFO-SEA",
  "outbound_date": "2026-11-18",
  "return_date": "",
  "time_range": "10:39 - 12:56",
  "duration": "2h 17m",
  "stops_label": "Nonstop"
}

For round trips, the search uses both travel dates and returns departing-flight options. It does not separately collect a full return-flight itinerary for each option.

🎯 Use Cases

• Compare flight options for a set of routes and dates.
• Collect fare snapshots for travel research and reporting.
• Repeat searches to build your own fare-monitoring dataset.

🐙 Why Octoparse

Use a ready-made input form, run the task in the cloud and export structured rows through Octoparse. No scraper code or separate proxy configuration is needed.

📝 Input

• One Way or Round Trip: choose One Way or Round Trip.
• Departure and Destination (up to 100): enter one pair per line, separated by a semicolon. Examples: SFO;SEA, Madrid;Milan. You can also import a file. Each pair is a separate search; origins and destinations are not cross-combined.
• Departure Date: required. Accepts yyyy-mm-dd, yyyy/mm/dd or mm/dd/yyyy.
• Return Date: required for Round Trip; ignored for One Way. It cannot be earlier than the departure date.
• Advanced / Previous Inputs: optional Departure Airport Code(s) and Arrival Airport Code(s) support previous input workflows. For normal use, fill the paired-route list above.
• Exclude Basic Economy: apply the fare filter where the response supplies relevant information.
• Fetch Booking Options: include available links and a Google Flights search-page link. This does not book tickets or guarantee airline booking links.

🚀 How to Use

1. Open the template and choose One Way or Round Trip.
2. Enter up to 100 route pairs and the departure date. Add the return date for a round trip.
3. Check your account balance, then start the cloud task.
4. Review the returned rows and export the data using Octoparse.

⚠️ Limitations

Results and fares depend on the selected routes, dates and current Google Flights availability. The number of rows varies. Only flight options available in the retrieved search response are returned; this is not a guarantee of every possible flight or fare. Some fields may be empty. The template does not complete bookings.

💡 Tips

Start with one route. Use IATA airport codes when a city name is ambiguous. Keep your route pairs on separate lines and check the date format before starting. Save the search time with exports when comparing fare snapshots.

❓ FAQ

Can I scrape round-trip flights?

Yes. Select Round Trip and provide both dates. The output lists departing-flight options for those dates, rather than separate rows for both legs.

How many routes can I enter?

Up to 100 departure–destination pairs per task. The number of returned flights per route varies.

Is this template free or local?

No. The current template runs in the cloud, requires Standard or above and costs $0.03 per 1,000 output rows.

Are all output fields always populated?

No. Values depend on what the source search response provides. Output column names are in English.

🔗 Related Templates

See the existing recommendations in the Related Templates tab.