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://moz.com/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
-
Is there any benefit to changing 303 redirects to 301?
A year ago I moved my marketplace website from http to https. I implemented some design changes at the same time, and saw a huge drop in traffic that we have not recovered from. I've been searching for reasons for the organic traffic decline and have noticed that the redirects from http to https URLs are 303 redirects. There's little information available about 303 redirects but most articles say they don't pass link juice. Is it worth changing them to 301 redirects now? Are there risks in making such a change a year later, and is it likely to have any benefits for rankings?
Intermediate & Advanced SEO | | MAdeit0 -
Allowing correct crawlers for GeoIP Redirect
Hi All, I am working on an international site and we have started running into issues with crawlers successfully crawling the site. GeoIPEnable On Redirect one country RewriteEngine on
Intermediate & Advanced SEO | | michaelpw
RewriteCond %{ENV:GEOIP_COUNTRY_CODE} ^US$
RewriteCond %{HTTP:X-Host} !.nexcesscdn.net$ [NC]
RewriteRule ^(.)$ https://us.website.com/ [R,L] The main reason for working on a hard GEOIP redirect would be that we are unable to show certain products in certain regions, the customer should not be given the option which is best practice. Can anyone advise? Thanking in advance.0 -
301 redirect hops from non-https and www
It's best practice to minimize the amount of 301 redirect hops. Ideally only one redirect hop. It's also best practice to 301 redirect (or at least canonical) your non-https and/or your non-www (or www) to the canonical protocol/subdomain. The simplest (and possibly the most common) way to implement canonical protocol/subdomain redirects is through a load balancer or before your app processes the request. Both of which will just blanket 301 to the canonical domain/protocol regardless if the path exists or not In which case, you could have: Two hops. i.e. hop #1 http://example.com/foo to https://example.com/foo, hop #2 https://example.com/foo to https://example.com/bar 301 to a 404. Let's say https://example.com/dog never existed, but somebody for whatever reason linked to it (maybe a typo). If I request https://www.example.com/dog, the load balancer would 301 to a 404 page. Either scenario above should be fairly rare. However, you can't control how people link to you. Should I care about either above scenario? I could have my app attempt to check if the page exists before forwarding, but that code could be complicated.
Intermediate & Advanced SEO | | dsbud0 -
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 -
How do you 301 redirect URLs with a hashbang (#!) format? We just lost a ton of pagerank because we thought javascript redirect was the only way! But other sites have been able to do this – examples and details inside
Hi Moz, Here's more info on our problem, and thanks for reading! We’re trying to Create 301 redirects for 44 pages on site.com. We’re having trouble 301 redirecting these pages, possibly because they are AJAX and have hashbangs in the URLs. These are locations pages. The old locations URLs are in the following format: www.site.com/locations/#!new-york and the new URLs that we want to redirect to are in this format: www.site.com/locations/new-york We have not been able to create these redirects using Yoast WordPress SEO plugin v.1.5.3.2. The CMS is WordPress version 3.9.1 The reason we want to 301 redirect these pages is because we have created new pages to replace them, and we want to pass pagerank from the old pages to the new. A 301 redirect is the ideal way to pass pagerank. Examples of pages that are able to 301 redirect hashbang URLs include http://www.sherrilltree.com/Saddles#!Saddles and https://twitter.com/#!RobOusbey.
Intermediate & Advanced SEO | | DA20130 -
.htaccess 301 Redirect Help! Specific Redirects and Blanket Rule
Hi there, I have the following domains: OLD DOMAIN: domain1.co.uk NEW DOMAIN: domain2.co.uk I need to create a .htaccess file that 301 redirects specific, individual pages on domain1.co.uk to domain2.co.uk I've searched for hours to try and find a solution, but I can't find anything that will do what I need. The pages on domain1.co.uk are all kinds of filenames and extensions, but they will be redirected to a Wordpress website that has a clean folder structure. Some example URL's to be redirected from the old website: http://www.domain1.co.uk/charitypage.php?charity=357 http://www.domain1.co.uk/adopt.php http://www.domain1.co.uk/register/?type=2 These will need to be redirected to the following URL types on the new domain: http://www.domain2.co.uk/charities/ http://www.domain2.co.uk/adopt/ http://www.domain2.co.uk/register/ I would also like a blanket/catch-all redirect from anything else on www.domain1.co.uk to the homepage of www.domain2.co.uk if there isn't a specific individual redirect in place. I'm literally tearing my hair out with this, so any help would be greatly appreciated! Thanks
Intermediate & Advanced SEO | | Townpages0 -
Is it safe to 301 redirect old domain to new domain after a manual unnatural links penalty?
I have recently taken on a client that has been manually penalised for spammy link building by two previous SEOs. Having just read this excellent discussion, http://www.seomoz.org/blog/lifting-a-manual-penalty-given-by-google-personal-experience I am weighing up the odds of whether it's better to cut losses and recommend moving domains. I had thought under these circumstances it was important not to 301 the old domain to the new domain but the author (Lewis Sellers) comments on 3/4/13 that he is aware of forwards having been implemented without transferring the penalty to the new domain. http://www.seomoz.org/blog/lifting-a-manual-penalty-given-by-google-personal-experience#jtc216689 Is it safe to 301? What's the latest thinking?
Intermediate & Advanced SEO | | Ewan.Kennedy0 -
301 - should I redirect entire domain or page for page?
Hi, We recently enabled a 301 on our domain from our old website to our new website. On the advice of fellow mozzer's we copied the old site exactly to the new domain, then did the 301 so that the sites are identical. Question is, should we be doing the 301 as a whole domain redirect, i.e. www.oldsite.com is now > www.newsite.com, or individually setting each page, i.e. www.oldsite.com/page1 is now www.newsite.com/page1 etc for each page in our site? Remembering that both old and new sites (for now) are identical copies. Also we set the 301 about 5 days ago and have verified its working but haven't seen a single change in rank either from the old site or new - is this because Google hasn't likely re-indexed yet? Thanks, Anthony
Intermediate & Advanced SEO | | Grenadi0