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
-
Help with international targeting
Hi all! Okay, so we've got a site, let's say example.com - we sell training courses worldwide with a particular focus in just 8 countries.
International SEO | | JamieM1611
Historically, we've never targeted users in different countries effectively, we've just got the example.com that floats about ranking in different countries, but our content is dynamic (obviously a big SEO no-no - we pick up the IP of the user and show the content relevant for that country without the URL's changing)
This obviously presents an SEO flaw in that we can effectively target people in our key countries effectively. So, we're introducing the targeting as subfolders (/uk/, /ie/ etc) my questions are: 1. Would this be the correct implementation of hreflang AND canonical tags for the URL: https://www.example.com/es/ 2. The second thing I was wondering is the 'international targeting' in search console. We haven't (because of our current set up) set a target country for www.example.com (because of the lack of regional targeting and dynamic catch all) - would we be better leaving that untargeted and only specifying the regional targets for the new subfolder URLs (www.example.com/us/ /uk/ etc) or should we set the .com as the USA as default? We'd be a bit weary of doing this because most of our traffic comes from the UK and South Africa, so I'm assuming it would be best to leave this alone unless someone else has a different opinion? I know Googlebot almost always crawls .coms from US, which is why we were thinking of leaving the .com as the 'catch all' and specifying the US version. 3. Finally, we do have a lot pages which don't really change at all (like the about us page) would we give these any special directives to avoid duplicate content (as the content on these won't be changing at all?) or do we just keep the structure as shown above? I.E would the about us page (even though not changing) still be (with the canonical): URL: https://www.example.com/about-us/ (x-default) ? Thanks in advance!0 -
Dual language in multiple URLs
Hi ! I wonder if anyone has ever experienced this problem before. One of our client is having some trouble with his multilanguage and international website. A small number of URLs contains 2 different language. Exemple : http://exemple.com/es-ar/productos/compression-baggers/empacadora-formacion-llenado-sellado/ The part in bold is in english and the rest in spanish.
International SEO | | PhilC-M
I need some help to find the source of the problem. The number of URLs like this doesn't stop to increase, but it remains under control. I temporarily implanted 302 redirects while trying to find the source of the problem and fix it. Thank you for your help.0 -
Country and Language Specific URL Paths
Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication?
International SEO | | mattdinbrooklyn0 -
What's the best homepage experince for an international site?
Greeting Mozzers. I have a question for the community, which I would appreciate your input on. If you have a single gTLD that services multiple countires, what do you think is the best homepage UX for the root homepage and why? So the example would be you own website www.company.org and target content to Germany, Japan and Australia with content through the folder structure eg. www.company.org/de-de If someone comes to the www.company.org from a region, would you: Redirect them based on location IP – so if from Germany they land on www.company.org/de-de Let them land on the homepage which offers location selection Let them land on a page with content and offer location selection eg. pop-up or obvious selection box Something I’ve not thought of… I'd appreciate your input. Thanks
International SEO | | RobertChapman0 -
In the U.S., how can I stop the European version of my site from outranking the U.S. version?
I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu. My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site. Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic!
International SEO | | matt-145670 -
Website Domains, Geographical targeting and Duplicate Content
My colleagues in Holland have 2 websites. I've copied and pasted their question - my comments are at the bottom "www.ancoferwaldram.nl with NL, EN and FR language www.ancoferwaldram.com with only EN language The EN versions Google sees as “duplicate content” so we have to get rid of that. I think we better use 1 website: www.ancoferwaldram.com with NL, EN, FR and maybe other languages and deactivate www.ancoferwaldram.nl Or keep the www.ancoferwaldram.nl with only the NL language? Or keep the www.ancoferwaldram.nl with direct links to www.ancoferwaldram.com and no content?" The focus is to get the site to rank in Non-eu countries for export. So given the .nl has higher DA (though only about 15) would it be better to have seperate .fr, .be, .com sites for specific languages and geo targeting. Or would it be better to keep everything on the same site? If so which domain? i assume that the duplicate content can be resolved by stating which is the canonical version, once the domain strategy is resolved welcome any thoughts here. 🙂
International SEO | | Zippy-Bungle0 -
Sub-domains or sub-directories for country-specific versions of the site?
What approach do you think would be better from an SEO perspective when creating country-targeted versions for an eCommerce site (all in the same language with slight regional changes) - sub-domains or sub-directories? Is any of the approaches more cost effective, web development-wise? I know this topic's been under much debate and I would really like to hear your opinion. Many thanks!
International SEO | | ramarketing0 -
Best practice for multi-language site?
Recently our company is going to expand our site from just english to multi-language, including english, french, german, japanese, and chinese. I deeply understand a solid and feasible plan is pretty important, so I want to ask you mozzers for help before we taking action! Our site is a business site which sells eBook software, for the product pages, the ranks are taken by famous software download sites like cnet, softonic, etc. So the main source of our organic traffic is the guide post, long-tail keywords. We are going to manually translate the product pages and guide post pages which targeting on important keywords into other languages. Not the entire english site. So my primary question is: should I use the sub-domain or sub-category to build the non-english pages? "www.example.com/fr/" or "fr.example.com"? The second question: As we are going to manually translate the entire pages into other languages, should I use the "rel=alternate hreflang=x" tags? Because Google's official guideline says if we only translate the navigations or just part of the content, we should use this tag. And what's your tips for building a multi-language site? Please let me know them as much as possible Thanks!
International SEO | | JonnyGreenwood0