International Site - Language Targetting
-
Hi Mozzers,
I am currently conducting a technical site audit on a large website. Their main content and audience is in the US, but they have started to add translated versions of the content in different languages (about 30 different languages). Also, they are not using cookies or scripts to auto-populate the language on the page, and the pages seem to be getting indexed just fine.
Currently, they have their language distinguished by sub-folder (i.e. example.org/blog/by-language/spanish/), which I plan to 301 redirect to example.org/blog/es/ for each language. However, they are not implementing any sitemaps or hreflang header tags.
I have not dealt with this in the past as all of my work has been done on smaller US sites, so I wanted to verify the steps I plan to take to ensure this is a solid approach.
- 301 redirect example.org/language/spanish/blog/ to example.org/es/blog/
- Recommend adding hreflang markup into the header for each language. (They have a lot of pages, so they may not implement this if it is too much work.)
- Highly recommend adding XML sitemaps for each content version of the site using the media flow HREFLANG Siitemap Tool.
- Setting up multiple Webmaster Tools accounts and geotargetting them by language. I would also add the XML sitemap for each language.
Is this a solid approach, given the information above? I want to make sure I am fundamentally sound on this before suggesting so many large changes. Thank you in advance for any thoughts / wisdom you can instill!
---------------------additional information---------------------
If I am hearing you correctly, I would only submit one XML Sitemap for international content. It would look something like the below image. I would only use one GWT account to upload the file, and I would not need to add any additional markup on each page, as it will be located in the hreflang xml sitemap.
Finally, would it be a good or bad idea to 301 redirect their naming convention to a new, shorter one?
example.org/by-language/spanish/blog/this-is-an-example --> example.org/es/blog/this-is-an-example
-
Thank you very much Robert for your thorough follow-up. I am humbled at the insights you offered, and am very glad I asked about this. It is much more detailed than I was expecting, and definitely not something to make a hasty, uninformed decision on.
-
Jbanz,
I am happy to help. I want you to realize that for a first multi-lingual, international site, you are taking on a big project. You need to be very clear as to what you are doing before you do it. The reason I preface my comments is: I think you are getting confused between language and country/region or seeing them both as the same (they are not). NOTE: Before you begin to make changes to URLs, use a program like Screaming Frog so you do not lose any of your urls. You will be able to go back afterwards and compare apples to apples on your 301's. (Yes, based on the structure you gave in the example, I do think it would be good to clean them up.)
You state:** Their main content and audience is in the US, but they have started to add translated versions of the content in different languages (about 30 different** languages).
Then you state: **...****Webmaster Tools accounts and geotargetting them by language **If you are geotargeting, you are saying I want to influence a region (not a language). So, a gTLD for the US would set the geotargeting in WMT to US. That same site could have Spanish pages (we do this a lot in Texas), Vietnamese pages, etc. but you are geotargeting the US and you are providing content to people in the US who speak these various languages. That is different from having a gTLD that is trying to influence many worldwide markets. If the US site I mentioned wants to influence (target) all Spanish speakers in the world, you would not set the geo-targeting in WMT to the US as that would dampen your exposure in Spain, Chile, Mexico, etc. You would instead (if using a single site and directories) use the sitemap approach talked about in GWMT. It clearly says, "These annotations help Google serve the correct language or regional URL to searchers." So, you are deciding what you want to do and you can do both.
If you use the example from GWMT, they have an English site, but they want to target German speakers worldwide. So if you are saying that you have German pages and you want to geo-target German speakers in Switzerland and also all German speakers the sitemap would look like theirs. (See notes after code).
-
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" <br="">xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url><loc>http://www.example.com/english/</loc>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="http://www.example.com/deutsch/"
/>
<xhtml:link<br>rel="alternate"
hreflang="de-ch"
href="http://www.example.com/schweiz-deutsch/"
/>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="http://www.example.com/english/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></url><url><loc>http://www.example.com/deutsch/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="http://www.example.com/english/"
/>
<xhtml:link<br>rel="alternate"
hreflang="de-ch"
href="http://www.example.com/schweiz-deutsch/"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="http://www.example.com/deutsch/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></url><url><loc>http://www.example.com/schweiz-deutsch/</loc>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="http://www.example.com/deutsch/"
/>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="http://www.example.com/english/"
/>
<xhtml:link<br>rel="alternate"
hreflang="de-ch" **This is saying German speakers in Switzerland and establishes a location. **
href="http://www.example.com/schweiz-deutsch/" **This is the url for those in Switzerland who speak German. **
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></url>You must create a separate
url
element for each URL. Eachurl
element must include a loc tag indicating the page URLs, and anxhtml:link rel="alternate" hreflang="XX"
subelement for every alternate version of the page, including itself. </urlset> -
This example uses the language code
de
for the URL targeted at German speakers anywhere, and the language-locale codede-ch
for German speakers in Switzerland. If you have several alternate URLs targeted at users with the same language but in different locales, it's a good idea to provide a URL for geographically unspecified users. For example, you may have specific URLs for English speakers in Ireland (en-ie
), Canada (en-ca
), and Australia (en-au
), but want all other English speakers to see your generic English (en
) page. In this case you should specify the generic English-language (en
) page for searchers in, say, the UK.
Again, you are taking on a big task. Go at it slowly and methodically until you get the hang of it.
Best,
Robert -
-
Thank you Robert for your thorough explanation! I am sorry your first post timed-out, and I appreciate the follow up post. I added a little clarification based off of what you said.
-
Jbanz,
Your question is reasonable and I wrote an extensive answer that, when I hit post, all went away as moz had logged me out. Even though I could still go to my community profile, etc. and had an option to logout. Makes me want to scream. Spend a lot of time answering and nothing to show for it. But, maybe the shorter version is better.
So, since I have little time I will give you the condensed version. You are trying to use language to target countries and it won't work the way you are trying to do it. You cannot use geo-targeting of a generic TLD when you want to target more than one country.
What you need to do is back up two or three steps and read the following about sitemaps and targeting from GWMT:
Submit rel-alternate-hreflang annotations in a sitemap. (NOTE: not multiple sitemaps for urls from one gTLD domain) This will keep it simple for you. From GWMT (the bold is mine)
If your site targets users in many languages and, optionally, countries, you can use Sitemaps to provide Google with
rel="alternate" hreflang="x"
. These annotations help Google serve the correct language or regional URL to searchers. More information.Imagine you have an English language page, targeted at English speakers worldwide. You also have equivalent versions of this page targeted at German speakers worldwide, and German speakers located in Switzerland. Your full set of URLs is:
I hope this helps you out and makes it all simpler for you.
Robert
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
-
International SEO Two Subdomains Showing Up in Google Search Results
Hi I have a client that is having two subdomains showing up SERP when you Google their name. Here are the details. They have two subdomains us.companyname.com and en.companyname.com us.companyname.com is for the US and has completely different products and content than en.companyname.com en.companyname.com is the site designed for Europe and it is in English. How can I make it so that only the us. version shows up in the search results? Thanks in advance!
International SEO | | JohnWeb120 -
MultiRegional site indexing problems
Hello there!!! I have a multiregional site and dealing with some indexing problems. The problem is that google have only indexed our USA site We have: -set up hreflang tags -set up specific subdirectories https://www.website.com/ (en-us site and our main site) https://www.website.com/en-gb https://www.website.com/en-ca https://www.website.com/fr-ca https://www.website.com/fr-fr https://www.website.com/es-es ..... -set up automatic GEO IP redirects (301 redirects) -created a sitemap index and a different sitemap for each regional site -created a google webmaster's tool for each country targeted -created translations for each different language and added some canonicals to the US' site when using English content. The problem is that Google is not indexing our regional sites. I think that the problem is that google is using a US bot when spidering the site, so it will be always redirect to the US version by a 301 redirect. I have used fetch as google with some of our regional folders and asked for "Indexing requested for URL and linked pages", but still waiting. Some ideas?? changing 301 to 302? Really don't know what to do. Thank you so much!!
International SEO | | Alejandrodurn0 -
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 -
Different urls for the homepage on an international website
Hi! I was wondering what would be the best strategy to solve duplicated content generated by the homepage and its differents URLS This is an international website. Now it only has one language working: Spanish, but the url structure is already ready to work with the language approach So we have now www.brand.com -> Spanish Homepage (canonical www.brand.com/es)
International SEO | | teconsite
www.brand.com/es -> Spanish Homepage (canonical www.brand.com/es)
www.brand.com/index.php -> Spanish Homepage (canonical www.brand.com/es) I would like to know if this is the correct approach of if we should add 301 redirects instead of canonical. Let's image that they want to active the /en language, so they will have www.brand.com
www.brand.com/index.php
www.brand.com/es
www.brand.com/en now what? I image they have to use hreflang, but I am a little lost with how this should work. 301? canonical? hreflang? Could you help me? Thank you! Victoria0 -
Opening Up Webmaster Tools Geo-Targeting to Everyone Instead of US
Hi Mozzers, I wanted to get everyone's opinion on this. We have an e-commerce site that was targeting 3 different geo-locations. The main one is a .com. The other two were Canada and UK based. We recently turned off our Canada site and 301 to the .com. The .com site had been targeted towards United States in Google Webmaster Tools. Should I remove the Webmaster Tools geo-targeting now that Canada is pointing towards our main site? I don't want to lose rankings for US since that is our main market and the .com site is our main revenue driver and focus. I'm inclined to leave it as is because I still see our .com site ranking when I search in Google CA. From what I've seen is that it can take months for something to change and I definitely don't want anything to go awry. Just wanted to get everyone's thoughts on this. Thanks in advance.
International SEO | | SylviaH0 -
Wordpress international SEO Plugin - recommendations needed
Hi Mozzers, I am designing the web architecture for a international website and will be using Wordpress. Can anyone recommend a plugin that lets me SEO for all countries? I have used Yoast many times but it does not seem to work for International Web SEO Architectures. Thanks Carla Here is an idea of what I was thinking of doing Homepage.com Irish-homepage.ie or Homepage.com/ie Irish-Subpages.ie or Homepage.com/ie/subpage Irish-Subpages.ie or Homepage.com/ie/subpage Irish-Subpages.ie or Homepage.com/ie/subpage UK homepage.co.uk or Homepage.com/uk UK-subpages.co.uk or Homepage.com/uk/subpage UK-subpages.co.uk or Homepage.com/uk/subpage
International SEO | | Carla_Dawson0 -
Multilingual site - Best choice?
Quick question for a site that has the same content but in a different language (not machine translated) on seperate pages.
International SEO | | Crunchii
Say I have:www.mydomain.com (which is in English)
www.mydomain.com/ES (which is in Spanish)
www.mydomain.com/NL (which is in Dutch) I don't want to limit the ie. Spanish to only Spain so geotargeting isn't necessary What is the best/correct setup for the pages?0 -
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