Change domain aliases from 302 (temporary) to 301 (permanent)
-
- https://docs.cloudron.io/apps/#aliases
- https://stackoverflow.com/questions/1393280/http-redirect-301-permanent-vs-302-temporary
I believe 301 redirects are the correct here, please
(otherwise you end up with a random mix of the aliases in SERPs)
If you have some reason or use for 302/Temporary, then maybe make that optional, but I believe most of what this will be used for should be 301/Permanent.
Especially important when you've made a website under a dev URL that got indexed somehow, and then moved it to www to go live. (Yes, I know, should block dev URLs with robots.txt, if you remember.)
-
Aliases don't redirect at all, it's up to the app to do whatever it wants. Maybe your app is misconfigured?
Only redirections redirect - https://docs.cloudron.io/apps/#redirections . 302 is correct here since it allows people to move around URLs as they see fit without having to worry about long term implications.
-
Aliases don't redirect at all, it's up to the app to do whatever it wants. Maybe your app is misconfigured?
Only redirections redirect - https://docs.cloudron.io/apps/#redirections . 302 is correct here since it allows people to move around URLs as they see fit without having to worry about long term implications.
@girish Sorry, wrong choice of words then, I mean redirections.
It's WordPress. I'm not sure you can do a 302 to a 301. Natural place for this, being that's it domain redirect and not path, is at the DNS level, since you're already offering one type of 30x in that setting.
It's a long term implication I need (positive implication).
How about an option dropdown for "301 Permanent", "302 Temporary" on Redirections, then please?
If I'm doing my job right, it will always be towards achieving positive permanence, as quickly as possible
-
I actually don't mind changing the default to 301 instead of the current 302. I think the most common case for redirections is the www -> bare domain or vice versa. In that case, the 301 is best.
We did 302 initially because we thought when people are moving around domains it's more convenient.
-
I actually don't mind changing the default to 301 instead of the current 302. I think the most common case for redirections is the www -> bare domain or vice versa. In that case, the 301 is best.
We did 302 initially because we thought when people are moving around domains it's more convenient.
@girish With 302, search engines can end up with a mix of subdomains in the SERPs, whereas with 301, they'll update it to the authoritative final destination. I think 302 is more for if redirecting to somewhere where you wouldn't later have the control to redirect a 301 back.
-
G girish marked this topic as a question on
-
G girish has marked this topic as solved on
-
Cloudron community teamwork wins again
