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
-
SiteName Attribute Showing in Different Language in SERP
We are currently experiencing issues with our subdomain SiteName. Our parent company root domain is a Japanese language site, but we have an English subdomain that is for the United States primarily, and nearly rest of world for organic traffic. Our issue is that we have followed the guidelines here: https://developers.google.com/search/docs/appearance/site-names There was a large post on here with many responses including Googlers with issues others were having, but it has since been removed. Here is the code in place on our homepage: <script
Technical SEO | | Evan_Wright
type="application/ld+json"> { "@context": "https://schema.org",
"@type": "WebSite",
"name": "Mescius Developer Tools",
"alternateName": ["Mescius, inc.", "developer.mescius.com"],
"url": "https://developer.mescius.com" }
</script> Unfortunately this is what is appearing in the SERP. It is using the Japanese equivalent of our parent company. Screenshot 2024-02-23 at 3.37.55 PM.png Even though the relationship between root and subdomain should not be causing this, it seems like something is impacting this incorrect SiteName, and it is impacting CTR for the subdomain. Has anyone else experienced this and found a fix?0 -
General questions about implementing hreflang using XML sitemap
I created another thread regarding hreflang sitemaps. However, this one is more general and doesn't cover multiple sitemaps for different localizations so I think it's reasonable creating a new thread. We are trying to implement hreflang using XML sitemap. We have localized content for a few countries, but only 1/3 of the content is 'duplicate' localized content. How should this be presented in the sitemap? Can we have some urls with hreflang-tags and some without? Also, where should this be located? In the usual sitemap file at site.com/sitemap.xml or should we create a different sitemap site.com/hreflang.xml where we just paste all hreflang-info? And if it should be in /hreflang.xml - can we have the same URL twice (in both current sitemap and hreflang sitemap)?
Technical SEO | | Telsenome0 -
How to use rel=alternate and hreflang=es to help with International SEO?
We have completed translating our important pages from English to Spanish on our website. I am confused if I should be adding attributes like rel=alternate and hreflang=es to links. On our homepage we have links to our solution pages and the code looks like this: <a href="https://www.membroz.com/es/club-management-software/">...</a > <a href="https://www.membroz.com/es/salon-management-software/">...</a > <a href="https://www.membroz.com/es/pre-school-management-software/">...</a > Should I add the attributes rel & hreflang to them? It would look something like this: ... <a <span>rel="alternate" hreflang="es"</a <span> href="https://www.membroz.com/es/salon-management-software/">... <a <span>rel="alternate" hreflang="es"</a <span> href="https://www.membroz.com/es/pre-school-management-software/">...
Technical SEO | | Krtya0 -
HREFLANG: language and geography without general language
Some developers always implement the hreflang for German (which should be "de") as "de-de", so language German and country Germany. There is usually no other German version targeting the other German-speaking countries (mostly ch, at). So obviously the recommendation is to make it "de" and that's the end. But I kept wondering and not finding anything: IF there is a more specialised hreflang, will google take that if there is no default? Example: Search in: de-at (or de-ch) Search result has the following hreflang versions: de-de; x-default (==en), en => Will Google give the result for x-default or de-de?
Technical SEO | | netzkern_AG0 -
Best practice for URL - Language/country
Hi, We are planning on having our website localized into more languages. We already have an English and German version. The German version is currently a sub-domain: www.example.com --> English version de.example.com --> German version Is this recommended? Or is it always better to have URLs with language prefixes such a: www.example.com/de www.example.com/es Which is a better practice in terms of SEO?
Technical SEO | | Kilgray1 -
Hreflang Tag great for Google, what about Bing or others?
I've read that the Hreflang Tag is all the rave for International solutions on a per page basis. I haven't read much about what International agencies are using for non-Google search engines such as Bing. Is the common language meta tags the only solution? would love to see an article that addresses this
Technical SEO | | MikeSEOTruven0 -
Best way to setup large site for multi language
Hello, I am setting up a new site which is going to be very large, over 250,000 products. Most of our customers are in the UK (45%), the rest are from various European countries and the USA. Unfortunately we only have a team of two people writing content for these pages in English. I would value some input on the best way to setup my website structure for ranking. Obviously the best would be individual country oriented domains I.e. domain.fr domain.de domain.co.uk . However we wouldnt have the time to create content for every page and most pages would contain the same content as the English domain. Would I get a penalty for this from google? The second choice is to follow the example of overstock.com and pull in information relating to each country I.e. currency and delivery time. this would be a lot easier but I am concerned that the lack of geo focus would effect my rankings. Does any one have any ideas?
Technical SEO | | DavidLenehan0 -
Domain with more Languages
Hey folks! I was wondering what you would do. I do have a Website. The website is provided in 8 other languages. Right now every language has it's own Domain name. The domain name is always the country in the language. I'm thinking about combine everything to one domain and hope to get some great linkjuice from the other 7 domains. So it would be www.example.com/en/ www.example.com/fr/ and so on. How do you handle that. Would this have a big positive impact on that one domain I'm forwarding to?
Technical SEO | | leitpix
I really think so!0