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.
In the U.S., how can I stop the European version of my site from outranking the U.S. version?
-
I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu.
My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site.
Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic!
-
Hi Gianluca.
Thanks so much for the detailed explanation! I appreciate your taking the time to provide all that great info.
Unfortunately, I'm not sure what to do here. I understand the client made a mistake in launching one site for all of Europe, but I know they'll never pay to build out separate sites for each target country (at least not right now).
At the risk of sounding like an annoying client, what if I was to use the "en-us" hreflang tag on the U.S. site and just "en" on the English version of the European site as a temporary fix? (Then once we launch the translated versions of the European site – in Spanish, French, and Italian – we'd tag them as "es," "fr," and "it.")
Would that help at all with my issue of having the European site outrank the U.S. site in the U.S. SERPs?
Thanks again for taking the time to try to steer me in the right direction. From your answers, I feel like I have a pretty good handle on what we should do in an ideal world. Unfortunately, this situation is not ideal, so I'm looking for a relatively quick band-aid fix... but I'm getting the sinking feeling that there's no such thing.
-
Hi Alan!
yes, I was saying exactly that. If you're going for an international multi-country SEO and you have to deal with countries that share language, like in the case of Ireland and Uk, it is better to target them with two different "sites" (being a site in a ccTld or subfolder or sibdomain, depending on business convenience).
if you're doing multi-cointry SEO and one of your targeted counties has 2+ official languages, then the ideal solution is having a ccTld for that country and creating as many subfolder translated versions as are the official languages of that country.
For instance:
www.domain.be, with the French version appended from the root,
www.domain.be/nl/, with the Flemish translated version.
As alternatives be you can redirect 302 via user agent from domain.com to /fr/ or /nl/, while always letting users to eventually choose the alternate version via language selector.
-
Gianluca
Thanks for jumping in on this one. So if I'm reading your answer correctly, the bottom line here that there really should be one site per country, regardless of language spoken, correct?
-
Hi Alan and Matt,
I am sorry to tell you that if you set up the hreflang for "Europe" as hreflang="en-GB", that won't work.
That annotation, in fact, tells Google to show the URLs having it only to users searching in English from Great Britain.
It would be better to use only "en" in European website.
Said that, this is not the best solution either, because it is telling Google: "show this to users searching in English globally (but not if they are in the USA).
If the European web site is meant to reach users who not necessarily are using English as default language (eg: Spanish, French, Italians, Germans et al), than a solution could be tagging the European website with the "x-default" hreflang.
Note, though, that this a quite extreme use of the x-default.
The big mistake, anyway, is creating an European website itself:
- Google does not consider political regions like European Community nor continents and geographical areas like "Asia", "Middle East", "Europe";
- Because of 1, you cannot geotarget a website but for Political States (Spain, UK, Russia...)
- To think that not-English speaking users will use English for searching something it is not realistic, therefore it is correct what Matt says in his answer re: translated versions served in whatever format (ccTld, sudomain, subfolder) better fits your business needs.
Finally, personally I would not suggest to a ccTld for targeting European users, because that ccTld would geotarget the site to its country (eg: .es to Spain). Better a generic domain name (.net or even .eu, which is a generic domain name and does not have any geotargeting power), or even a subfolder/subdomain.
Finally, when creating the different country sites, I remind you that in certain countries is spoken the same language. For instance Ireland and UK share English, but they have different currencies, obviously different postal system and phone numbers and, especially, a different culture, so that you should not think in having an European EN version serving all the English speaking countries, but localizing each one of them.
To not talk, and I really end my answer, countries like Switzerland (French, German, Italian and Romance), Spain (Spanish and Catalan), Belgium (French and Flemish), Ukraine (Russian and Ukranian).
-
Yeah inheriting previous work can be a challenge.
Since you are already planning on rolling out content in different languages, you will have not only the opportunity to set the hreflang tags for each, but also it will be important to ensure all of the content within each section is actually in that section's primary language for consistency. That too will help address the confusion Google has.
-
Thanks, Alan! That's great info. Yes, we do have only one set of content for all of Europe at this point – but we'll be pushing out translated versions in several different languages soon so we will definitely take your advice on the hreflang tags. I wish we had set up separate domains for the U.S. and European sites, but I wasn't involved in that decision unfortunately. Still good to hear your insight on that topic though.
-
Have you set the different hreflang tags appropriately across your content?
You said "US" and "European" - so does that mean you have just one set of content for all of Europe? If so, that can be more difficult to deal with, however if you set all of the US pages with an hreflang of "en-us" and the European pages with an hreflang of en-gb, you can at least help Google understand "this set is for the U.S. and this set is not".
What I always recommend if you're not targeting individual countries with your content (the "Europe" reference you made says you are not for that content), is to at the very least, split out content to two different domains. Have a .com domain for US content, and a separate .eu or .co.uk or .de or whatever other domain for your European content. That, while also setting up hreflang tagging, is really more helpful in communicating what should show up in which search results higher up.
You'll also need to accumulate inbound geo-relevant links to point to the appropriate content set to help reinforce this.
And if you split out domains, you can set country targeting more readily in Google Search Console.
For more info:
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
-
How can I restrict the domains country by country?
Hello, I have Two Domains one is xyz.co.uk and other is xyz.com Now, my main target for .com is United States, and I don't want to open that .com domain in any other country especially India. The same with the .co.uk, I dont want to open .co.uk in other countries. I did it with some developer help but it gave me redirected error in Google Webmaster. Can anyone please guide me how I can do this the proper way ? And Other issues is, how can I implement ,if any user in United States open xyz.co.uk than he should redirect to the .com version. Thank you.
International SEO | | AmitTulsiyani0 -
What's the difference between 'en-gb' and 'en-uk; when choosing Search engines in campaign set up?
Hi What's the difference search engine wise and which one should I choose, i presume GB since covers entire British landmass whereas UK excludes Ireland according to political definition, is it the same according to Google (& other engines) ? All Best Dan
International SEO | | Dan-Lawrence0 -
Problems with the google cache version of different domains.
We have problems with the google cache version of different domains.
International SEO | | Humix
For the “.nl” domain we have an “.be” cache..
Enter “cache:www.dmlights.nl” in your browser to see this result. Following points are already adapted: Sitemap contains hreflang tag Sitemap is moved to the location www.dmlights.nl/sitemap.xml We checked the DNS configuration Changed the Content language in de response header to : Content-Language: nl-NL Removed the cache with webmastertools Resolved serverrequest errors. Can anyone provide a solution to fix this problem? Thanks, Pieter0 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
What is the proper way to setup hreflang tags on my English and Spanish site?
I have a full English website at http://www.example.com and I have a Spanish version of the website at http://spanish.example.com but only about half of the English pages were translated and exist on the Spanish site. Should I just add a sitemap to both sites with hreflang tags that point to the correct version of the page? Is this a proper way to set this up? I was going to repeat this same process for all of the applicable URLs that exist on both versions of the website (English and Spanish). Is it okay to have hreflang="es" or do I need to have a country code attached as well? There are many Spanish speaking countries and I don't know if I need to list them all out. For example hreflang="es-bo" (Bolivia), hreflang="es-cl" (Chile), hreflang="es-co" (Columbia), etc... Sitemap example for English website URL:
International SEO | | peteboyd
<url><loc>http://www.example.com/</loc></url> Sitemap example for Spanish website URL:
<url><loc>http://spanish.example.com/</loc></url> Thanks in advance for your feedback and help!0 -
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 -
International (foreign language) URL's best practices
I'm curious if there is a benefit or best practice with regards to using the localized language on international sites (with specific ccTLDs). For example, should my french site (site.fr) use the french language as keywords within the URLs or should they be in english? e.g. www.site.fr/nourriture vs. www.site.fr/food Is that considered best practice for SEO (or just for brand perception those markets?). Is there a tangible loss in SEO if we do not use the correct language for those URLs and just stick with English around the world? I recall seeing a Matt Cutts video on the topic and he said that google does support i18n URL's but other SE's might not support them as gracefully but he didn't come down with a hard recommendation to go with i18n URL's or just English. Would love a strong ruling in favor one direction based on best practices.
International SEO | | mongillo0 -
Targeting Different Countries... One Site or Separate?
I have a client who has 3 ecommerce sites. They are somewhat differentiated but for the most part sell the same stuff. Luckily 2 of them are quite authoritative, old and rank reasonably well. Most of the visitors and sales come from the US. He wants to start targeting Europe, Mexico and Canada. What are your suggestions for doing this? Are we better targeting on the main domains? Not really sure how to do that? Should we use a subdomain and a new store front for each geo? Should we use a .co.uk .co.mx and .co.ca each with a unique storefront? It looks like we are moving to a Magento platform so setting up multiple storefronts on a single database is not a big issue. Anyone have any experience with this?
International SEO | | BlinkWeb0