I'm working on a Hotel chain website that has custom back buttons on their hotel pages. The back button takes users to the previous level in the navigation.
E.g: A user in "Hotel page" clicks "<- Back" and goes to "Hotels in Madrid"
This has been working fine, but now the site is going to grow. We're going to introduce changes in the Information Architecture and new pages like Hotel collections, Restaurant pages, etc. This means that there will be multiple paths for users to get to the hotel pages, so my question is... What should happen to the custom back button?
I was thinking of 2 options:
- a) Remove the custom back button because it adds too much complexity.
- b) Make the button dynamic (e.g: <-Back to [dynamic_copy]) and try to establish a set of rules depending on the users previous path.
What do you think? Do you have another idea? Thank you