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.
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?
-
Most assuredly use different CC-TLDs! I would also point to each from each as you have seen on many global sites. This will allow you to use different keywords also as Europe and the US have different spellings for the same words. So make sure your shopping cart software allows this if you are using the same across all domains.
This will help in link building also as it would be harder to get a spanish website linking to an english website even with sub domains.
-
I like that a lot! Can you rewrite product descriptions without maintaining separate databases? Would that involve a custom field or something?
-
Roger, The way we have approached this in the past was to go with separate TLD's using Magento. The main thing we did was to focus on a complete content rewrite for all pages including product descriptions to remove any possibility of duplicate content issues holding back the new sites and then set about localising with directories, webmaster tools and some low level link building. This seemed to do the trick in getting our .co.uk and .ie domains to rank above the older .com original site.
-
Hosting on a US server is not as much of a problem as it used to be because the search engines have worked this one out.
Where it appears you may have a problem is that the site is already established in the US which will make it more difficult to establish a UK site unless you go for the uk tld.
If you want to make sure UK visitors to the .com are sent to the right site, then a lightbox generated using JavaScript for non-US IP users would do the trick e.g. www.travelzoo.com
Once the user has selected UK then a cookie is dropped and they will always be sent to the UK site.
Make sure your country select page includes a no index, follow tag so that it doesn't get indexed, but does pass any link juice it happens to acquire.
-
It depends a bit on the client. While it's true that a new .ca domain will do better in Canada than a new .com domain, a brand new .ca may not do as well as your established .com which already has some authority. What we've often done was to setup a structure of www.clientsite.com/ca for the regional site. You can register www.clientsite.ca and 301 redirect it to to the subfolder.
If you do that, you can handle it in WT by creating multiple entries for the site, not declaring a region for the main domain but creating separate regions for each subfolder.
-
I kinda figured that was the case.
I know it is going to be more complicated then setting the market in WMT. Any specific advise around geo targeting for e-commerce?
Is hosting on a US server a problem if we were going to launch a site in the UK?
-
If you are going for other markets with the same language e.g. UK (English) then I would go with a separate local TLD because a .com with a /uk will struggle to establish itself in a new market like the UK.
Believe me when I say that it is not as simple as indicating in webmaster tools which markets you wish to target, especially if you already have an established site in the US on a .com
Go separate. Go local tld.
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
-
International SEO - Targeting US and UK markets
Hi folks, i have a client who is based in italy and they set up a site that sells travel experiences in the sout of Italy (the site currently sit on a server in Italy). The site has been set up as gTLDs: www.example.com They only want to target the US and the UK market to promote their travel experiences and the site has only the english version (the site does not currently offer an italian version). If they decide to go for the gTLDs and not actually change to a ccTLDs (which would be ideal from my point of view) how are the steps to be taken to set this up correctly on GSC? They currently only have one property registered on GSC: www.exapmple.com therefore i guess the next steps are: Add new property - www.example.com/uk and and set up geo targeting for UK Existing property - www.example.com/ set up geo targeting for US In case the client does not have the budget to optimise the content for american and british languages, would still make sense to have 2 separate property in GSC (example.com for US market and example.com/uk for UK market)? Few considerations: Add canonical tag to avoid duplicate content across the two versions of the site (in the event there is no budget to optimise the content for US and UK market)? Thank you all in advance for looking into this David
International SEO | | Davide19840 -
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!
International SEO | | matt-145670 -
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 -
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 -
Working with country specific domain names vs. staying with .com
I've recently inherited a client that has a country specific domain for Canada (.ca) but there is also a US branch for the company at the .com address. They have a direct competitor that operates also in the U.S. and Canada that has decided to operate entirely under the .com address and re-direct all .ca traffic to their .com address. When I compare the link analysis data for both the .ca, .com, and competitors site, I'm finding there is a huge difference between the .ca site and the competitors site, but not a huge difference between the .com site and the competitors site. For example, the domain authorities are as follows: myclient.ca (Canadian branch) - 22 myclient.com (US branch) - 46 competitor.com - 53 When I do a brand search for my client in Canada, the Canadian branch website shows up first, but the American one is second. At this point, would it be better for my client to consolidate the two branches into the .com address and focus on increasing external followed links to the .com website? Or, is there merit in continuing to create a separate inbound link strategy for the .ca site? Thanks.
International SEO | | modernmusings0 -
Is .in domain affecting international traffic inflow to my site?
My holiday website http://seekandhide.in/ was completed and went live in Feb 2012. Last month I got 83% traffic from India and 3-5% each from USA and UK. The rest is a mixed bag from other countries. This is largely the trend since the last 3-4 months. I want to attract more organic traffic from UK and rest of Europe. My SEO consultant says that with a .in domain that will be difficult. My website currently features unique holiday properties in India that typically attract European tourists so I don't think it is a product issue. But both website visits and sales enquiries remain primarily Indian even though total number of visitors have increased gradually over the last 6 months.. My queries are 1. Is it only the .in domain that's affecting inflow of international traffic? 2. Is there anything that I can do to offset it? 3. I own seekandhide.co.uk too. Is there something I can do with that site without building a whole different website there? If I shift completely to .co.uk, I will have the same issue of being geographically limited and end up losing Indian traffic. 4. Is there something else that is not ok on the site that I am missing? 5. Advice that I get from a lot of consultants is to buy seekandhideindia.com but I plan to add international properties in a couple of years so that name would limit my appeal. Thanks in advance! Sudha
International SEO | | Sudha_Mathew0 -
Correct Hreflang & Canonical Implementation for Multilingual Site
OK, 2 primary questions for a multilingual site. This specific site has 2 language so I'll use that for the examples. 1 - Self-Referencing Hreflang Tag Necessary? The first is regarding the correct implementation of hreflang, and whether or not I should have a self-referencing hreflang tag. In other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), I am uncertain whether the source code should contain the second line below: Obviously the Spanish version should reference the English version, but does it need to reference itself? I have seen both versions implemented, with seemingly good results, but I want to know the best practice if it exists. 2 - Canonical of Current Language or Default Language? The second questions is regarding which canonical to use on the secondary language pages. I am aware of the update to the Google Webmaster Guidelines recently that state not to use canonical, but they say not to do it because everyone was messing it up, not because it shouldn't be done. So, in other words, if I am looking at the source code for http://www.example.com/es/ (our Spanish subfolder), which of the two following canonicals is correct? OR For this question, you can assume that (A) the English version of the site is our default and (B) the content is identical. Thanks guys, feel free to ask any qualifiers you think are relevant.
International SEO | | KaneJamison1