Hreflang for multple countries but single language
-
I'm working on a site that has implemented hreflang.
The site is all in English but has slight differences and breaks down to separate domains, so
the hreflang implementation targets specific countries per domain.
This was tested using http://flang.dejanseo.com.au but Webmaster Tools has thrown up errors. For example,
**URLs for your site and alternative URLs in 'en_GB' that do not have return tags. **But every page refers back.Any ideas what's going wrong?
-
The only valid redirection is the one based on user browser, not IP, IMHO.
However, if you want to use that kind of redirection for the home page (not the others pages), then that redirection should be working the first time, so that users can eventually choose to go to another version of the site they prefer (i.e.: I live in Spain and I go to domain.eu. When I travel in the US, I still want to go to domain.eu, not always being pushed to use domain.com).
Moreover, doing that, you will let crawlers to discover also the others version even though they were redirected to the one corresponding to their IP the first time. In other words, Googlebot (Mountain View, USA, IP), the first time will go always to domain.com, but once there it will able to discover also domain.eu and domain.co.uk from the versions selector, and it won't be redirected again to domain.com.
Said all this, the fact is that you want to target a political area (EU) with domain.eu, the world with domain.com and the UK with domain.co.uk.
This desire to target three different kind of geographies complicates everything :-).
The only solution I see is:
-
Domain.com set up as "global" >> hreflang="en". All users using English will see it in the SERPs despite of their location but in these cases (see point 2 and 3);
-
Domain.eu set up as the site for the European countries >> hreflang="en-ES" - hreflang="en-IT" - hreflang="en-DE" and so on.
-
Domain.co.uk set up as the site for Great Britain >> hreflang="en-GB".
Doing this and implementing the hreflang in the canonical URLs of the sites and referencing only canonical URLs of the others sites (apart having the self-referral hreflang), then you should be safe.
However, remember that with those hreflang, people searching in another language than English will never (or almost never) see your sites but for brand name searches or very specific brand + product queries.
Therefore, I am still of the idea that having only English websites for targeting the world means missing a huge business opportunity.
-
-
Hi Michael,
The tool crawls with the user agent "Hreflang.org Testing Tool - Desktop version". It does not impersonate Googlebot. It does not follow 301 redirects because if you use Hreflang to point to another page, you should link to the canonical version of that page. A 301 redirect indicates an error.
My opinion is that forced, IP-based redirection is not a good idea because all URLs must be accessible from all locations. Google recently (about a year ago?) started crawling from other countries but you still want all URLs to be accessible from everywhere. The point of Hreflang is to indicate links across URLs; so hreflang makes IP-based redirection unnecessary.
If you really want to do IP-based redirection, do it on the x-default version of the page. And use the x-default version solely for redirection. For example, don't have your English version as the x-default and then redirect non-English users to other versions. If you do that, Germany-based crawlers won't ever be able to access your English URL.
-
Hi Nikhilesh,
as a matter of interest is your tool crawling as a google bot, rather than some IP? We have now set to deliver TLD depending on IP but the tool reports the following for the hreflangs not on the same domain
- Could not load this page. Server responded with HTTP Status code 301. Expected HTTP response code is 200 OK.
-
thanks. I'm taking a look.
-
I believe what's happening with your site is the same thing as what happened here on Google webmaster forums. JohnMu replied in that thread to say that because you have the same content on different sites (it might say en-US or en-GB but there is no detectable language customization for country). Google considers this duplicate content and starts ignoring some of your pages. And when some pages get ignored, the hreflang return tags from those pages go missing.
I blogged about this phenomenon in detail here.
Of course, it's also possible that your Hreflang markup has errors that the dejan seo tool did not detect. You can try the tool at hreflang.org to get a second opinion.
-
This is a bit difficult. All 3 domains are bringing in some good diverse country traffic as is, but Google has said it will now ignore hreflang until resolved.
So for example, .com brings in traffic and sales from Chile, Mexico and Bahamas. So if we removed the 'global' for .com are we not risking dropping the traffic for these locations. Or will Google ignore anyway and serve? There are too many countries getting traffic to implement each one as hreflang and remove the global en, it would be massive.
But having said that if the server was setting the TLD to be served depending on location it would then be adequate to just use the 'global' hreflang's to hreflang="en"? Is that right?
-
You should consider using either one subfolder hreflang or strongly considering wire going into these markets for instance Germany would be best for .de if you are just targeting a European country that speaks English for only English-speaking countries throughout the world you may be best off with A geotld
i agree with Gianluca.
-
If your .eu domain targets English in all European countries but UK (and you are targeting the USA with the .com), then you should not use the hreflang:
because that annotation says to Google to show the .eu domain to all the people using English independently from where they are, but in the UK ("show domain.co.uk") and USA ("show domain.com"). In other words, you .eu site would be visible to Canadian, Australians or even people in Greenland using English.
If that is also the meaning of the .eu domain, than that's fine, but if it is meant just for European countries, then better not having it.
Moreover, if the .eu is meant as "global", then it is useless to add all the hreflang like "en-it", "en-es" and so on, because the hreflang="en" would be enough.
However, I hope you are considering the .eu in English for targeting countries like Italy, Spain, France, Germany et al as temporary, because - let me tell you - you are not going to see lot of traffic from European not English speaking countries. Why? Because we don't search in English, neither we have our browser set up to use English as main language
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
-
Rank regional homepages using canonicals and hreflangs
Here’s a situation I’ve been puzzling with for some time: The situation
Technical SEO | | dmduco
Please consider an international website targeting 3 regions. The real site has more regions, but I simplified the case for this question. screenshot1.png There is no default language. The content for each regional version is meant for that region only. The website.eu page is dynamic. When there is no region cookie, the page is identical to website.eu/nl/ (because Netherlands is the most important region) When there is a region cookie (set by a modal), there is a 302 redirect to the corresponding regional homepage What we want
We want regional Google to index the correct regional homepages (eg. website.eu/nl/ on google.nl), instead of website.eu.
Why? Because visitors surfing to website.eu sometimes tend to ignore the region modal and therefor browse the wrong version.
For this, I set up canonicals and hreflangs as described below: screenshot2.png The problem
It’s 40 days now since the above hreflangs and canonicals have been setup, but Google is still ranking website.eu instead of the regional homepages.
Search console’s report for website.eu: screenshot3.png Any ideas why Google doesn’t respect our canonical? Maybe I’m overlooking something in this setup (combination of hreflangs and canonicals might be confusing)? Should I remove the hreflangs on the dynamic page, because there is no self-referencing hreflang? Or maybe it’s because website.eu has gathered a lot of backlinks over the years, whereas the regional homepages have much less, which might be why Google chooses to ig nore the canonical signals? Or maybe it’s a matter of time and I just need to wait longer? Note: I’m aware the language subfolders (eg. /be_nl) are not according to Google’s recommendations. But I’ve seen similar setups (like adobe.com and apple.com) where the regional homepage is showing ok. Any help appreciated!0 -
Google displaying root domain instead of country locale
Hi, For many months now, Google refuses to display the relevant locale in many markets, and instead shows the root domain as number 1 result. The country locale isn't even in the SERP in some countries(!). This only applies for branded searches. It appears Google is treating the root domain as an international landing page or something, while this isn't the case - visitors get redirected automatically based on their Geo-IP to the relevant country locale if they enter the root domain, there is no "flag selector" that people or bots can choose. Site: example.com If someone searches for "example" from Google Canada, they should be met with example.com/en-ca/ as the first result for branded searches. Instead, example.com is ranking, and example.com/en-ca/ is nowhere to be found. This problem is in all our English markets; Canada, India and UK. For non-english countries, branded searches return the relevant locale, but the root domain is often the 2nd result as well. This isn't as bad as the case with the English markets, but still. Any help whatsoever would be greatly appreciated, or if you can recommend great reading assets. I have researched this thoroughly and tried different technical solutions, but nothing has worked so far. Thanks!
Technical SEO | | LeoVegas0 -
International SEO - Hreflang tags and URL Structure
Hello, I wonder if any SEO internationalisation experts can help. We are a UK centric business with a .com domain which all our traffic currently goes to. We have been growing in the US and are therefore looking to internationalise our website by building out some US pages using the subfolder .com/us. Since the keywords we wish to target in the US are different to the keywords we are targeting elsewhere, when implementing hreflang tags is it possible to use a different URL for the US page? So let’s say we are targeting ‘estate car’ generally but want to target ’station wagon’ as the keyword for the equivalent US page, can the URLs be different? Example: General page: www.example.com/estate-car US: www.example.com/us/station-wagon Hreflang tags: Would that be the correct implementation? Any help or guidance would be much appreciated!
Technical SEO | | SEOCT0 -
Google tries to index non existing language URLs. Why?
Hi, I am working for a SAAS client. He uses two different language versions by using two different subdomains.
Technical SEO | | TheHecksler
de.domain.com/company for german and en.domain.com for english. Many thousands URLs has been indexed correctly. But Google Search Console tries to index URLs which were never existing before and are still not existing. de.domain.com**/en/company
en.domain.com/de/**company ... and an thousand more using the /en/ or /de/ in between. We never use this variant and calling these URLs will throw up a 404 Page correctly (but with wrong respond code - we`re fixing that 😉 ). But Google tries to index these kind of URLs again and again. And, I couldnt find any source of these URLs. No Website is using this as an out going link, etc.
We do see in our logfiles, that a Screaming Frog Installation and moz.com w opensiteexplorer were trying to access this earlier. My Question: How does Google comes up with that? From where did they get these URLs, that (to our knowledge) never existed? Any ideas? Thanks 🙂0 -
Hreflang in country specific XML Sitemaps?
Hello! I'm rolling out hreflang tags in my client's "main" XML Sitemap. My question is: do we need to implement these tags in the country level XML Sitemaps also? Thanks!
Technical SEO | | SimpleSearch1 -
Sites for English speaking countries: Duplicate Content - What to do?
HI, We are planning to launch sites specific to target market (geographic location) but the products and services are similar in all those markets as we sell software.So here's the scenario: Our target markets are all English speaking countries i.e. Britain, USA and India We don't have the option of using ccTLD like .co.uk, co.in etc. How should we handle the content? Because product, its features, industries it caters to and our services are common irrespective of market. Whether we go with sub-directory or sub-domain, the content will be in English. So how should we craft the content? Is writing the unique content for the same product thrice the only option? Regards
Technical SEO | | IM_Learner0 -
Duplicated content in moz report due to Magento urls in a multiple language store.
Hi guys, Moz crawl is reporting as duplicated content the following urls in our store: http://footdistrict.com and http://footdistrict.com?___store=footdistrict_es The chain: ___store=footdistrict_es is added as you switch the language of the site. Both pages have the http://footdistrict.com" /> , but this was introduced some time after going live. I was wondering the best action to take considering the SEO side effects. For example: Permanent redirect from http://footdistrict.com?___store=footdistrict_es to http://footdistrict.com. -> Problem: If I'm surfing through english version and I switch to spanish, apache will realize that http://footdistrict.com?___store=footdistrict_es is going to be loaded and automatically it will redirect you to http:/footdistrict.com. So you will stay in spanish version for ever. Deleting the URLS with the store code from Google Web Admin tools. Problem: What about the juice? Adding those URL's to robots.txt. Problem: What about the juice? more options? Basically I'm trying to understand the best option to avoid these pages being indexed. Could you help here? Thanks a lot.
Technical SEO | | footd0 -
Multi- language URL best practices
we have two different content perlanguage (Fr. EN )) they are not Duplicated and they are completly different. what is better for the URL a language sub domain or a folder fr.mycompany.com or mycompany.com/fr/
Technical SEO | | omarfk0