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
-
Multilang site: Auto redirect 301 or 302?
We need to establish if 301 or 302 response code is to be used for our auto redirects based on Accept-Language header. https://domain.com
International SEO | | fJ66doneOIdDpj
30x > https://domain.com/en
30x > https://domain.com/ru
30x > https://domain.com/de The site architecture is set up with proper inline HREFLANG.
We have read different opinions about this, Ahrefs says 302 is the correct one:
https://ahrefs.com/blog/301-vs-302-redirects/
302 redirect:
"You want to redirect users to the right version of the site for them (based on location/language)." You could argue that the root redirect is never permanent as it varies based on user language settings (302)
On the other hand, the lang specific redirects are permanent per language: IF Accept-Language header = en
https://domain.com > 301 > https://domain.com/en
IF Accept-Language header = ru
https://domain.com > 301 > https://domain.com/ru So each of these is 'permanent'. So which is the correct?0 -
How do you optimise a website for European traffic?
I have a design portfolio website here https://www.nicholsoncreative.com/ which uses a .com but is currently configured through the Search Console to appear in results for Google.co.uk. I am going to be restructuring the website and optimisation and I want to bring in more traffic/enquiries/business from around Europe. As there's no Google.eu, and as Google also serves results based on the searchers geographic location it would seem difficult to structure and optimise content so that results can be found across all of Europe. I assume simply switching to a .eu domain extension for my own website wouldn't solve the problem? I also assume that creating content in different languages would be a logical (if time consuming) option? Are there any other tried and trusted techniques that can be used to target traffic throughout Europe? I'd appreciate any advice.
International SEO | | JCN-SBWD0 -
Help! Choosing a domain for a European sub-brand when working as a partner in North America
Background: Let's say there's a European company ABC.com, they have some presence in the US already for a lot of product brands in a certain space (let's say they make widgets). ABC Co gets 1,600 searches a month and all of that volume centers around the widgets they are known for. ABC Co purchases a company that makes gears, let's call it Gears Inc (gears.com). Gears Inc. was known for making gears in Europe, but their brand is not known in the US (search volume 0). Ideally, I would keep the Gears Inc. brand and build up the presence in the US, separating it from ABC Co. ABC Co wants to maintain their brand and eliminate Gears Inc. But we've received permission to keep the Gears brand for bringing that product to the US ... we will have an uphill battle building up the brand recognition, but at least it won't get lost in what ABC Co is already known for in the US. (ie: we don't want calls for widgets). Domain Situation: ABC Co. has redirected gears.com (DA 1) to a subdomain: {gearmakers}.abcco.com (DA 66) ... they have agreed to place a landing page under that 301 that links to the regional domains (theirs in the EU and ours in the US/North America). They are unwilling to let us use or purchase gears.com OR 301 gears.com directly to our domain. What we're trying to do: build Gears Inc. as a recognizable brand when someone searches "gears inc", this domain would rank first create a simple "brand domain" that a less-tech-savvy users could easily navigate to needs to have recognition in US, Canada and Mexico
International SEO | | mkretsinger
I don't know if this helps or provides anything more? The question is what do we use as our domain name? Any feedback is appreciated!0 -
International Site Merge
Hello, I've never had to deal with an international site before, let alone a site merge. These are two large sites, we've got a few smaller old sites that are currently redirecting to the main site (UK). We are looking at moving all the sites to the .com domain. We are also currently not using SSL (on the main pages, we are on the checkout). We also have a m.domain.com site. Are there any good guides on what needs to be done? My current strategy would be: Convert site to SSL. Mobile site and desktop site must be on the same domain. Start link building to the .com domain now (weaker link profile currently) What's the best way of handling the domains and languages? We're currently using a .tv site for the UK and .com for the US. I was thinking, and please correct me if i'm wrong, that we move the US site from domain.com to domain.com/us/ and the domain.tv to domain.com/en/ Would I then reference these by the following: What would we then do with the canonicals? Would they just reference their "local" version? Any advice or articles to read would really be appreciated.
International SEO | | ThomasHarvey0 -
Two versions of a website with different languages - Best way to do it?
I'm working on a website for a Swedish artist and her page is in Swedish, everything is in Swedish on the site, even though it's not a lot of text on the site. We would like to have the site in English too, or another version of the site in English on a separate domain, what's the best way to proceed from here? The domain name is a .se (swedish domain), would it be better to create a another domain and host the english version of the site on a .com domain? Or will we bump into problems with duplicate content if we create a replica of the swedish site in english. We're using wordpress and I know that there's translation plugins out there, is that a good option? I'm a bit clueless on how to proceed and would love some help or guidance here.
International SEO | | Fisken0 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
Country specific domains pointing to a .com site
Hello, I am new to seo so please be easy if this happens to be a "silly" question. My company has a .com site. We are expanding into global markets, focusing on specific countries right now. General question: Would I be penalized for duplicate content if I purchased country-specific domains and pointed them to the .com site? Thanks, Jim
International SEO | | jimmer0 -
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