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
-
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 -
Is using JavaScript to render translations safe for International SEO?
Hello World! Background: I am evaluating a tool/service that a company wants to use for managing the translated versions of their international/multi-lingual websites: https://www.transifex.com/product/transifexlive/ Transifex is asking webmaster to "simply add a snippet of JavaScript" to their website(s); the approved translations are added by the business in the back-end; and the translated sites are made live with the click of a button (on/to the proper ccTLD, sub-domain, or sub-directory, which is specified). CONCERN: Even though I know Google reads JavaScript for crawling and ranking,
International SEO | | SixSpokeMedia64
I am concerned because I see the "English text" when I view the source-code on the "German site", and I wonder if this is really acceptable? QUESTION: Is a service like this (such as Transifex using JavaScript to render translations client-side) safe for indexing and ranking for my clients' international search engine visibility, especially via Google? Thank you!0 -
International SEO Question: Using hreflang tags across two different TLDs.
Hi! My UK based company just recently made the decision to let the US market operate their ecommerce business independently. Initially, both markets were operating off the same domain using sub-directories (i.e: www.brandname.com/en-us/ , www.brandname.com/en-gb/ ) Now that the US team have broken away from the domain - they are now using www.brandnameUSA.com while the UK continues to use www.brandname.com/en-gb/. The content is similar across both domains - however, the new US website has been able to consolidate several product variations onto single product pages where the UK website is using individual product pages for each variation. We have placed a geo-filter on the main domain which is 301 redirecting North American traffic looking for www.brandname.com to www.brandnameUSA.com However, since the domain change has taken place, product pages from the original domain are now indexing alongside the new US websites product pages in US search results. The UK website wants to be the default destination for all international traffic. My question is - how do we correctly setup hrlang tags across two separate TLDs and how do we handle a situation where multiple product pages on the "default" domain have been consolidated into one product page on the new USA domain? This is how we are currently handling it: "en-us" href="https://www.BRANDNAMEUSA.com/All-Variations" /> href="https://www.BRANDNAMEUSA.com/All-Variations" />
International SEO | | alexcbrands0 -
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 -
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 -
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 -
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