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
-
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience?
What are the SEO implications of having a website hosted in Singapore (as a subdomain of the global website) when the website is targeting the UK audience? Will it be hard to get it to rank? Will there be problems with search console?
International SEO | | ToniFarrington-Allthingsweb0 -
Need help with search results for US site for a compnay that has many international sites
I am tasked with optimizing a US site for a company that has many international sites. Currently, if you search for just the main company name and don't include "USA" in your search, it won't even give you the US site on the SERP. It displays the Italian, French, etc etc sites - even though I'm searching on Google in the US with a preferred language of Engilsh. Unfortunately I don't have any control over the other sites, only the US one. Is there anything I can add to the US site (aside from setting the country code in GSC) so that when someone searches from within the USA, they get the US site and not all of the other ones? thanks!
International SEO | | SEOIntouch0 -
International Link Building Vendors
I'm working with a large enterprise site with many international domains. I have most of the markets covered but am having trouble identifying link building specialists/vendors in APAC - specifically Japan and Korea. Any recommendations from the community? Many thanks in advance!
International SEO | | JonClark150 -
International SEO Subfolders / user journey etc
Hi According to all the resources i can find on Moz and elsewhere re int seo, say in the context of having duplicate versions of US & UK site, its best to have subfolders i.e. domain.com/en-gb/ & domain.com/en-us/ however when it comes to the user journey and promoting web address seems a bit weird to say visit us at: domain.com/en-us/ !? And what happens if someone just enters in domain.com from the US or UK ? My client wants to use an IP sniffer but i've read thats bad practice and should employ above style country/language code instead, but i'm confused about both the user journey and experience in the case of multiple sub folders. Any advice much appreciated ? Cheers Dan
International SEO | | Dan-Lawrence0 -
Is International Geotargeting with Duplicate Content Effective?
A company located in Canada is currently targeting Canada through the geotargeting setting in Google Webmaster Tools. Google.ca rankings are good, but Google.com rankings are not. The company would like to gain more traction for US people using google.com. The idea on the table is to set up a subfolder www.domain.com/us/ and use WMT to designate this version for the US. Here's the kicker: the content is exactly the same. Will Google consider the US version duplicate content? Is this an effective way to target US and Canada at the same time? Is it better to forget a duplicate US site altogether and use the "unlisted" setting in WMT?
International SEO | | AliveWired0 -
How does Google Serve the correct language version?
Hi guys, I'm currently working on a multi lingual .eu website with 20 lanuages which has been live now for a month now. Its is a sub directory set up so the french language version would look something like www.example.eu/fr. The English language version defaults to the home page www.example.eu. When you search for the brand name on the local search engines the home page English version appears instead of the preferred language version for each Country. 90% of the external links so far link to the homepage so I'm guessing this is the reason why. We are still waiting for the development company to create sitemap for each language using the rel=”alternate” hreflang=”x” XML Sitemap Tool. I know Google look at a number of factors when deciding what results to give a user. Can anybody share their experience or advice here? Thanks Rob
International SEO | | daracreative0 -
Improving Search Rankings in other Countries for an existing site
Hello SEOmoz, I have a very well respected international client who ranks high in the US and for English language Google search results worldwide. However, the client's foreign language pages for specific countries do not show up on the first page of SERPs in those specific countries. The foreign nation/language pages are served on the same root domain as the main English language site it this fashion: www.client.com/france www.client.com/brazil Here are my questions: What can we do from an SEO standpoint to improve SERPs in Google.fr or other countries What is the best way to prevent duplicate content errors or prevent the wrong page from being indexed abroad. What are some best practices when using Google Webmaster tools in this regard? Thanks
International SEO | | BPIAnalytics0 -
International SEO with .com & ccTLD in the same language
I've watched http://www.seomoz.org/blog/intern... and read some other posts here. Most seem to focus on whether to use ccTLD, subdomains or subfolders. I'm already committed to expanding my US-based ecommerce to Canada with a .ca ccTLD. My question is around duplicate content as I take my .com USA ecommerce business to canada with a second site on a .ca URL. With the .com site's preference set to USA, and the .ca site's geo preference (automatically) set to Canada, is it a concern at all? About 80% of the content would be the same. FYI, .com ranks OK in Canada now and I want .ca to outrank it in Canada. I know 'localizing' content within the same language is important (independent of duplicate content), but this might not be viable in the short run given CMS limitations. Any direct experience to help quantify the impact here between US and Canadian ecommerce? Adding: I'm not totally confident here. From this google webmaster central post it seems that canonical tags aren't needed. I tend to think nothing is truly neutral and want to be confident regarding whether to use canonicals or not. Is it helpful, harmful or harmless? My site already has internal canonical tags and having internal and external would be a pain I think. @Eugene Byun used it successfully, but would the results have been the same without? Thanks!
International SEO | | gravityseo0