For purposes that concern at most a handful of people, I have often set up HTTP 301 redirects to link to a Google Drive document. For example, instead of linking to [a Google Forms link, I had one here but it made my post get autoremoved] I would link to example.com/form, using a 301 redirect to move users to the former address.
However, when I read about HTTP 301 redirects online, I always read things like "permanently moved", "old url", "let search engines know the address was updated", etc. These don't apply to my use case: nothing was moved or changed, I just want to create a shortcut.
Right now I am in charge of a larger website (larger as in more users), and I would like to add some of these shortcuts. But first I would like to hear from someone more knowledgeable on web development: is this use case for a HTTP 301 redirect alright? Or might it cause unintended side effects?
Thanks!
However, when I read about HTTP 301 redirects online, I always read things like "permanently moved", "old url", "let search engines know the address was updated", etc. These don't apply to my use case: nothing was moved or changed, I just want to create a shortcut.
Right now I am in charge of a larger website (larger as in more users), and I would like to add some of these shortcuts. But first I would like to hear from someone more knowledgeable on web development: is this use case for a HTTP 301 redirect alright? Or might it cause unintended side effects?
Thanks!