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.
301 or 302 Redirects with locale URLs?
-
Hi Mozers,
I have a bit of a tricky question I need some help answering. My agency are building a brand new website for a client of ours which means changing the domain name (yay...). So! I have my 301's all ready to go for the UK locale, however, the issue I have is that the site will also eventually have French, German and Spanish locales - but these won't be ready to go until later this year. We will be launching in just English for September. The current site already has the French and German locales on it as well.
Just to make sure I'm being clear, the site will be www.example.com for launch, but by lets say November, we will also have a www.example.com/fr/ and www.example.com/de/ site launched too.
So what do I do with the locale URLs? As I said above, the exisitng site already has the French and German locales on it, so I don't particularly want to redirect the /fr/ and /de/ URLs to the English homepage, as I will want to redirect them to the new URLs in November, and redirecting more than once is bad for SEO right?
Any ideas? Would 302s maybe be the best suggestion?
Thanks!
Virginia
-
Thanks Greg. Yeah, I didn't really want to go down the 302 route, it makes everything so much more time sensitive!
-
Thanks Rob!
I'm trying to encourage my client as much as possible to start work on the translations of the sites ASAP so that we don't end up going down the Google Translate route. I've advised against this already.
Your advise has been really helpful!
Thanks
-
Hi Virginia,
In all honesty, it's probably not going to matter very much which kind of redirect you are using. If I understand you correctly, your current redirect chain will look like:
www.example.com --> www.example2.com
www.example.com/fr --> www.example2.com
www.example.com/de --> www.example2.comThe reason redirects won't matter is that in November your second French, Dutch, etc. sites are going live. The redirects will have to be changed in November to look more like this:
www.example.com --> www.example2.com
www.example.com/fr --> www.example2.com/fr
www.example.com/de --> www.example2.com/deGiven that there is a maximum of 6-8 weeks when these redirects will be active, Google will barely have time to index them before you are changing your redirect chain all over again. In my books, that makes these redirects somewhat redundant - either way you are going to have some SEO changes occurring during that time which will probably be in a downward direction. That being said, you will want to finish up with 301 redirects since that will be the permanent fix.
However, once the new redirects are placed and indexed, you should see things return to normal and even improve if the new sites are featuring good UX. Keep in mind that any redirect is going to hurt your link profile a little bit, so you can expect to lose some rankings once your redirects are indexed.
Bottom line:
- Focus on ensuring the new sites are well put-together with good content
- Make sure proper translations are taken care of (this is a HUGE problem with multi-lingual sites)
- Try to avoid Google Translate plugin for translation services (doesn't sound like this is what you're doing)
- More importance should be placed on the UX of the site and the link profile impacts of 301 redirects
- Make sure 301 redirects are what you finish up with after the new sites go live in November
Feel free to reach out if I can be of more assistance.
Cheers,
Rob
-
Also, I understand your confusion in 301 vs 302. I mean essentially, your redirect is temporary. But 302 redirects are meant more so for short time periods, probably with a month being the max amount of time you would want to do this. You'll want to use a 301 to maintain linking power. There's no harm in doing so and then replacing it later.
-
You would remove the old 301 redirect from www.example.com/fr/ to www.example.com and add a new one from www.example.com/fr/ to www.example2.com/fr/ , then force a recrawl on your site.
-
But what will happen when I have to 301 again? Currently, I will have to redirect from www.example.com/fr/ to my new English only site which is www.example.com. But then in 3 months time, I will have a www.example2.com/fr/. So I want my old www.example.com/fr/ to redirect to my new www.example2.com/fr/ website. So how would that work?
-
Personally I think a 301 redirect would be the best.
-
I reckon you must use 301 as it seems like you're moving your sites permanently so there is no point to have 302 at all.
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
-
How to Get google to get to index New URL and not the OLD url
Hi Team, We are undertaking a Domain migration activity to migrate our content frrom one domain to another. 1. the Redirection of pages is handeled at Reverse proxy level. 2. We do have 301 redirects put in place. However we still see that google is indexing pages with our Old domain apart from the pages from new domain. Is there a way for us to stop google from indexing our pages from Old domain. The recommendations to have Noindex on Page mete title and disallow does not work since our redirection is setup at RP and google crawlers always discover the new pages after redirection.
Local Website Optimization | | bhaskaran0 -
Local SEO Over Optimization
We are targeting a bunch of services for our local business that works in and around their location. I'm concerned about over optimization and need some guidance on whether these points should be resolved. The company is based in a city and works mostly in the city but also in the surrounding areas. Currently, the site has 6 services pages (accessible via main nav) targeting the same location i.e. “Made Up Service London”, “Imaginary Service London” (with URLs and H1 tags etc. in place containing this location). However this is soon going to become 9 services pages, I am concerned that the repetition of this one location is starting to look spammy, especially as its where the company is based. Initially, I also wanted pages targeting the same services in other nearby areas. For example “Made Up Service Surrey”, “Imaginary Service Essex”. This has not happened as the info available has been too sporadic. I was going to add links to relevant case studies into these pages to beef up the content and add interest. To that end, we came up with case studies, but after a while, I noticed that these are also largely focused on the primary location. So out of 32 case studies, we have 19 focused on the primary location again with URL’s and H1 tags etc containing the location keyword. So in total, we have 25 pages optimized for the location (soon to be 28 and more if further case studies are added). My initial feeling was that the inclusion of pages targeting services in other locations would legitimize what we have done with the main pages. But obviously we have not got these pages in place and I question whether we ever will. What is my best course of action moving forward?
Local Website Optimization | | GrouchyKids1 -
Is CNAME / URL flattening a bad practice?
I recently have moved a number of websites top a new server and have made the use of CNAME / URL flattening (I believe these are the same?). A network admin had said this is an unrecommended practice. From what I have read it seems flattening can be beneficial for site speed and SEO even if very little.
Local Website Optimization | | Dissident_SLC0 -
Do I need to change my country og:locale to en_AE
Hi MOZ, I have a site that is aimed at the English speaking market of the United Arab Emirates. The language tag is currently set to lang="en-GB" and the og:locale also set to en_GB. The domain is a .com and aimed at the whole world. Should I be trying to target en-AE and en_AE for these tags instead of GB?
Local Website Optimization | | SeoSheikh0 -
Local SEO - Adding the location to the URL
Hi there, My client has a product URL: www.company.com/product. They are only serving one state in the US. The existing URL is ranking in a position between 8-15 at the moment for local searches. Would it be interesting to add the location to the URL in order to get a higher position or is it dangerous as we have our rankings at the moment. Is it really giving you an advantage that is worth the risk? Thank you for your opinions!
Local Website Optimization | | WeAreDigital_BE
Sander0 -
Should I use pipe in title tags for local seo?
Hi, I've created a bunch of landing pages for local areas, reading, windsor, slough etc for the title tag I have for Windsor Emergency Electrician Windsor - BrandName should I be using a pipe in the tag to further help search engines learn/identify the location? Emergency Electrician | Windsor - BrandName Thank you Kev
Local Website Optimization | | otex1 -
Subdomain versus Subfolder for Local SEO
Hello Moz World, I'm wanting to know the best practices for utilizing a subdomain versus a subfolder for multi location businesses, i.e. miami.example.com vs. example.com/miami; I would think that that utilizing the subdomain would make more sense for a national organization with many differing locations, while a subfolder would make more sense for a smaller more nearby locations. I wanted to know if anyone has any a/b examples or when it should go one way or another? Thank you, Kristin Miller
Local Website Optimization | | Red_Spot_Interactive0 -
International Site Geolocation Redirection (best way to redirect and allow Google bots to index sites)
I have a client that has an international website. The website currently has IP detection and redirects you to the subdomain for your country. They have currently only launched the Australian website and are not yet open to the rest of the world: https://au.domain.com/ Google is not indexing the Australian website or pages, instead I believe that the bots are being blocked by the IP redirection every time they try to visit one of the Australian pages. Therefore only the US 'coming soon' page is being properly indexed. So, I would like to know the best way to place a geolocation redirection without creating a splash page to select location? User friendliness is most important (so we don't want cookies etc). I have seen this great Whiteboard Friday video on Where to Host and How to Target, which makes sense, but what it doesn't tell me is exactly the best method for redirection except at about 10:20 where it tells me what I'm doing is incorrect. I have also read a number of other posts on IP redirection, but none tell me the best method, and some are a little different examples... I need for US visitors to see the US coming soon page and for Google to index the Australian website. I have seen a lot about JS redirects, IP redirects and .htaccess redirects, but unfortunately my technical knowledge of how these affect Google's bots doesn't really help. Appreciate your answers. Cheers, Lincoln
Local Website Optimization | | LincolnSmith0