Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Geoip redirection, 301 or 302?
-
Hello all
Let me first try to explain what our company does and what it is trying to achieve.
Our company has an online store, sells products for 3 different countries, and two languages for each country.
Currently we have one site, which is open to all countries, what we are trying to achieve is make 3 different stores for these 3 different countries, so we can have a better control over the prices in each country. We are going to use Geoip to redirect the user to the local store in his country.
The suggested new structure is to add sub-folders as following:
www.example.com/ca-en
www.example.com/ca-fr
www.example.com/us-en
...If a visitor is located outside these 3 countries, then she'll be redirected to the root directory www.example.com/en
We can't offer to expand our SEO team to optimize new pages for the local market, it's not the priority for now, the main objective now is to be able to control the prices for different market. so to eliminate the duplicate issue, we'll use canonical tags.
Now knowing our objective from the new URL structure, I have two questions:
1- which redirect should we use? 301, 302?
If we choose 301, then which version of the site will get the link juice? (i.e, /ca-en or /us-en?)
if we choose 302, then will the link juice remain in the original links? is it healthy to use 302 for long term redirections?2- Knowing that Google bots comes from US-IP, does that mean that the other versions of the site won't be crawled (i.e, www.example.com/ca-fr), this is especially important for us as we are using AdWords, and unindexed pages will effect our quality score badly.
I'd like to know if you have other account structure in your mind that would be better than this proposed structure.
Your help is highly highly appreciated.
Thanks in advance. -
For geo-redirects, I do not recommend you use 301 redirects. Browsers can cache these, so if you tell a browser in Canada that example.com should redirect to www.example.com/ca-fr, and later the user changes their language to English, and then tries to go www.example.com, the browser could use that redirect again to go back to the French version without hitting your server. 301 tells the browser that www.example.com ALWAYS (permanently) goes to www.example.com/ca-fr. Page rank isn't really a consideration with these, since Googlebot always comes from the US, so it should never hit these redirects. If example.com always goes to one of the versions via a redirect (i.e. you don't serve content under that root URL), then you do have a bit of problem with redirects. You don't want to 302 Googlebot to another page for your home page, but at the same time, you want to avoid weird redirect behaviors for your customers.
Google can visit the international versions directly without redirects, right? They should have no problem indexing those pages then.
I agree with István, get some local links to your different local versions, register them each with Google Webmaster Tools (and Bing), put up sitemaps for each, and implement the hreflang tags in your sitemaps (or pages). That way Google can easily index each version, and knows exactly what each version is for.
-
Other opinions are highly appreciated, Thanks for everyone in advance.
-
Thanks István Keszeg for your clear and detailed answer.
I still have some questions:
1- redirection will not be for 1 version, but for several pages (ca-en, us-en, uk-en) then would the link juice be divided on these 3 version? put in other words, will that effect our current SEO ranking for the words we are currently ranked for?
2- (point no . 2 in my first post).
Thanks in advance.
-
Hi Marcel,
Let us not forget that in order to be able to rank with your website, you will have to give the possibilities for Search Engines to make 3 steps: 1. Crawl 2. Index 3. Rank
One of the best solutions that I have seen for your case is what Specialized Bikes uses (www.specialized.com

So As I have seen they have an IP sniffing on the main address only: www.specialized.com which will then redirect you to your location's store (for me it is http://www.specialized.com/ro/en/home/ for a person from the US it should be http://www.specialized.com/us/en/home/ and so on for each country which they have specified).
This is good, because then in Google Webmasters Tools they can create separate profiles for each folder: /ro/ /us/ /fr/ etc.
This means that they can still create a sitemap.xml for each of the "stores" and they can submit the sitemaps from Google Webmaster's Tools and avoid crawling issues. (And if you check via proxy different local Google results, you will see that they still rank quite good).
The problem comes with the same language content on different countries where you could:
- insert Hreflang
- get local some nice LOCAL links for both
(at least this is what I would try to do)
Now to respond your question, I quote:
1- which redirect should we use? 301, 302?
A: This wont be a temporary redirect, so be sure to use 301! 302 redirect will retain the "link juice" on the old version. For reference check the following article of Dr. Pete: http://a-moz.groupbuyseo.org/learn/seo/http-status-codes
If we choose 301, then which version of the site will get the link juice? (i.e, /ca-en or /us-en?)
A: Depends who do you redirect to.
P.S. As you mentioned you will have duplicate content issue because of us-en and ca-en, which Ideally it shouldn't be a problem:
“Duplicate content and international sites
_Websites that provide content for different regions and in different languages sometimes create content that is the same or similar but available on different URLs. This is generally not a problem as long as the content is for different users in different countries.” _Source: https://support.google.com/webmasters/answer/182192
if we choose 302, then will the link juice remain in the original links? is it healthy to use 302 for long term redirections?
I wouldn't advise you to do so. If it is a permanent redirection, let it be a 301.
So before making the huge step, I would advise you to go through some steps:
- create a full list of incoming links
- Sort your list of links for relevance, quality and geo-location
- Make the change in the URL system
- Start contacting your most important linking partners and kindly ask them to change the old links into the new versions (from example.com to example.com/us/en/ or if it is a French link from Canada then from current version to the example.com/ca/fr/ version and so on)
I know it is really a huge work, but it will grow its fruits.
Good luck!
Istvan
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
302 > 302 > 301 Redirect Chain Issue & Advice
Hi everyone, I recently relaunched our website and everything went well. However, while checking site health, I found a new redirect chain issue (302 > 302 > 301 > 200) when the user requests the HTTP and non-www version of our URL. Here's what's happening: • 302 #1 -- http://domain.com/example/ 302 redirects to http://domain.com/PnVKV/example/ (the 5 characters in the appended "subfolder" are dynamic and change each time)
Intermediate & Advanced SEO | | Andrew_In_Search_of_Answers
• 302 #2 -- http://domain.com/PnVKV/example/ 302 redirects BACK to http://domain.com/example/
• 301 #1 -- http://domain.com/example/ 301 redirects to https://www.domain.com/example/ (as it should have done originally)
• 200 -- https://www.domain.com/example/ resolves properly We're hosted on AWS, and one of my cloud architects investigated and reported GoDaddy was causing the two 302s. That's backed up online by posts like https://stackoverflow.com/questions/46307518/random-5-alpha-character-path-appended-to-requests and https://www.godaddy.com/community/Managing-Domains/My-domain-name-not-resolving-correctly-6-random-characters-are/td-p/60782. I reached out to GoDaddy today, expecting them to say it wasn't a problem on their end, but they actually confirmed this was a known bug (as of September 2017) but there is no timeline for a fix. I asked the first rep I spoke with on the phone to send a summary, and here's what he provided in his own words: From the information gathered on my end and I was able to get from our advanced tech support team, the redirect issue is in a bug report and many examples have been logged with the help of customers, but no log will be made in this case due to the destination URL being met. Most issues being logged are site not resolving properly or resolving errors. I realize the redirect can cause SEO issues with the additional redirects occurring. Also no ETA has been logged for the issue being reported. I do feel for you since I now understand more the SEO issues it can cause. I myself will keep an eye out for the bug report and see if any progress is being made any info outside of this I will email you directly. Thanks. Issue being Experienced: Domains that are set to Go Daddy forwarding IPs may sometimes resolve to a url that has extra characters appended to the end of them. Example: domain1.com forwards to http://www.domain2.com/TLYEZ. However it should just forward to http://www.domain2.com. I think this answers what some Moz users may have been experiencing sporadically, especially this previous thread: https://a-moz.groupbuyseo.org/community/q/forwarded-vanity-domains-suddenly-resolving-to-404-with-appended-url-s-ending-in-random-5-characters. My question: Given everything stated above and what we know about the impact of redirect chains on SEO, how severe should I rate this? I told my Director that I would recommend we move away from GoDaddy (something I don't want to do, but feel we _**have **_to do), but she viewed it as just another technical SEO issue and one that didn't necessarily need to be prioritized over others related to the relaunch. How would you respond in my shoes? On a scale of 1 to 10 (10 being the biggest), how big of a technical SEO is this? Would you make it a priority? At the very least, I thought the Moz community would benefit from the GoDaddy confirmation of this issue and knowing about the lack of an ETA on a fix. Thanks!0 -
Hacked website - Dealing with 301 redirects and a large .htaccess file
One of my client's websites was recently hacked and I've been dealing with the after effects of it. The website is now clean of malware and I already appealed to Google about the malware issue. The current issue I have is dealing with the 20, 000+ crawl errors which are garbage links that were created from the hacking. How does one go about dealing with all the 301 redirects I need to create for all the 404 crawl errors? I'm already noticing an increased load time on the website due to having a rather large .htaccess file with a couple thousand 301 redirects done already which I fear will result in my client's website performance and SEO performance taking a hit as well.
Intermediate & Advanced SEO | | FPK0 -
Switching from HTTP to HTTPS: 301 redirect or keep both & rel canonical?
Hey Mozzers, I'll be moving several sites from HTTP to HTTPS in the coming weeks (same brand, multiple ccTLDs). We'll start on a low traffic site and test it for 2-4 weeks to see the impact before rolling out across all 8 sites. Ideally, I'd like to simply 301 redirect the HTTP version page to the HTTPS version of the page (to get that potential SEO rankings boost). However, I'm concerned about the potential drop in rankings, links and traffic. I'm thinking of alternative ways and so instead of the 301 redirect approach, I would keep both sites live and accessible, and then add rel canonical on the HTTPS pages to point towards HTTP so that Google keeps the current pages/ links/ indexed as they are today (in this case, HTTPS is more UX than for SEO). Has anyone tried the rel canonical approach, and if so, what were the results? Do you recommend it? Also, for those who have implemented HTTPS, how long did it take for Google to index those pages over the older HTTP pages?
Intermediate & Advanced SEO | | Steven_Macdonald0 -
SEO impact difference between a URL Rewrite and 301 redirect
Hi guys and girls! Just putting a new site live, we changed the URL from one thing to another and I created a 301 file redirecting the urls like for like. The developer installing it has created a different file with columns like: RewriteRule ^page/ http://www.site/page [R=301,L] RewriteRule ^/page/ http://www.site/page [R=301,L] What's the difference? The page redirects but is there a difference between the 301 redirect and this URL rewrite in terms of SEO and link value?
Intermediate & Advanced SEO | | shloy23-2945840 -
Redirect at Registrar or Server
Hi folks, I have run into a situation were a new client has 3 TLDs (e.g. mycompany.com, mycompany.org and mycompany.biz), all with the same content. They are on a Windows IIS environment, which I am not familiar with. Until now, all of my clients have been Linux/Apache environment, so I always dealt with these issues utilizing htaccess. Currently all resolve to the same IP, but the URL remains the same in the browser address field (e.g. if you type-in mycompany.org - it remains as such). We want the .org and .biz version to 301 Redirect to the .com TLD. I am wondering what the best practice might be in this situation? Could we simply redirect at the registrar level or would implementation at the server level be best? If so, I would really appreciate an example from someone with experience implementing redirects on IIS. Thank you!
Intermediate & Advanced SEO | | SCW0 -
Remove URLs that 301 Redirect from Google's Index
I'm working with a client who has 301 redirected thousands of URLs from their primary subdomain to a new subdomain (these are unimportant pages with regards to link equity). These URLs are still appearing in Google's results under the primary domain, rather than the new subdomain. This is problematic because it's creating an artificial index bloat issue. These URLs make up over 90% of the URLs indexed. My experience has been that URLs that have been 301 redirected are removed from the index over time and replaced by the new destination URL. But it has been several months, close to a year even, and they're still in the index. Any recommendations on how to speed up the process of removing the 301 redirected URLs from Google's index? Will Google, or any search engine for that matter, process a noindex meta tag if the URL's been redirected?
Intermediate & Advanced SEO | | trung.ngo0 -
303 redirect
Hi, 303 redirect is a good thing or not ? I have a homepage in 2 languages FR and EN > mywebsite.com/fr/ and mywebsite.com/en/. A 303 redirect is on mywebsite.com to mywebsite.com/fr/. Thanks D.
Intermediate & Advanced SEO | | android_lyon0 -
How To 301 Redirect .html pages
I need to redirect a page/URL that is purely .html to a new location. I don't know how to do this. All the redirects I can find are for server side code pages .php/.aspx etc. From my understanding I can't put a server side redirect in a .html file. I am hosting on a microsoft server, however the new page I am redirecting to is .php. I am running some WordPress (.php) files on the server. I need to make it redirect before the old page loads so visitors don't start reading something that is about to get redirected Can someone please help me?
Intermediate & Advanced SEO | | MyNet0