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
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
-
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 -
Images Returning 404 Error Codes. 301 Redirects?
We're working with a site that has gone through a lot of changes over the years - ownership, complete site redesigns, different platforms, etc. - and we are finding that there are both a lot of pages and individual images that are returning 404 error codes in the Moz crawls. We're doing 301 redirects for the pages, but what would the best course of action be for the images? The images obviously don't exist on the site anymore and are therefore returning the 404 error codes. Should we do a 301 redirect to another similar image that is on the site now or redirect the images to an actual page? Or is there another solution that I'm not considering (besides doing nothing)? We'll go through the site to make sure that there aren't any pages within the site that are still linking to those images, which is probably where the 404 errors are coming from. Based on feedback below it sounds like once we do that, leaving them alone is a good option.
Intermediate & Advanced SEO | | garrettkite0 -
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 -
Should I redirect my xml sitemap?
Hi Mozzers, We have recently rebranded with a new company name, and of course this necessitated us to relaunch our entire website onto a new domain. I watched the Moz video on how they changed domain, copying what they did pretty much to the letter. (Thank you, Moz for sharing this with the community!) It has gone incredibly smoothly. I told all my bosses that we may see a 40% reduction in traffic / conversions in the short term. In the event (and its still very early days) we have in fact seen a 15% increase in traffic and our new website is converting better than before so an all-round success! I was just wondering if you thought I should redirect my XML sitemap as well? So far I haven't, but despite us doing the change of address thing in webmaster tools, I can see Google processed the old sitemap xml after we did the change of address etc. What do you think? I know we've been very lucky with the outcome of this rebrand but I don't want to rest on my laurels or get tripped up later down the line. Thanks everyone! Amelia
Intermediate & Advanced SEO | | CommT0 -
When should you redirect a domain completely?
We moved a website over to a new domain name. We used 301 redirects to redirect all the pages individually (around 150 redirects). So my question is, when should we just kill the old site completely and just redirect (forward/point) the old domain over to the new one?
Intermediate & Advanced SEO | | co.mc0 -
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 -
301 Redirect - What happens to backlinks
Hello... One of my sites is losing rankings in G. I received the webmaster notification of unnatural links... My question is, should i do a 301 redirect of every page on my site to a new domain? If so, do the backlinks (which i believe are causing my rankings to drop) carry over? How about the good backlinks? Also, what would happen to the rankings i currently have on page 1? Thanks
Intermediate & Advanced SEO | | Prime850 -
301 Redirects After Company Acquisition
We recently acquired a company, and now we are going to redirect all of the pages on their site to their respective pages on our site. Do we need to keep the original pages on their site active? For how long? Ideally, we would like to redirect everything and remove the old site entirely so we don't have to pay to keep hosting it. Is this possible? Thanks!
Intermediate & Advanced SEO | | pbhatt1