How To Actually Use Google Flights When You're Leaving Chicago
Most people treating Google Flights like a fancy Expedia don't know what they're missing. I spent years booking flights for a logistics company out of O'Hare and Midway, and the tool works completely differently if you stop scrolling and start understanding the search behavior behind the results. The basic search is obvious, but the date grid and price graph are where most people give up too early. When I searched from ORD to SFO on a Tuesday morning using just the default calendar view, I kept seeing prices around $320 round trip. The trick is clicking the date grid and looking at the full month view. Prices dropped to $198 the week before and $187 two weeks out. That's not a rounding error. The flex dates option is another thing people skip. If you're traveling from Chicago and your dates are flexible by even a single day, toggling flexible dates can show you options that aren't visible in the standard search. I found a Wednesday departure out of ORD to London Heathrow at $412 round trip when the same route on Tuesday or Thursday was showing $580. The system just needed to see the range.
Track prices is straightforward but underutilized. You set it and forget it, which is fine, except the alerts sometimes arrive hours late. I once got a price drop alert for a flight from MDW to Austin four hours after the fare had already jumped back up. Checking the flight manually every couple of days while the tracker runs in the background is more reliable than trusting the email alone. One specific problem I ran into repeatedly involved the near-airports feature when searching from Chicago. If you're flying out of Midway and the top results are all showing departures from O'Hare, you might assume there's nothing better available. But the nearby airports toggle defaults to including both, which muddies the results. I had to uncheck O'Hare and search MDW-only to actually see which Southwest routes were competitive. Without that step, I was comparing apples and oranges and making the wrong call half the time. The baggage filter is another detail that trips people up. The fare comparison on Google Flights sometimes doesn't include carry-on fees for basic economy tickets from certain carriers. When I was booking Spirit or Frontier flights out of Chicago, the listed price looked good until checkout. The base fare would be $89 but adding a carry-on bag pushed it to $134. Always click through to the airline's site before committing to see the real total.
Multi-city searches are built into the interface but most people don't use them properly. You can string together three or more cities without returning to the origin point. I used this for a trip that went Chicago to Denver to Phoenix to Las Vegas and back to Chicago, and the multi-city tab saved me at least forty minutes compared to running individual searches. The routing isn't always optimal price-wise, so cross-check with separate one-way searches if time allows. There are clear limitations though. Google Flights doesn't show every airline. Southwest doesn't appear at all. If you're booking a trip where Southwest fares matter, which they do from Midway, you need to check Southwest separately. The same goes for some international carriers that don't share fare data with Google's aggregator. You'll miss deals if you treat Google Flights as your only tool. The interface also occasionally mislabels layover times, especially on complex international routes. I found a flight from ORD to Tokyo listed with a two-hour layover in Seoul that was actually seventy-five minutes when you dug into the details. The connection was technically legal but not realistic if either flight was even slightly delayed. Always double-check the actual connection time before buying, especially on routes with tight layovers.
Get the Full Details
For the best results, combine Google Flights with a direct airline check. Use the tool to find the date and route, then go straight to the airline's website to book. This avoids the middleman markup that sometimes appears when you click through Google's booking partners. The fare might be identical, but occasionally it's lower on the airline side, and you get better customer service if something goes wrong. The search itself takes about three to five minutes if you're familiar with the interface. Learning the features properly might add ten minutes upfront, but it pays off immediately. I've seen people waste twenty minutes bouncing between three different booking sites when a single Google Flights search with the right filters would have settled it in under two.
