Our ViewsHello Airbnb family,
I hope my message finds you...
Latest reply
Our ViewsHello Airbnb family,
I hope my message finds you well.
I started to handle a resort (Hosteria in Spanish in my ho...
Latest reply
My listing is a lakefront cottage on Lawrence Pond on Cape Cod MA, but Elevate is assigning its location to the wrong lake (Peter's Pond) that is about 2 miles away. Therefore its category is only "Lake" (which means within a 10 minute walk) instead of "Lakefront". In fact, Elevate has grouped about a dozen homes not on Peter's Pond to that lake. I also see this is true across the entire region where homes are assigned to lakes that they're not located on.
My title, description, photos, and reviews all clearly indicate that the home is a lakefront property. However, my request to add the "Lakefront" category has been denied 4 times in a row.
I've called Airbnb about half a dozen times seeking help, but as everyone knows none of their representatives can contact Elevate (which is a third party department) directly about any problems. The representatives agree that this is a problem, but no one knows what to do other than advise the host to submit a request through the app, which I've done repeatedly with photos and detailed explanations. I get automated responses, but no resolution or explanation.
What seems to be happening is that the Elevate algorithm can only handle a limited number of geographic points, and then uses those few points as a reference for an entire category. Because there are probably tens of thousands of lakes around the country, they only select a few in each geographic area. However, that negatively affects the other 90 percent of the lakefront homes that are on their own lakes by not being included in the "Lakefront" category.
One solution would be for Elevate to rely less on geographic locations on a few random points, and instead looks at the photos, titles, and descriptions more carefully when a request is made as often as I have made. Can someone share any insight on how to get Elevate's or Airbnb's attention that the algorithm is flawed? The reason I'm pushing for this correction is that I'm losing bookings and potentially higher rental income because a "Lakefront" category is more exclusive and valuable than the normal "Lake" category.
Yes!!! I'm now in the Lakefront Category. And for the first time in 2 years, I'm listed on the right lake (Lawrence Pond)!! I'm showing up in the Lakefront category! There is hope in the world! I also see all of my neighbors no longer mis-labeled in terms of their lakes.
Now I just need Beach and Beachfront to be added. But one step at a time!!
Actually, I just Googled and it says that beach and beachfront only apply to the ocean, so you were right about that Joan. It's a shame because there are many lakefront homes around the world that have beautiful beaches and lots of sand. Maybe they should change the term to oceanfront homes to "Oceanfront" since many lakefront homes also have beautiful beaches and since beaches are defined by the sand next to water and not necessarily how big the body of water is.
Totally agree with that. It would be a win-win for Hosts and Airbnb if this was corrected. I'm just thinking about all the beautiful lakes and rivers around the world with gorgeous beaches!
Well...hate to be the bearer of bad news but....
Looks like Airbnb has removed the proximity callout to Lawrence Pond on your listing and replaced it with "comfortable beds" 🤥
Perhaps they realize the whole "walking distance" or distance to a particular beach feature wasn't working correctly and just removed it entirely?