Should I use 301 to redirect in place?

Question

We would like to redirect to a localized version of our login web page if IP is detected from a specific country. We use ASP.Net, GeoLite Country Db (this is a very small 1 Mb downloadable database at the time of writing this question).

Thus, most users will receive English content, but if they come from a local place, they will have local content, which will be used by default. Of course, they can change their preferred language at any time.

Question: if www.example.comby default it displays default.aspxwhether we should (if we discover that the IP is "local"):

• Use "301 Moved Permanently"and redirect it, say www.example.com/local.aspx, or

• Just display the relevant content inside default.aspx?

We would like to know if there are any side effects with SEO or similar problems with any of the approaches?

Answer 1

I would just bring the localized content local.aspx and send the corresponding Content-Location , referencing local.aspx along with it.

Or, if you want to redirect, use status code 307 to indicate a temporary redirect.

Answer 2

This may not be the best solution.

wikipedia , 300 :

http://en.wikipedia.org/wiki/URL_redirection

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.1

HTTP :

* 300 multiple choices (e.g. offer different languages)
* 301 moved permanently
* 302 found (originally temporary redirect, but now commonly used to specify redirection for unspecified reason)
* 303 see other (e.g. for results of cgi-scripts)
* 307 temporary redirect