How should I handle hreflang tags if it's the same language in all targeting countries?
-
My company is creating an international version of our site at international.example.com. We are located in the US with our main site at www.example.com targeting US & Canada but offering slightly different products elsewhere internationally. Ideally, we would have hreflang tags for different versions in different languages, however, it's going to be an almost duplicate site besides a few different SKUs. All language and content on the site is going to be in English. Again, the only content changing is slightly different SKUs, they are almost identical sites. The subdomain is our only option right now. Should we implement hreflang tags even if both languages are English and only some of the content is different? Or will having just canonicals be fine? How should we handle this?
Would it make sense to use hreflang this way and include it on both versions? I believe this would be signaling for US & Canda visitors to visit our main site and all other users go to the international site. Am I thinking this correctly or should we be doing this a different way?
-
Hi tcope25,
Thanks for the clarification, that helps me to understand better the end goal. To futher clarify, you say "we want every other visitor in the world to visit our international subdomain." Do you mean "every other [English speaking] visitor in the world." ? If so, I think your proposed code is close. It is now just missing a self-referencing element, so it should be:
Just keep in mind that even if your tags are perfect, if your English US site has significantly more authority, it may show up in international search results anyway as rel="alternate" hreflang is a signal, not a directive.
Hope that helps!
Dana
-
Thanks for your comments Dana! I do appreciate the time you took to help explain more about hreflang.
I have implemented hreflang on multiple other websites in different languages without any issues. However, this situation is a bit different. To answer your questions...yes, our main site is the English site in the US & Canada. Same exact site, URL, content. We want every other visitor in the world to visit our international subdomain.
If implemented the code below, what would happen if I searched our website brand in the US? Would our main site come up? What would happen to a searcher in France? Would Google serve our international site?
By your comments above are you suggesting the below?
-
Hi tcope25,
Implementing rel="alternate" hreflang is likely one of the most complex, and most commonly incorrectly implemented elements for SEO. Just the example you've provided above would take about 30 minutes to talk through, clarify business needs, and then determine a course of action.
I normally don't push off answering a question, but I would highly recommend seeking out an SEO professional to help you sort this out. Tere's just a lot wrong with the proposed code above - sorry, not trying to be insulting, but helpful.
One real standout in your proposed code above that I would not recommend is to set your "x-default" to one of your secondary international sites. The "x-default" if used, should point to your strongest, primary version of your business sites. For example, if your English site in the US is your primary, most important site, then your "x-default" should the English US site URL.
Also based on your code above, it looks like you are serving the same content, via the same URLs to US and Canada searchers. If this is true , meaning you are not localising content for Canada and it is 100% the same page (I hope you aren't showing different content to US and Canada visitors via the same URL by attempting to use geo-location to decide what they see - that's a whole separate SEO issue) - then you don't need "en-us" and "en-ca" you just need "en" - But you would need to be sure that you haven't set your International Targeting in Google Search Console to "United States" - You need to leave the country targeting there unchecked.
This are very high level observations - I would recommend engaging a reliable SEO consultant to help make sure it's all implemented correctly.
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
-
Incorrect homepage country variant appearing in search resutls
Hi, Background I have an international site with 32 country homepages within the same domain: eg www.domain.com/en-gb/
International SEO | | coma99
www.domain.com/fr-fr/
www.domain.com/de-de/
www.domain.com/es-es/ and so forth We use IP redirection on the root www.domain.com (which has no HTML page of its own) to divert the user to their relevant country homepage. Within each country homepage we include: (a canonical link to itself) ... (hreflang alternates to all instances of other homepages including itself ) Our Google Crawl bot is located in Germany and so when it crawls our root www.domain.com it takes the title and description from its destination url which in crawlbots case is www.domain.com/de-de/ because of the IP redirect. What is the problem I am trying to solve? Every variation of local Google results (eg UK/FR/IT/US) displays at the top the crawled root www.domain.com page with German title/description. How can I stop this happening? Surely adding appropriate hrefs and canonicals to every homepage instance is sufficient for Google to display to you your relevant country homepage variant instead!? Thanks0 -
Important pages are being 302 redirected, then 301 redirected to support language versions. Is this affecting negatively the linking juice distribution of our domain?
Hi mozzers, Prior to my arrival, in order to support and better serve the international locations and offering multiple language versions of the same content the company decided to restructure its URLs focused on locale urls. We went from
International SEO | | Ty1986
https://example.com/subfolder to https://example.com/us/en-us/new-subfolder (US)
https://example.com/ca/en-us/new-subfolder (CAN)
https://example.com/ca/fr-ca/new-subfolder (CAN)
https://example.com/de/en-us/new-subfolder (Ger)
https://example.com/de/de-de/new-subfolder (Ger) This had implications on redirecting old URLs to new ones. All important URLs such as https://example.com/subfolder were
302 redirected to https://example.com/us/en-us/subfolder and then 301 redirected to the final URL. According to the devs: If you change the translation to the page or locale, then a 302 needs to happen so you see the same version of the page in German or French, then a 301 redirect happens from the legacy URL to the new version. If the 302 redirect was skipped, then you would only be able to one version/language of that page.
For instance:
http://example.com/subfolder/state/city --> 301 redirect to {LEGACY URL]
https://example.com/subfolder/state/city --> 302 redirect to
https://example.com/en-us/subfolder/state/city --> 301 redirect to
https://example.com/us/en-us/new-subfolder/city-state [NEW URL] I am wondering if these 302s are hurting our link juice distribution or that is completely fine since they all end up as a 301 redirect? Thanks.1 -
Is It valuable to use hreflang tags for blog posts?
I realize it's important to use hreflang tags when your site is translated into multiple languages and that content is very similar if not identical to the original language. However, is there value in having hreflang tags implemented for every blog post that gets translated? Does the same value hold true? In my case, the blog posts which get translated into different languages can somewhat vary from the original. By no means are they a direct translation. They are often adapted to meet the needs of that language and audience.
International SEO | | UnbounceVan0 -
Sitelinks in multiple language
Hello ! In a french browser & french Google interface with no browsing history, I have the french version of my website indexed, but the site links coming along with it are in English ! Is there any way to combat this? Note - we use a 302 language re-direction. See screenshot here: http://bit.ly/25kViB0
International SEO | | TechWyse0 -
Soft Launch App with Country Targeting To Match?
Hi,
International SEO | | eTinaRose
We're gearing up to do a soft launch of our app in a few countries, such as Australia. Our website says to request early access since the app is not yet publicly available in the apple store. However, it will be in those soft launch countries. This is what I'm considering... Creating a subdomain site such as au.liquidtext.net (liquidtext.au is not available). And setting that site, au.liquidtext.net, to be country targeted to Australia via webmaster tools. Once the app is available internationally, and the main site has been updated to show this, I would then redirect any subdomains to the main site. Thoughts? Are there any negative repercussions to this this approach that I am not considering? Thank you for your help Moz community!! Tina0 -
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 -
Alternate tag. Anybody had success getting English websites only with localized currency served with alternate tag?
I have an English website with USD prices and US phone.
International SEO | | lcourse
Via currency dropdown visitors in Ireland can choose EUR as currency, visitors from Denmark Danish crown etc and via GEO IP I also serve local contact phone numbers. So I though it made sense to define this with the alternate tags, but now after several months google still does not pickup these pages in local searches. Did anybody have success with getting a website just with currency parameter ranked locally using the alternate tag? Does it help to have also static links (not only dropdown links) to currency versions on the page? Any other thing that could help to have google pick these up? Below my code sample:0 -
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