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.
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.
-
Hi Thomas,
If a page doesn't have an equivalent on the other country version then you don't need to specify hreflangs really, you can just specify the one of the page that exist if you want, to keep the consistency, although if you see: the goal of the hreflang is to specify Google which is the "best" URL to show in their results when a search is done and there are many that could be relevant as they target the same queries, but should be targeted to different audiences, since in this case there will be only one, then it's not necessary to do it.
Thanks,
Aleyda
-
Hi Aleyda,
The reason we want to merge to one domain is because the higher ups want to, so that's what is happening.
Anyway, thank you for your in depth reply unfortunately having suggested that the site merge and https goes live at the same time development won't be able to achieve that.
I do only have one question left really, if a page doesn't have an equivalent on one site. What does the rel alternate have to be, is it left blank or does it go to the main language url?
Thanks,
Tom
-
Hi Thomas,
Why do you want to merge them on a single domain? If you want to consolidate everything on a single .com domain -which is recommended in case you don't want complexity and capitalize your authority better, while targeting international markets effectively-, then it would be to:
-
Migrate by 301-redirecting your current domains to their relevant country directories that you will enable in your .com, and that should be geolocalized independently each one through the Google Search Console (https://support.google.com/webmasters/answer/62399?hl=en) to their specific countries: .com/gb/ to the UK and .com/us/ to the US, so each one of them can effectively be geo-targeted. Since you have an independent mobile site on an "m" subdomain this case you also have to do the same for them: m.yourbrand.com/gb/ geolocalized to the UK and m.yourbrand.com/us/ geolocalized to the US.
-
Use hreflang annotations (https://support.google.com/webmasters/answer/189077?hl=en) to specify for each one of the site pages their language and country alternatives, for example:
-
Since you will be moving domains anyway, I'll directly migrate to the new .com site already using SSL, instead of splitting these two migrations by migrating to the .com first and then doing a migration towards the https version of the .com a few months after, the direct migration towards the https version will add maybe a bit more of complexity and additional validations to make, but since you're migrating anyway many of them you'd need to follow and do anyway.
-
Finally, be aware that after any change of a Web structure, specially from one domain to another (and if this other doesn't have a highly authoritative link profile yet) will always have a short-term negative effect, so is important that you start an SEO process not only to make sure you follow best practices when migrating but to validate afterwards and grow the new domains results based on what has been found on a technical, content and link profile audit and the desired results: Optimizing the new Web structure, Optimizing or creating content, optimizing or creating links, etc.
I hope this helps!
Thanks,
Aleyda
-
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
-
CcTLD vs subfolder for international SEO
In what situations is subfolder better than ccTLD, and vice versa.
International SEO | | MedicalSEOMarketing1 -
International SEO
Okay, so I have read through the following link in respect to International SEO (https://moz.com/learn/seo/international-seo), and I believe that the way forward it a ccTLD. My thought was to have .com, .co.uk and .eu. Currently my site is .com, but receives most of its traffic from UK sources. I'm concerned that when I switch over to ccTLDs, the .co.uk in particular, that my UK traffic could dry up. Switching from .com to .co.uk and then using the .com to target the US market makes sense, but I would like to know others opinions on the potential dangers of doing this. Also, are ccTLDs kept on the same hosting or would they require individual hosting? The link doesn't cover this question.
International SEO | | moon-boots1 -
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
If I redirect based on IP will Google still crawl my international sites if I implement Hreflang
We are setting up several international sites. Ideally, we wouldn't set up any redirects, but if we have to (for merchandising reasons etc) I'd like to assess what the next best option would be. A secondary option could be that we implement the redirects based on IP. However, Google then wouldn't be able to access the content for all the international sites (we're setting up 6 in total) and would only index the .com site. I'm wondering whether the Hreflang annotations would still allow Google to find the International sites? If not, that's a lot of content we are not fully benefiting from. Another option could be that we treat the Googlebot user agent differently, but this would probably be considered as cloaking by the G-Man. If there are any other options, please let me know.
International SEO | | Ben.JD0 -
What are the best practices for translation of city/state names for international SEO? (ie. New York in English vs. Nueva York in Spanish)
I'm working on international SEO / translation of a global travel site. While we have a global keyword research and translation strategy in process for each market they serve, I've run into a unique question. Overall, we are translating (and localizing) content for each market but aren't sure what to do with location names. Each country/state has cities and locations that have their own dedicated pages. I see three options for these location names (when titling a page and writing content): keep them in English, translate the names in the market languages, or use a combination of the two. The challenge with altering the location names to the market languages is that they are truly not known by those names. Though there are some instances where it may make sense…for instance **New York **in Spanish would be "Nueva York" with **‘**Nueva' being the Spanish translation of ‘new’. There are other instances, where no translation exists. If you’ve had a similar experience I'd love to hear your approach/recommendation.
International SEO | | JonClark150 -
International hreflang - will this handle duplicate content?
The title says it all - if i have duplicate content on my US and UK website, will adding the hreflang tag help google figure out that they are duplicate for a reason and avoid any penalties?
International SEO | | ALLee1 -
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