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
-
Why Google is not indexing each country/language subfolder on the ranks?
Hi folks, We use Magento 2 for the multi-country shops (its a multistore). The URL: www.avarcas.com The first days Google indexed the proper url in each country: avarcas.com/uk avarcas.com/de ... Some days later, all the countries are just indexing / (the root). I correctly set the subfolders in Webmaster tools. What's happening? Thanks
International SEO | | administratorwibee0 -
Google Analytics Search Console for International Countries
Hi Moz Community, Our e-commerce site is trying to gauge the opportunity of certain queries for specific countries. I'm trying to use the search console data presented in GA to do this. I'm looking at the top queries filtered by each country and also the top landing pages for each country as well. The non filtered data for queries and landing pages is completely different than by country and some if it looks wrong. For instance, our most popular query by impressions shows 0 query impressions in the US once filtered by country. Our site is based in the US so this doesn't make any sense, the same is true for landing pages. Is the queries and landing page data in GA under search console a combination of all countries? Since our target is set to the USA in search console is this data technically US based? How is this data so off? Thanks for answering!
International SEO | | znotes0 -
If domain mapping subfolders to TLD's is it perceived as a fully separate entity/site therafter ?
Hi I take it once you have domain mapped a country specific subfolder to a country specific TLD (for better local region targeting reasons) Google perceives it as a completely separate entity and it no longer shares any of the parent sites domain benefits (such as domain authority etc) so from that point on requires its own dedicated link building etc ? All Best Dan
International SEO | | Dan-Lawrence0 -
Multilingual Site with 2 Separate domains and hand-translated
I have 2 separate domains: .com & .jp
International SEO | | khi5
I am having a professional translator translate the English written material from .com. However, the .jp will have same pictures and videos that I have on the .com which means alt tags are in English and video titles are in English. I have some dynamic pages where I use Google Translate and those pages I place as "no index follow" to avoid duplicate issues and they are not very important pages for me any way. Question: since I am doing a proper translating - no machines involved - can I leave pages as is or should I include any format of these: ISO language codes
2) www.example/com/” /> Even though hand translated, the translation will probably be 85% similar to that if I used Google Translate. Will that potentially be seen as duplicate content or not at all since I have not used the Google Translate tool? I wonder from which angle Google analyses this. Thank you,0 -
Huge spike in referral traffic from international domains
We have recently experienced a huge spike in referral traffic from .fr domains (we are in the UK). They all lead to our 404 page. Its been going on for the last 3 days, and its still happening with about 20 visitors browsing the site from these domains at any one time, staying approx 3-7 seconds and then bouncing. The top domain appears to be a parked page. We cant see any obvious links or ads coming from any of these .fr domains and they are quite irrelevant to our sites industry anyway, which leads me to believe these may not be real visitors. Any advice on what may be causing this? And how to stop it? Needless to say none of these referrals have converted.
International SEO | | Silkstream0 -
International SEO - Setting up reporting
What would you consider to be a best practice for setting up international keyword tracking? Both in MOZ and in Google Analytics? Would you set them up by language? IE Spanish, French, German... Or by country? Mexico, Spain, US Spanish, French Canadian, French... ect... *Our website is set up with our countries in subdomains. We currently are in about 10 different countries and plan on expanding globally. Any advice helps! Much thanks!
International SEO | | ScentsySEO0 -
Researching (and launching a site within) a foreign language market
Morning peeps, A client wants to clone their website for a foreign language market, obviously swapping all English content for whichever language/market they're looking to target. Any advice on how to research a foreign market (when I only speak English), or perhaps any pitfalls to look out for or advice you might have with a launch like this? thanks
International SEO | | Martin_S0 -
Multilingual site - separate domain or all under the same umbrella
this has been asked before with not clear winner. I am trying to sum up pros and cons of doing a multilingual site and sharing the same domain for all languages or breaking it into dedicated subdomains e.g. as an example lets assume we are talking about a french property portal with an english version as well. Assume most of the current incoming links and traffic is from France. A) www.french-name.fr/fr/pageX for the french version www.english-name.com/en/pageX for the english version B) www.french-name.fr/fr/ for the french name (as is) www.french-name.fr/en for the english version the client currently follows approach A but is thinking to move towards B we see the following pros and cons for B take advantage of the french-name.fr domain strength and incoming links scalable: can add more languages without registering and building SE position for each one individually potential issues with duplicate content as we are not able to geotarget differenly on web master tools of google potential dilution of each page's strength as we will now have much more pages under the same domain (double the pages basically) - is this a valid concern? usability/marketing concerns as the name of the site is not in english (but then people looking for a house in France would be at least not completely alien to it) what are your thoughts on this? thanks in advance
International SEO | | seo-cat0