Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
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
-
-
Nope, not needed, unless you are changing the language.
Now, if you wanted to do one big site and then offer certain pages that are the same except for "translation" - and it's a local dialect translation, then yes, HREFLANG would be used in that situation.
So you could use HREFLANG rather than a canonical between the kinda duplicated pages if they are changed only in dialect translation. But since there is different content per country, you would still need that geo-targeted section for the content that is different.
domain.com/congo/about-congo-office (I don't know the country code for Congo) - No hreflang, will be geo-targeted with the subfolder.
domain.com/congo/similar-product-page - If just translated to the local Congo English dialect, use HREFLANG with all similarly "translated" pages. If not changed at all, use canonical to the original page. If changed overall to target the Congo market, no canonical or HREFLANG needed.
-
For option 2, or 1 for that matter, would you use hreflang to do any of the targeting or just geotarget with WMT?
-
Hmmm, I am thinking there are two possible solutions.
1. Create a "site" per country (subfolders like you have now), but use canonical for the pages that are duplicated, the pages that are the same across all countries.
Also use javascript to detect a new user's location (don't auto redirect though, ask) to get them to the "right" version of the page, if they come into the non-country focused general page.2. Create a "site" per country (subfolders like you have now), and spend the resources to change the content on each page just enough to target that country. It doesn't have to be much, just enough to target that group.
Option 2 is the most time and resource intensive. Option 1 can be messed up quickly if the technical implementation isn't done right.
I know that's not a clean answer but international never is. There are always so many moving parts.
-
Yes. Beneficial information would be local events, customer stories/wins, press releases, local sales contact information, local partners, etc
-
This is tough. Let me ask you one question: For a potential customer in South Africa, is there any different information they need to see than someone in the Congo, or somewhere else in the world that speaks English? If yes, what kind of different information would they need to see?
-
We choose to target our sites based on where the regional/country offices are located. So in the example of South Africa our main African office is located in South Africa so the site content (events, forms, news) is based primarily on South Africa. That being said much of the content is duplicated from our main corporate English site. Our South African site mainly targets South Africa but could potentially go after any English speaking African country. Since the ZA site is primarily targeting a country with a duplicated language, is your recommendation to only geo-target via webmaster tools and not utilize hreflang? Most of our regions/countries do their best to translate the language on their sites but many follow the same tactic as my South African example, some content is local but most is a duplicate of our Corporate English site. What is the best tactic to not have duplicate content and to get the right sites ranking in the correct local version of Google?
-
Excellent answer Kate!
-
This is one of the instances that made me change the way I see the HREFLANG tag. So many people disagree but hear me out.
The HREFLANG tag is only for language differentiation. There are language and country codes because, as you point out, there are many countries that speak the same language and some have some major dialect changes. The biggest example being UK and US English. Therefore, if you have a site developed in US English that you want to "translate" to UK English, but not change the content of the site other than that, you would use HREFLANG tags to note the difference in the pages to Google. Since you changed nothing else (no currency changes, no legal changes, no product set changes), there is no reason for country targeting. You are just translating the same content ... aka changing a few words.
Now, let's say that you are operating a site that has a geo-targeted section to South Africa. Depending on the setup, you might not need HREFLANG tags at all. If you are changing the content other than through translation to target South Africa, that is geo-targeting. Targeting the country.
You can do both geo-target AND change language settings. For instance, if you are a Canadian company that legally has to have all of it's content in Canadian French (fr-ca) and Canadian English (en-ca), you would use HREFLANG between those two. But then you decide to move into the US. You might create a subfolder, subdomain, or ccTLD specific to the US market since you can't offer all of your products or services over there due to regulations. You would geo-target the new section/site to the United States, but not use HREFLANG since the content is targeted at a different country. You would want to make sure the content changed enough and the Canadian English pages might rank for a while but over time the US site/section would get stronger.
I hope that all makes sense.
In your instance where you have geo-targeted, I assume that is for a reason. However, because you have geo-targeted that section to South Africa, you cannot geo-target it to the Congo as well. You would either need to great a section for the Congo and geo-target that, or, if geo-targeting isn't really needed, use one big site and country specific translations. Only do this if your content is the same across the board and you are changing some of the wording to local dialects.
If you want to know more, check out my international search tool that might help you find what structure you should have: http://www.katemorris.com/issg/
-
What is the preferred way to indicate to Google that one site(or subfolder in this case) is targeted to the same language in multiple countries?
the only way to target everyone Speaking the language on the one URL is telling Google Webmaster tools not to specify a location or geo-target.
I do not know if that is the best method for you but if you just want to target English with one subfolder and have multiple countries you would take that away if you geo-targeted it to a country.
May be the best ways to handle it is multiple subfolders I wish I had a better answer for you but if you want to use one sub folder it would be to not target and to use an IP address from a server inside the country you wish to target the most.
e.g
All you have to do is list the alternative version of the pages and have the x default at the bottom. For example, this is what you would do for the English Canadian version:
Specific regions in countries can be done the same way you would do something in Canada.
the other method would be to pick the countries with additional subfolders.
you can target the same language in multiple countries by not adding to the additional information
Canada for instance let's say you did not want to target French and you wanted to target the United States as well
with one subfolder it could not be done. If you set it up to something like this I know that's one subfolder and one domain
-
Why would I target the main domain to a country that I have a subfolder for? My question is based on targeting one site (that is already set up via a subfolder) with the same language to multiple countries. What is the preferred way to indicate to Google that one site(or subfolder in this case) is targeted to the same language in multiple countries? Is this possible?
It may help to understand that my site is set up with multiple subfolders that target countries or regions. Some sites are translated and have local content for a specific country or region and other sites are in English but have content specific to that local country or region. I am worried about the sites that are in English but should be targeted to a specific region or country.
-
the answer is yes you can
here are some more thorough resources
https://support.google.com/webmasters/answer/189077?hl=en
http://www.branded3.com/blogs/implementing-hreflang-tag/
http://moz.com/blog/using-the-correct-hreflang-tag-a-new-generator-tool
http://searchenginewatch.com/sew/how-to/2232347/a-simple-guide-to-using-rel-alternate-hreflang-x
you can create the tags that this tool or create a site map using the tool below
http://www.internationalseomap.com/hreflang-tags-generator/
http://www.themediaflow.com/tool_hreflang.php
you can validate everything with this as well
http://www.seerinteractive.com/blog/case-study-the-impact-of-hreflang-tag/
by the way the way you can validate with screaming Frog the same can be done with deep crawl on a larger level.
hope this helps,
Tom
-
you could target one language using this method
as long as you add a subfolder or a sub domain preferably a subfolder. You can keep adding entries.
Take a look at http://moz.com/learn/seo/hreflang-tag
&
https://sites.google.com/site/webmasterhelpforum/en/faq-internationalisation
Hope this helps,
Tom
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
-
Correct Hreflang & Canonical Tags for Multi-Regional Website English Language Only having URL Parameters
Dear friends, We have a multi-regional website in English language only having the country selector on the top of each page and it adds countrycode parameters on each url. Website is built in Magento 1.8 and having 1 store with multiple store views. There is no default store set in Magento as I discussed with developer. Content is same for all the countries and only currency is changed. In navigation there are urls without url parameters but when we change store from any page it add parameters in the url for same page hence there are total 7 URLs. 6 URLs for each page (with country parameters) and 1 master url (without parameters) and making content duplicity. We have implemented hreflang tags on each page with url parameters but for canonical we have implemented master page url as per navigation without url parameters Example on this page. I think this is correct for master page but we should use URL parameters in canonical tags for each counry url too and there should be only 1 canonical tag on each country page url. Currently all the country urls are having master page canoncial tag as per the example. Please correct me if I am wrong and **in this case what has to be done for master page? **as google is indexing the pages without parameters too. We are also using GEOIP redirection for each store with country IP detection and for rest of the countries which are not listed on the website we are redirecting to USA store. Earlier it was 301 but we changed it to 302. Hreflang tags are showing errors in SEMRush due to redirection but in GWT it's OK for some pages it's showing no return tags only. Should I use **x-default tags for hreflang and country selector only on home page like this or should I remove the redirection? **However some of the website like this using redirection but header check tool doesn't show the redirection for this and for our website it shows 302 redirection. Sorry for the long post but looking for your support, please.
International SEO | | spjain810 -
How to Localise per Region (Europe, America, APAC, EMEI) and not per country as best SEO practise?
Hi SEO expertises! I am currently working with a client that initially have an English website targeting UK users but want to expand their market into four new regions (Europe, America, APAC and EMEI) keeping English as a main language. I would like to request your help here as I told the client ISO location and hreflang it will be just possible per language and they must need to localise each English region with local keywords, however I would like to double check if it will be any way (Sitemap, Hreflang) we can tell Google we are targeting per region and not per country? Thanks a lot!
International SEO | | Atalig20 -
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 -
Worldwide and Europe hreflang implementation.
Hi Moz ! We're having quite a discussion here and I'd like to have some inputs. Let me explain the situation and what we plan to do so far. One of our client has two separate markets : World and Europe. Both pages versions will be mostly the same, except for the fact that they will have their own products. So basically, we'd want to show only the European EN version to Europe and the standard EN version to the rest of the world, same goes for FR and ES. As far as IT, DE, CS and SK, they will only be present within the european version. Since we cannot target all Europe with a single hreflang tag, we might have to do it for every single european countries. Regarding this subject, SMX Munich recently had quite an interesting session about this topic with a confirmation coming from John Mueller saying that we can target a single URL more than once with different hreflang tags. You can read more here : http://www.rebelytics.com/multiple-hreflang-tags-one-url/ So having all this in mind, here's the implementation we plan to do : www.example.com/en/ Self canonical www.example.com/fr/ - hreflang = fr www.example.com/es/ - hreflang = es www.example.eu/it/ - hreflang = it www.example.eu/de/ - hreflang = de www.example.eu/cs/ - hreflang = cs www.example.eu/sk/ - hreflang = sk www.example.eu/fr/ - hreflang = be-fr www.example.eu/fr/ - hreflang = ch-fr www.example.eu/fr/ - hreflang = cz-fr www.example.eu/fr/ - hreflang = de-fr www.example.eu/fr/ - hreflang = es-fr www.example.eu/fr/ - hreflang = fr-fr www.example.eu/fr/ - hreflang = uk-fr www.example.eu/fr/ - hreflang = gr-fr www.example.eu/fr/ - hreflang = hr-fr etc… . This will be done for all european countries (FR, EN and ES). www.example.com/en/ - x-default Let me know what you guys think. Thanks!
International SEO | | Netleaf.ca0 -
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 -
Hreflang tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
Subdomains or subfolders for language specific sites?
We're launching an .org.hk site with English and Traditional Chinese variants. As the local population speaks both languages we would prefer not to have separate domains and are deciding between subdomains and subfolders. We're aware of the reasons behind generally preferring folders, but many people, including moz.com, suggest preferring subfolders to subdomains with the notable exception of language-specific sites. Does this mean subdomains should be preferred for language specific sites, or just that they are okay? I can't find any rationale to this other than administrative simplification (e.g. easier to set up different analytics / hosting), which in our case is not an issue. Can anyone point me in the right direction?
International SEO | | SOS_Children0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1