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
-
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 -
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 -
Advanced Hreflang !
Hey Everyone: We are currently implementing hreflang tags on our site, and we have many parameter pages with hreflang tags; however, I am afraid these may be counted as duplicate content without canonical tags. example.com/utm_source=tpi href='http://example.com/de" hreflang="de" rel="alternate" href='http://example.com/nl" hreflang="nl" rel="alternate" href='http://example.com/fr" hreflang="fr" rel="alternate" href='http://example.com/it" hreflang="it" rel="alternate" I have two questions 1. On the parameter pages (which have hreflang tags like above) do we also need a canonical tag on example.com/utm_source_tpi pointing to example.com ? 2. On the homepage (page without the parameter), should I add a self referencing hreflang tag? (href="http://example.com/" hreflang="es") Thanks so much for your help! -K
Technical SEO | | TeespringMoz0 -
Redirects on multi language site and language detection
Hello! I have a multi language site in German and English. The site ranked well for the brand name and for German keywords. But after switching to a contend delivery network and changing the language detection method from browser language to IP location the site had indexing and ranking problems. Also in SERP the English homepage is shown for German keywords. On the other hand the language detection method is more accurate now. Current setup: The languages are separated via a folder structure for the languages: www.site.com/**en **and www.site.com/de. If the users IP is in Germany he is redirected via 302 from .com to .com/de. The rest of the world is redirected via 302 to .com/en. So the root www.site.com/ doesn't exist but has the most of the backlinks. Each folder has one sitemap under /de/sitemap.xml and /en/sitemap.xml. Each site and the root (.com, .com/de, .com/en) was added to WMT (no geo targeting) and the sitemaps were added (on the root domain both sitemaps and on the language specific sites just one). The sitemaps have no hreflang tag. Each page has an hreflang tag in the header pointing to itself and the alternate language. hreflang="x-default" is not set anywhere. Also on each page is a link to change language. Goals: From an SEO point of view we primarily target German speaking people. But a lot of international people (US, South America, Europe) search for our brand name so we want to serve them the English site. Therefore we want to: Get all the link juice when someone links to www.site.com to the German site Show Germans the German site in SERP and all others the English one Still serve the language automatically based on the location Do you have any idea how to achieve this? I think our main problem is that we want to push the German site the most but still serve the English site for most people (and therefore the Google Bot). Also does submitting the same sitemap twice (on the domain site and folders) do any harm? Any help oder links to ressources are greatly appreciated. I read a ton of articles but they are mostly for the case that english is the default language. Thanks for you help Moz community! Alex
Technical SEO | | AlexBLN1 -
International architecture: Country specific subfolders > domain mapping to tld
Hi Ive got a clients dev saying they are setting up with country/language specific subfolders (as i recommended) BUT now they are saying they want to set up on network.domain.com (for example) and then each language will have its own sub-folder BUT will be domain mapped to the TLD as and when they get them. I have asked them to clarify since sounds a bit strange since thought best to have domain.com then /uk and /us etc etc and sure ok to forward country specific TLD's to these subfolders. Its this new subdomain (network.) thats concerning me and mapping rather than forwarding (or is it the same thing) but anyone know off hand if above sounds ok or also thinks a bit strange or know issues with such a set up ? many thanks dan
Technical SEO | | Dan-Lawrence0 -
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 -
I've consolidated other domains to a single one with 301 redirects, yet the new domain authority in MOZ is much less that the redirected ones. Is that right?
I'm trying to increase the domain authority of my main site, so decided to consolidate other sites. One of the other sites has a much higher domain authority, but I don't know why after a 301 redirect, the new site's domain authority hasn't changed on over a month. Does MOZ take account of thes types of things?
Technical SEO | | bytecgroup2 -
Best geotargeting strategy: Subdomains or subfolders or country specific domain
How have the relatively recent changes in how G perceives subdomains changed the best route to onsite geotargeting i.e. not building out new country specific sites on country specific and hosted domains and instead developing sub-domains or sub-folders and geo-targeting those via webmaster tools ? In other words, given the recent change in G perception, are sub-domains now a better option than a sub-folder or is there not much in it ? Also if client has a .co.uk and they want to geo-target say France, is the sub-domain/sub-folder route still an option or is the .co.uk still too UK specific, and these options would only work using a .com ? In other words can sites on country specific domains (.co.uk , .fr, .de etc etc) use sub-folders or domains to geo-target other countries or do they have no option other than to develop new country specific (domains/hosting/language) websites ? Any thoughts regarding current best practice in this regard much appreciated. I have seen last Febs WBF which covers geotargeting in depth but the way google perceives subdomains has changed since then Many Thanks Dan
Technical SEO | | Dan-Lawrence0