Multilang site: Auto redirect 301 or 302?
-
We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header.
https://domain.com
30x > https://domain.com/en
30x > https://domain.com/ru
30x > https://domain.com/deThe site architecture is set up with proper inline HREFLANG.
We have read different opinions about this, Ahrefs says 302 is the correct one:
https://ahrefs.com/blog/301-vs-302-redirects/
302 redirect:
"You want to redirect users to the right version of the site for them (based on location/language)."You could argue that the root redirect is never permanent as it varies based on user language settings (302)
On the other hand, the lang specific redirects are permanent per language:IF Accept-Language header = en
https://domain.com > 301 > https://domain.com/en
IF Accept-Language header = ru
https://domain.com > 301 > https://domain.com/ruSo each of these is 'permanent'.
So which is the correct?
-
Hi Guys i am newer to SEO. my web with the 301 302 issue. anyone able help to fix it? will be high appreciated.
Internal URL
Yes
Full URL
https://myoffroadled.com/led-rocker-switch
HTTP status code
301 Moved permanently
First found at
Seed URL
Content type
text/html; charset=utf-8
Depth
0
Redirect URL
https://www.myoffroadled.com/led-rocker-switch/
Not crawled
Is redirect loop
No
Page rating
100 -
@fj66doneoiddpj In some cases users may have a reason for using the site in something other than their browser language.
For example, perhaps a shared device, or simply wishing to check a different localisation.
If your hreflang is working correctly, they should never see the "wrong" version anyhow.
But, there are pros and cons of course.
-
Thank you for the reply, 302 is also what we decided after many hours of reading.
The main reason for auto redirect is that we feel it's a better user experience as user will arrive the content target to his/her browser language. -
I would use a 302 here, just as an added insurance in case you ever accidentally serve Google the redirect.
However, I'm not a huge fan of auto redirects in general - they tend to cause issues for crawlers and users alike. Can you explain a bit more when/why the user gets redirected? Perhaps instead you could serve a country selection insterstitial if a user seems to be on the "wrong" variant?
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
-
href lang questions - please help
Hi I have a few questions about href lang implementation and I was hoping for some guidance / opinions. An international website is using mostly a folder structure, but for some locations it might have standalone sub-domains. Some folders are there to target locations and languages, with others just targeting languages. See the list below: domain.com/es-mx [Language: Spanish - Location: Mexico]
International SEO | | MarkCanning
domain.com/pt-br [Language: Portuguese - Location: Brazil]
domain.com/ja-jp [Language: Japanese - Location: Japan]
domain.com/en-jp [Language: English - Location: Japan]
domain.com/fr-ca [Language: French - Location: Canada]
domain.com/en-ca [Language: English - Location: Canada]
domain.com/en-ie [Language: English - Location: Ireland]
domain.com/ar [Language: Arabic]
domain.com/ph [Language: Tagalog]
domain.com/it [Language: Italian]
domain.com/tr [Language: Turkish]
domain.com/kr [Language: Korean]
domain.com/fr [Language: French]
domain.com/ru [Language: Russian]
domain.com/vn [Language: Vietnamese] domain.in/en [Language: English - Location Indian]
domain.in/hi [Language: Hindi - Location Indian] My questions are: Is href lang sitemap equally as good as the href lang meta tag in terms of effectiveness. I know that the sitemap is easier to maintain and upkeep but i don't know which one is better as google recommends both. How do you mix your listings when some are targeting language and country and others are just targeting language speakers (not tied to any specific country). So take for example in the list above: there would be a general site for french speakers and then one for french speakers in Canada. Thanks for your advise in advance.0 -
Managing removed product pages
Hello everyone, I am turning to the community for your advice regarding the optimal management of product pages that are removed after an article is sold. Considering that we operate with unique articles on our site and consequently do not have large quantities in stock, the product pages are intended to be removed once the article is sold. My question is: from an SEO point of view, what would be the most effective strategy to manage these pages? Is it preferable to apply a permanent redirect (301) to the product category, or would it be better to use the status code 410 to indicate that the page has been permanently removed?
Intermediate & Advanced SEO | | filippodanesi
I would appreciate any suggestions or experience you could share on this matter. Thank you in advance for your help.0 -
Will URLS With Existing 301 Redirects Be as Powerful As New URLS In Serps?
Most products on our site have redirects to them from years of switching platform and merely trying to get a great and optimised URL for SEO purposes. My question is this: If a product URL has alot of redirects (301's), would it be more beneficial to me to create a duplicated version of the product and start fresh with a new URL? I am not on here trying to gain backlinks but my site is tn nursery dot net (proof:)
Intermediate & Advanced SEO | | tammysons
I need some quality help figuring out what to do.
Tammy0 -
Question regarding international SEO
Hi there, I have a question regarding international SEO and the APAC region in particular. We currently have a website extension .com and offer our content in English. However, we notice that our website hardly ranks in Google in the APAC region, while one of the main languages in that region is also English. I figure one way would be to set up .com/sg/ (or .com/au/ or .com/nz/), but then the content would still be in English. So wouldn't that be counted as duplicate content? Does anyone have experience in improving website rankings for various English-speaking countries, without creating duplicate content? Thanks in advance for your help!
International SEO | | Billywig0 -
Put a 301 from /main to home page, now I'm panicking
Hi, Our website is 10 years old, but I only noticed last night we had a https://curveball-media.co.uk/main page which has some badly formatted copy on. I redirected (301) to the home page https://curveball-media.co.uk/ Then I had a slight panic that maybe this was the wrong thing to do and it should be like it was with the home page and the /main page. Should I have left it or did I do the right thing?
Intermediate & Advanced SEO | | curveballmedia0 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
What is the best SEO site structure for multi country targeting?
Hi There, We are an online retailer with four (and soon to be five) distinct geographic target markets (we have physical operations in both the UK and New Zealand). We currently target these markets like this: United Kingdom (www.natureshop.co.uk) New Zealand (www.natureshop.co.nz) Australia (www.natureshop.com/au) - using a google web master tools geo targeted folder United States (www.natureshop.com) - using google web master tools geo targeted domain Germany (www.natureshop.de) - in german and yet to be launched as full site We have various issues we want to address. The key one is this: our www.natureshop.co.uk website was adversely affected by the panda update on April 12. We had some external seo firms work on this site for us and unfortunately the links they gained for us were very low quality, from sometimes spammy sites and also "keyword" packed with very littlle anchor text variation. Our other websites (the .co.nz and .com) moved up after the updates so I can only assume our external seo consultants were responsible for this. I have since managed to get them to remove around 70% of these links and we have bought all seo efforts back in house again. I have also worked to improve the quality of our content on this site and I have 404'ed the six worst affected pages (the ones that had far too many single phrase anchor text links coming into them). We have however not budged much in our rankings (we have made some small gains but not a lot). Our other weakness's are not the fastest page load times and some "thin" content. We are on the cusp (around 4 weeks away) of deploying a brand new platform using asp.net MVP with N2 and this looks like it will address our page load speed issues. We also have been working hard on our content building and I believe we will address that as well with this release. Sorry for the long build up, however I felt some background was needed to get to my questions. My questions are: Do you think we are best to proceed with trying to get our www.natureshop.co.uk website out of the panda trap or should we consider deploying a new version of the site on www.natureshop.com/uk/ (geo targeted to the UK)? If we are to do this should we do the same for New Zealand and Germany and redirect the existing domains to the new geo targeted folders? If we do this should we redirect the natureshop.co.uk pages to the new www.natureshop.com/uk/ pages or will this simply pass on the panda "penalty". Will this model build stronger authority on the .com domain that benefit all of the geo targeted sub folders or does it not work this way? Finally can we deploy the same pages and content on the different geo targeted sub folders (with some subtle regional variations of spelling and language) or will this result in a duplicate content penalty? Thank you very much in advance to all of you and I apologise for the length and complexity of the question. Kind Regards
International SEO | | ConradC
Conrad Cranfield
Founder: Nature Shop Ltd0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0