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
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
-
Multilang site: Auto redirect 301 or 302?
We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header. https://domain.com
International SEO | | fJ66doneOIdDpj
30x > https://domain.com/en
30x > https://domain.com/ru
30x > https://domain.com/de The site architecture is set up with proper inline HREFLANG.
We have read different opinions about this, Ahrefs says 302 is the correct one:
https://ahrefs.com/blog/301-vs-302-redirects/
302 redirect:
"You want to redirect users to the right version of the site for them (based on location/language)." You could argue that the root redirect is never permanent as it varies based on user language settings (302)
On the other hand, the lang specific redirects are permanent per language: IF Accept-Language header = en
https://domain.com > 301 > https://domain.com/en
IF Accept-Language header = ru
https://domain.com > 301 > https://domain.com/ru So each of these is 'permanent'. So which is the correct?0 -
Using same URL for both "en" and "en-us" hreflang tags
Hi,I have a question. Is it okay if I use the same URL for both "en" and "en-us" hreflang tags? For example, for my en-us page: Is this okay with Google? What are your thoughts on this?
International SEO | | Avid_Demand0 -
Should Hreflang x-default be on every page of every country for an International company?
UPDATED 4/29/2019 4:33 PM I had made to many copy and pastes. Product pages are corrected Upon researching the hreflang x-default tag, I am getting some muddy results for implementation on an international company site older results say just homepage or the country selector but…. My Question/Direction going forward for the International Site I am working on: I believe I can to put x-default all the pages of every country and point it to the default language page for areas that are not covered with our current sites. Is this correct? From my internet reading, the x-default on every page is not truly necessary for Google but it will be valid implemented. My current site setup example:
International SEO | | gravymatt-se
https://www.bluewidgets.com Redirects to https://www.bluewidgets.com/us/en (functions as US/Global) Example Countries w/ code Site:- 4 countries/directories US/Global, France, Spain Would the code sample below be correct? https://www.bluewidgets.com/us/en/ (functions as US/Global) US/Global Country Homepage - https://www.bluewidgets.com/us/en/ US/Global Country Product Page(s) This would be for all products - https://www.bluewidgets.com/us/en/whizzer-5001/ http://www.bluewidgets.com/us/en (functions for France) France Country Homepage - https://www.bluewidgets.com/fr/fr/ France Country Product Page(s) This would be for all products- https://www.bluewidgets.com/es/es/whizzer-5001 http://www.bluewidgets.com/us/en (functions as Spain) Spain Country Homepage - https://www.bluewidgets.com/es/es/ Spain Country Product Page(s) This would be for all products - https://www.bluewidgets.com/es/es/whizzer-5001 Thanks for the spot check Gravy0 -
Hreflang tags and canonical tags - might be causing indexing and duplicate content issues
Hi, Let's say I have a site located at https://www.example.com, and also have subdirectories setup for different languages. For example: https://www.example.com/es_ES/ https://www.example.com/fr_FR/ https://www.example.com/it_IT/ My Spanish version currently has the following hreflang tags and canonical tag implemented: My robots.txt file is blocking all of my language subdirectories. For example: User-agent:* Disallow: /es_ES/ Disallow: /fr_FR/ Disallow: /it_IT/ This setup doesn't seem right. I don't think I should be blocking the language-specific subdirectories via robots.txt What are your thoughts? Does my hreflang tag and canonical tag implementation look correct to you? Should I be doing this differently? I would greatly appreciate your feedback and/or suggestions.
International SEO | | Avid_Demand0 -
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 -
E-Commerce - Country Domains versus 1 Domain?
Hi, Just wanted to get some feedback and opinions re the idea of segmenting our ecommerce site languages under various domains, like .jp for japanese, .it for italian etc... I do understand the geolocation benefits that this could bring us, but on the flipside, it would mean that we would need to grow our domain authority, link buiding per country domain, which is quite a bit of work. Has anyone ever considered or implemented this and any thoughts? Thanks!
International SEO | | bjs20100 -
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 -
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