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.
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!
-
If I understand the OP's intent, it is to target countries, not languages. Hreflang can specify alternates for a language, or a language-country combination, but unfortunately not just for a country. So, as the OP has proposed, yes you do need to specify the language and the country. And that does bring up a dilema faced by many of us in terms of what language to use. If your content is in all English, then yes you should use like "en-FR". BUT, you might also want to include an "fr-FR" as well, pointing to the same alternate URL. Because there are going to be a lot more France-based visitors on Google whose browser settings are for French language than English. For sure, both do exist (there are native English speakers in France too), but you don't have to choose one. You can include both. Google may not completely respect your directives since the content is in English (assuming that's the case), but it's what I would recommend. So, for each country (assuming the content is in English), include both an English and a language-specific hreflang tag (pointing to the same destination) for that country.
Since your last example uses "es-ES", I assume maybe that you're planning to also publish some content in Spanish language. But if not, again, realize you can include multiple hreflang tags for a single country, and pointing to the same page.
I also don't know where you are based. But if the business is US-based, I wouldn't duplicate US also as a localization. Rather, I would make that the default. Or, if you are based somewhere else, same thing, but with that country.
On question 2, you can set up a GSC property for folder paths (www.example.com/fr/), and target those. I would not target the root level (www.example.com) in your case, because that would also apply to all the subfolders. That's one of the advantages of using subdomains instead of subfolders, is that you can target each independently. But with subfolders, you can target all except the root (because it would cascade downward).
On question 3, you should do the same as you do in number 1, as long as you are duplicating those pages in each subfolder. Otherwise, if you don't give a directive of which page to index, since they are duplicates, Google is going to choose for you. And might not choose the one you prefer.
-
The language codes you are using in the above examples are not correct. The correct languages should be "en", "fr", "it", "es". If you want to specify the country code it must appear after the language code, more info here.
Keep in mind that the hreflang tags are not used by the web browsers to load the preferred language automatically, they are intended for search engines.
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 targeting
I'm offering an international service to any country from any destination, The website main language is English and i have 4 other languages as subdirectories, https://beassistance.com https://beassistance.com/de/ https://beassistance.com/es/ https://beassistance.com/fr/ https://beassistance.com/ru/ I'm looking to target by language not country, Should i choose "unlisted" for all the subdirectories? my second question regards the meta tags , my current meta tag rel="alternate" hreflang="ru-ru" href="https://beassistance.com/ru/" /> And i'm thinking about using rel="alternate" hreflang="ru" href="https://beassistance.com/ru/" /> Is that best practice to target by the language? Update I already have Hreflang Sitemap <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" <br="">xmlns:xhtml="http://www.w3.org/1999/xhtml">
International SEO | | MTBE
<url><loc>https://beassistance.com</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url></urlset> <url><loc>https://beassistance.com/de/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/fr/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/es/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/ru/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url>1 -
International Site Merge
Hello, I've never had to deal with an international site before, let alone a site merge. These are two large sites, we've got a few smaller old sites that are currently redirecting to the main site (UK). We are looking at moving all the sites to the .com domain. We are also currently not using SSL (on the main pages, we are on the checkout). We also have a m.domain.com site. Are there any good guides on what needs to be done? My current strategy would be: Convert site to SSL. Mobile site and desktop site must be on the same domain. Start link building to the .com domain now (weaker link profile currently) What's the best way of handling the domains and languages? We're currently using a .tv site for the UK and .com for the US. I was thinking, and please correct me if i'm wrong, that we move the US site from domain.com to domain.com/us/ and the domain.tv to domain.com/en/ Would I then reference these by the following: What would we then do with the canonicals? Would they just reference their "local" version? Any advice or articles to read would really be appreciated.
International SEO | | ThomasHarvey0 -
Geo-Targeting separate TLD's where both are .com domains
Hi I have a client who owns two separate TLDs for the same brand (for the sake of this post, we'll call the two sites www.site-a.com and www.site-b.com). For site www.site-a.com the website has been around for a while and is their primary site for their US operations which is their heartland, is well established in the SERPS and is where they make most of their money. As they looked to expand to the UK, they then created www.site-b.com and added the UK as a subfolder (so www.site-b.com/uk) and geo-targeted it towards the UK in Webmaster tools . The site has recently launched but they now find that, when a customer searches for their brand in the UK, they find www.site-a.com in position 1 (which, given it's tailored for a primary US audience, has a significantly lower conversion rate for UK traffic) and www.site-b.com in position 2. However, the client doesn't want to specifically geo target www.site-a.com to the USA as they feel it might affect where they appear for other international markets aside from the UK. So the question is, how can they, with the existing infrastructure, help remove www.site-a.com from the UK SERPs without adversely affecting their rank elsewhere? Hope this makes sense and thanks in advance for your help. James
International SEO | | jimmygs19820 -
Can you target the same site with multiple country HREFlang entries?
Hi, I have a question regarding the country targeting aspect of HREFLANG. Can the same site be targeted with multiple country HREFlang entries? Example: A global company has an English South African site (geotargeted in webmaster tools to South Africa), with a hreflang entry targeted to "en-za", to signify English language and South Africa as the country. Could you add entries to the same site to target other English speaking South African countries? Entries would look something like this: (cd = Congo, a completely random example) etc... Since you can only geo-target a site to one country in WMT would this be a viable option? Thanks in advance for any help! Vince
International SEO | | SimonByrneIFS0 -
International TLD Differentiation Concerns
Currently working on a project where the TLD of the parent company site is a .COM and the U.S. subsidiary is a .US. This is a first for me. What I do know. Both sites must be live Parent (.COM) targets essentially the entire international market US Subsidiary (.US) targets United States only Concerns are even with non-duplicate content will there be confusion there with the closely related domain, just a TLD change? Any suggestions are greatly, greatly appreciated!
International SEO | | dodgejd0 -
SEO international - ccTLD or Subdirectories / Hosting on 1 server (IP) in Netherlands
Hi All, I do mingle me in discussion if it's better to have an Ecommerce site of a Brand X on seperate ccTLD's (Brand.nl / Brand.de / Brand.com or use subdirectories (brand.com/nl, brand.com/de, brand.com/fr etc. I see a lot of comments on this, but i am missing one (maybe) essential part. We are using Magento with multi ccTLD support. BUT the environment is hosted in the Netherlands. Will we be "penalized" on hosting in NL when using www.brand.DE or other countries? Or is it MUCH better to host those ccTLD in country of Origin? Because if it is, maybe we can better use subdirs because then we can use our builded authority of the root domain. Hope someone have an answer on this one! Thanks! Jeroen
International SEO | | RetailClicks0 -
I need suggestions. We're helping a big journal to improve their external links, even though they've a site with over 10 million monthly visits, their external links are week. Any suggestions?
Please let us know where we can find information on how to improve external links for a very big journal site. Thanks.
International SEO | | carloscontinua0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0