Trivago Redirect Caused Wrong JAZ Fanara Reservation

I made a hotel reservation via Trivago that automatically redirected me to Stayforlong, and because of an incorrect link on Trivago, I unintentionally booked the wrong property. My intention was to book Jaz Fanara Resort in Sharm El Sheikh, which is close to the main restaurants and the beach, but the Trivago link for Jaz Fanara Resort led to a Stayforlong page for Jaz Fanara Residence instead. As a result, on 22 May I booked Jaz Fanara Residence through Stayforlong for the dates 26 May to 1 June, without realizing that it was a different and much more distant location. My Stayforlong reservation / document number is 1283216301 and the security code is SFL-3E6C187***. The Jaz Fanara Residence is far from the main facilities, and due to my health situation this is a serious problem. I have a chronic condition, so I specifically need a room as close as possible to the main restaurants and beach area, that is, in the Jaz Fanara Resort part. We would never have booked the Residence if we had known it was a different listing and far away. I have a video recording that clearly shows Trivago’s Jaz Fanara Resort listing redirecting to Jaz Fanara Residence on Stayforlong, and as of the time of writing this, the same misleading redirection is still happening. I contacted the hotel and Stayforlong, explaining that the link on Trivago had redirected me to the wrong property and StayForLong informed us that our request was escalated to a higher level, but we have not received any response, and there is only one day left before check in. We are traveling from Ankara, Turkey, and this uncertainty just before our trip is causing us additional stress. I paid a total of ₺81,006 for this reservation, charged in Turkish lira. Since this mistake occurred because of the wrong redirect link on Trivago, I request either a full refund of the amount I paid or that my reservation be changed to Jaz Fanara Resort for the same dates, by coordinating with your partner Stayforlong. I kindly ask that Trivago urgently investigates this incorrect redirect and provides a fair solution.



