Http:// to https:// 301 or 302 redirect
-
I've read over the Q & A in the Community, but am wondering the reasoning behind this issue.
I know - 301's are permanent and pass links, and 302s are temporary (due to cache) and don't pass links. But, I've run across two sites now that 302 redirect http:// to https://.
Is there a valid reason behind this? From my POV and research, the redirect should 301 if it's permanent, but is there a larger issue I am missing?
-
Mike,
This is a really interesting question. The assumption is they are wanting a user to access the site securely every time. I cannot think of a reason for this not to be 301. I am assuming it is not from a single error page or other "event." I am guessing that someone within the Moz community will have an answer; it may be that they are doing it incorrectly.Best
-
It doesn't totally answer it I don't think, but it may shed light onto the issue. It could be a server specific/site specific kind of need as to why they are doing this.
-
Thanks for that article. I've always thought it to be a hard and fast rule that 301s should be used over 302. But the more I've run into https:// (with very brilliant IT guys), they always use 302s.
I've always wanted to understand the implications behind using 302s from the IT perspective - because from an optimization perspective, there is normally no doubt a 301 should be used.
Thank you.
-
I am not sure what big IT gurus think before they add 302 over 301 but if you ask me I have a simple rule that I apply before deciding which redirection to use.
- Obviously there is no hard and fast rule that you should use 301 over 302 redirections.
- Always keep it simple, you need to flow the link juice to the next page, go for 301 and if you don’t go with 301.
Hope this helps!
-
301 permanent redirect. Its the best solution and google too likes it.
hope it helps
-
Our IT guys do the same with our sites and they have no good reason for doing it.