Translate-plugin: ForceRedirect, redirects as 302.

[CptMeatball]

As the title implies; all redirects are redirected as 302. This is the default for Laravel's Redirect::to method. I'm no SEO expert but shouldn't it redirect as 301, so the link value is sent tot the redirect page?

[CptMeatball]

It seems to me that a force redirect acts a permanent action, so there at least should be an option to set the status of the redirect.

[vannut]

I see an additional config-parameter incoming for config/config.php :)

[LukeTowers]

Could I have some more context on this issue please?

[vannut]

At the moment, when you enable forceRedirectUrl the plugin redirects with Laravels Redirect::to() Which in its turn defaults to using a 302 as status code.

When you enable prefixDefaultLocale (which is the default for the plugin) you automatically discard the use of your root example.com/ and choose to use example.com/en. SEO wise this is a permanent move (we will never use the / anymore) so we should return a 301 - permanent redirect.

At least that is my small understanding of 301/2/7 redirects. Maybe somebody else with more SEO knowledge can weigh in. @CptMeatball and I looked at some major websites/shops here in the NL and how they handled the redirect. Both bol.com and klm.com use 301-redirects.

Regardless of that, it might be wise to go ahead and substract the redirect status number in the config.php so anybody can decide for them selves.

[CptMeatball]

Exactly that.

[LukeTowers]

So what are the proposed solutions to this? I'm not sure I see the value in providing a config parameter for this unless there's a reason for them to redirect with a 302 on a request path that will never be used.

[CptMeatball]

unless there's a reason for them to redirect with a 302 on a request path that will never be used.

Not sure who you mean with "them", but the arguments stay the same:

• 302 is for temporary redirects
• 302 redirects do not carry over the pagerank to the redirection
• ForceRedirects forces the locale to be prefixed to the URL. So users will never hit a unprefixed URL. They'll always be redirected to the prefixed URL.

I think a proposed config parameter, or a component parameter which both default to 302 (to make sure that old installs don't suddenly redirect dfferently) which gives the option to redirect as 301.

[LukeTowers]

@CptMeatball I mean is there ever a reason someone would want forceRedirectUrl to 302 redirect?

[CptMeatball]

Can't think of any. @vannut ?

One other thing is that the redirects happen to the default, except when there's a locale stored in the session. Not sure if that might give issues for SEO or anything 🤔

[mjauvin]

stale

[LukeTowers]

@mjauvin use https://github.com/octoberrain/meta/blob/master/github/saved-replies/abandoned.md and tag abandoned for stale issues please. I'm also looking into setting up StaleBot for OctoberCMS and RainLab.

[LukeTowers]

Closing as it has been over a month since any activity on this occurred and we are trying to figure out what issues are still relevant. If this is still something that you would like to see through to fruition please respond and we can get the ball rolling.