If you only searched for LAX, you would have been routed to the wrong entrance to LAX (closer to the coast), so I have created a small landmark https://www.waze.com/editor/#?%23%3F=&z ... rks=797743
and now when you search you get LAX, Los Angeles, CA in the top two items of the search. So I know the search is using landmark information in the client and map editor... Creating the landmark may have not been in the best practices but I was able to get the search to work and it returns the correct location.
That's what I had to do for MSY. The landmark originally covered the entire property of the airport and as a result, was leading people coming from I-10 into a commercial/industrial area on the north side of the airport, where the streets dead-end at the edge of the airport property. The actual entrance to the airport is on the south side, a couple of miles away. I removed the name of the large landmark, drew a new one over the terminal building, and named that one.
Additionally, I drew some tiny landmarks for long term and short term parking and arrivals and departures, and now they lead you to the exact spots that take you to those places, and they show up at the top of the list.
These tiny landmarks would be better served by a POI point (which we don't have).
However, at this point, the only landmarks I've gotten to work in the search are the ones that have been set as Airport, hence the need for a test of all landmark types. I suspect that some are set to work with the search and some are not.