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.
Multi Regional Website Best Practices
-
Hi there,
I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right.
I read this article which was a great insight into the hreflang tags. https://moz.com/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner:
When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect.
I have a few questions:
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location.2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag.
In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand)Any help would be appreciated.
Thanks
Nathan
-
Google explicitly advice to use 302 in case of redirection because of IP/User Agent detection, which is what it always says in others similar cases (i.e.: redirecting from desktop to mobile version of the site).
-
Hi Patrick,
If I created a landing page on the root domain, would that have positive or negative implications for SEO. I'm also thinking through usability whether it's more useable to redirect a user automatically with the option to change their region after they have landed on their 'local' site.
Do you know how my search results would look adding the landing page into the mix? I mean in terms of URL and content, how will it display in the search engines?
At the moment, sometimes I see the root domain in the search results and other times I see the country specific pages. An example of this is if you go to https://www.google.com.au/?gws_rd=ssl#q=destiny+rescue+where+we+work, you will see a mixture of results. There are some root domain representations, some /aus/ and even some /us/ and /nz/ (of which the last 2 technically shouldn't be present).
Thanks
-
Hi again
1. There is nothing you are going to lose by changing the 302 redirect to a 301. If anything, I would change the www.domain.com version of your site (leaving that country targeted to the world, no specific region) to give the user an option of what region they are from and what site they would like to visit based on their location. I would then follow the directions in my first paragraph.
2. See my suggestion in one. You shouldn't redirect your www.domain.com to a regional variant. Again, if anything, make the homepage an option page based on the users location so that they can choose which experience they would like to have.
Does this all make sense? Let me know!
-
Hi Patrick,
Thanks for your response.
I read the Moz page on redirections and it's interesting MOZ states that 0% link juice is passed with a 302. With that in mind I have the following additional questions:
1. At the moment I do a 302 from the root of domain to the geo graphical site. (The root domain page is never rendered, only redirected). From what I understand google bots only ever spider a site from the US. If I change the redirect to a 301 the link juice from the root page would then be transferred mostly to /us/ then would it? What sort of ranking power would /aus/ and /nz/ lose as a result of changing the redirect from a 302 to a 301.
2. Would that mean that the http://[website]/ root page would disappear from the search engines and only /us/, /aus/, & /nz/ would be displayed? At the moment the root page link (http://[website]/) is being displayed on most searches when I google.
Thanks.
-
Hi there
Yes - hreflang and language tags are a great place to start. I would also create a Google and Bing Webmaster Tools for each regional variation and country target them accordingly - here's the Bing resource to do that.
You can also use citation builders like Whitespark to build listings for the regional URL variations and their contact information.
When it comes to your 302 issues, I would make sure that your redirects are implemented properly - there are resources there on how to do so.
I would also suggest trying to mold your on-site SEO and content to capture traffic in regional areas for a better user experience.
Here are a couple of more resources for you:
International SEO (Moz)
The International SEO Checklist (Moz)Hope this all helps! Good luck!
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
-
Best practice for Spanish version of English website?
I'm doing an audit for a site that has all of its English pages under the same roof with Spanish pages in Wordpress. It is intended for Chicago, not Mexico. I suspect this is not a good thing, but I only have instinct to rely on here. What is the best practice for having the same website in two languages? http://www.enhancedform.com/ and http://www.enhancedform.com/spanish/
International SEO | | realpatients0 -
Two versions of a website with different languages - Best way to do it?
I'm working on a website for a Swedish artist and her page is in Swedish, everything is in Swedish on the site, even though it's not a lot of text on the site. We would like to have the site in English too, or another version of the site in English on a separate domain, what's the best way to proceed from here? The domain name is a .se (swedish domain), would it be better to create a another domain and host the english version of the site on a .com domain? Or will we bump into problems with duplicate content if we create a replica of the swedish site in english. We're using wordpress and I know that there's translation plugins out there, is that a good option? I'm a bit clueless on how to proceed and would love some help or guidance here.
International SEO | | Fisken0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
Multilingual Ecommerce Product Pages Best Practices
Hi Mozzers, We have a marketplace with 20k+ products, most of which are written in English. At the same time we support several different languages. This changes the chrome of the site (nav, footer, help text, buttons, everything we control) but leaves all the products in their original language. This resulted in all kinds of duplicate content (pages, titles, descriptions) being detected by SEOMoz and GWT. After doing some research we implemented the on page rel="alternate" hreflang="x", seeing as our situation almost perfectly matched the first use case listed by Google on this page http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077. This ended up not helping at all. Google still reports duplicate titles and descriptions for thousands of products, months after setting this up. We are thinking about changing to the sitemap implementation rel="alternate" hreflang="X", but are not sure if this will work either. Other options we have considered include noindex or blocks with robots.txt when the product language is not the same as the site language. That way the feature is still open to users while removing the duplicate pages for Google. So I'm asking for input on best practice for getting Google to correctly recognize one product, with 6 different language views of that same product. Can anyone help? Examples: (Site in English, Product in English) http://website.com/products/product-72 (Site in Spanish, Product in English) http://website.com/es/products/product-72 (Site in German, Product in English) http://website.com/de/products/product-72 etc...
International SEO | | sedwards0 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0 -
French Canadian Website and French Language URLs
Hello, One of my clients has a question on a new Quebec, Canada version of their website. The website content and copy is in the French Canadian language, but the IT Director has asked if, for the purpose of SEO, should the URLs be in French as well? So, this questions has two parts... For SEO, should the URL's be in French or left in English, to avoid crawl errors? For visitor UX, is there any reason to have them in French versus English?
International SEO | | Aviatech0 -
Website Translation
Hi All, I know its not an SEO question, but....................... Can anyone suggest a few good website translation "widgets" I would like to give those who are not fluent in English and option to choose another language in which to view the page text. Thank You!!!
International SEO | | APICDA0