Changing lang in a url should redirect 404 or 301 #910

Closed
riquito opened this Issue Jul 30, 2011 · 5 comments

Projects

None yet

6 participants

@riquito
riquito commented Jul 30, 2011

Say I have a multilanguage page, with urls
/en/hello/world
/it/ciao/mondo

Both urls point to same page, different translations.

At present, if you write
/it/hello/world
the italian page is presented

For SEO purposes, we shouldn't have two urls serving the same exact content.
The proper way to handle it would be to either redirect to the completely translated url with a 301
/it/hello/world => 301 => /it/ciao/mondo
or let it fail with a 404
/it/hello/world => 404

Contributor
FrankBie commented Aug 8, 2011

In order to theme the site properly,
meaning having controll over the site structure and link flow,
/it/hello/world is not a url that should be reachable, so I would 404 it.
As only 2 pages exist
/en/hello/world and
/it/ciao/mondo

just my 2 cents
Frank

Collaborator
ojii commented Jul 2, 2012

I'm +1 on 301, simply because people copy/paste links all the time (and sometimes change the language prefix). Also, non-prefixed URLs should 301 too. Like that one content (in a language) only has one URL attached to it, but it makes it still easy for users to get there.

Contributor
evildmp commented Jul 3, 2012

301 sounds sensible to me.

GMLudo commented Jul 11, 2012

+1 for 301.

Member
digi604 commented Oct 4, 2012

this has been resolved in the multilingual middleware removal branch merge.

@digi604 digi604 closed this Oct 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment