Why Google Flights Hides Wizz Air Prices (And How to See Them)

If you’ve searched Oslo to Gdansk on Google Flights and somehow ended up paying €180 when a friend got the same flight for €49 on Wizz Air, you’re not imagining it. Google Flights does not always show Wizz Air fares. On some of the most competitive European routes, the single cheapest option in the market is invisible on the most-used flight search engine in the world.

I ran into this one too many times building Flightmussy, so I started digging. Here’s what I found, which routes are most affected, and how you can verify the real price in under a minute.

The gap: what actually happens on Google Flights

Google Flights gets its flight data from a mix of sources: the Amadeus GDS, direct airline feeds, and ITA Matrix’s own pricing engine. Low-cost carriers like Wizz Air, Ryanair, and Widerøe do not always participate in those feeds. When they don’t, one of three things can happen:

1. The fare is shown, with a “Book on airline site” label — no booking path through Google, but the price is visible.
2. The flight itself is shown with no price — a greyed-out row labelled “Check airline” or similar, which users skip past.
3. The flight is omitted entirely — no row, no price, as if Wizz doesn’t fly that route at all.

The third case is the one that costs travellers money. Internally, Google Flights carries a flag that looks like _redirect_airline, attached to certain airline/route combinations where Google has decided the fare isn’t worth displaying without a direct booking path. The flight data is in the itinerary object, but it never reaches the user-facing price column.

Why Google does this

Nobody at Google will confirm this on the record, but the behaviour is consistent with two business realities:

First, distribution fees. Full-service carriers pay GDS distribution fees so their inventory flows into aggregators. Low-cost carriers like Wizz, Ryanair, and Widerøe make most of their margin on ancillary fees (bags, seats, priority boarding) that don’t convert well when the customer booked through a third party with limited up-sell real estate. So these airlines distribute selectively, or not at all, through GDS channels.

Second, monetisation alignment. Google Flights earns nothing directly from the search result, but it earns indirectly from Google’s hotel and travel ads, and from the Google ecosystem keeping travellers on-platform. A booking path that requires the user to leave Google for a ropy airline site with no ability to up-sell insurance or hotels is less valuable to Google than a booking on Booking.com or an integrated OTA. So Wizz, which would always send you off-site, is deprioritised.

The result is a ranking algorithm that systematically undercounts low-cost carriers on routes where they’re the cheapest option.

Which routes are most affected

From cross-checking routes while building Flightmussy, the Wizz gap shows up most consistently in three patterns:

• Central and Eastern Europe to the UK and Scandinavia. Routes like Warsaw – Oslo, Gdansk – London, Katowice – Stockholm, and Kraków – Edinburgh — Wizz operates these with thin margins and aggressive pricing, and Google Flights frequently omits them.
• Eastern Europe to Southern Europe. Warsaw – Barcelona, Budapest – Lisbon, Bucharest – Malaga — Wizz often undercuts Ryanair on these and isn’t shown.
• Niche routes to the Middle East and Caucasus. Wizz flies Abu Dhabi, Yerevan, Tbilisi, Amman — these barely register on Google Flights at all.

On Western European trunks like Paris – Rome or London – Madrid, the gap is narrower because Wizz doesn’t dominate those lanes. But on its bread-and-butter Central and Eastern European network, Wizz is regularly invisible — often enough that cross-checking directly is worth the 90 seconds.

How to verify manually (90 seconds)

1. Do your normal search on Google Flights. Note the cheapest price shown.
2. Open a second tab and go to wizzair.com. Enter the same route, same dates.
3. Compare. If Wizz’s price is lower than Google’s “cheapest,” you just found the real price.
4. Do the same check on ryanair.com for Ryanair-heavy routes.

Three tabs, 90 seconds. On the routes where Wizz is hidden, the direct fare is routinely tens of euros below whatever Google surfaces. This is the kind of thing a flight aggregator is supposed to do for you, but when the aggregator gets paid by the carriers it shows, it doesn’t have an incentive to surface the carriers that pay nothing.

What about Ryanair and Widerøe?

Ryanair has a similar history with Google Flights, though the relationship has swung back and forth. In 2024 Ryanair re-entered some GDS feeds, then partially withdrew again in 2025. On any given week, Ryanair fares might be fully visible, partially visible, or omitted depending on route.

Widerøe, Norway’s regional carrier, is the most extreme case. On Norwegian domestic routes like Oslo – Ørsta, Bergen – Sogndal, or Tromsø – Hammerfest, Widerøe is often the only operator. Google Flights on those routes regularly returns zero results. The flight exists. The price exists. Widerøe just never shows up.

Tools that surface Wizz fares

Rather than open three tabs for every search, the practical fix is a tool that queries the low-cost carriers directly. I built Flightmussy to do exactly this: it sends a direct request to Wizz Air’s timetable endpoint (the same endpoint Wizz’s own website uses) in parallel with the Google Flights query, and merges the results. Where Google shows nothing, you see the Wizz fare alongside. Same for Widerøe on Norwegian domestic.

Flightmussy is free, has no signup, no ads, and no tracking. It pays for itself through affiliate click-outs when you book — so the incentive is aligned with surfacing the cheapest real option, not the one that pays the most commission. There is also a “Crypto” button on every result that deeplinks to a Travala checkout if you want to pay in BTC, ETH, USDT, BNB, or AVA.

The pattern, concretely

What the gap looks like in practice on a typical Central European Wizz route, say Oslo to Gdansk on a shoulder-season weekend:

• Google Flights surfaces a one-stop routing on a full-service carrier at the top of its list.
• Skyscanner or Kiwi shows the Wizz direct — cheaper, shorter, but usually not the default suggestion.
• The Wizz website itself, or any tool that queries Wizz directly, shows the lowest fare of all three — frequently tens of euros below Google’s “cheapest.”

That gap between “cheapest on Google” and “cheapest on Wizz direct” is where the money is. On a couple travelling together it doubles. Multiplied across the number of Europeans booking Wizz routes on Google Flights every year, the total money left on the table is enormous — all because a meta-search isn’t really a meta-search when it quietly drops the cheapest carriers.

Action checklist

• If your route is Central or Eastern Europe, or to/from Nordic cities, always cross-check Wizz directly.
• If your route is Norwegian domestic, always cross-check Widerøe directly — or use a tool that queries it.
• If Google Flights shows you a route with one stop via LOT, Lufthansa, or SAS, and the price is over €120 for a sub-1000 km leg, there’s almost certainly a cheaper direct on a low-cost carrier.
• Save yourself the tabs and use a tool that already does the direct queries for you. Flightmussy is one. There are others — but the free, no-signup, no-tracking combination is rare.

The underlying point isn’t that Google Flights is broken. It’s a good tool, most of the time, for most users. The point is that the market for flight meta-search isn’t neutral. Aggregators surface what pays them. Knowing that, you know where to check yourself — or which tools were built to do it for you.