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
-
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 -
Should Hreflang x-default be on every page of every country for an International company?
UPDATED 4/29/2019 4:33 PM I had made to many copy and pastes. Product pages are corrected Upon researching the hreflang x-default tag, I am getting some muddy results for implementation on an international company site older results say just homepage or the country selector but…. My Question/Direction going forward for the International Site I am working on: I believe I can to put x-default all the pages of every country and point it to the default language page for areas that are not covered with our current sites. Is this correct? From my internet reading, the x-default on every page is not truly necessary for Google but it will be valid implemented. My current site setup example:
International SEO | | gravymatt-se
https://www.bluewidgets.com Redirects to https://www.bluewidgets.com/us/en (functions as US/Global) Example Countries w/ code Site:- 4 countries/directories US/Global, France, Spain Would the code sample below be correct? https://www.bluewidgets.com/us/en/ (functions as US/Global) US/Global Country Homepage - https://www.bluewidgets.com/us/en/ US/Global Country Product Page(s) This would be for all products - https://www.bluewidgets.com/us/en/whizzer-5001/ http://www.bluewidgets.com/us/en (functions for France) France Country Homepage - https://www.bluewidgets.com/fr/fr/ France Country Product Page(s) This would be for all products- https://www.bluewidgets.com/es/es/whizzer-5001 http://www.bluewidgets.com/us/en (functions as Spain) Spain Country Homepage - https://www.bluewidgets.com/es/es/ Spain Country Product Page(s) This would be for all products - https://www.bluewidgets.com/es/es/whizzer-5001 Thanks for the spot check Gravy0 -
International URL paths
Wanted to ask everyone a questions: So our company is going to be doing a website that is going to be full of videos. The url path will be country.domain.com/language/slug/content-id. We redirect the user when they go to the different country. So if you're in spain on a train to france your URL will change from es.domain.com/es/slug/content-id to fr.domain.com/es/slug/content-id. Each country can listen to each video in all languages. My question is with hreflang tags and canonicals. Aside from targeting users in a certain country via Google Search Console, how do I eliminate duplication and tell Google which I'd like to show up via which country. In spain I would like es.domain.com/es/slug/content-id to show in Google and would have hreflang tags on each of the es.domain pages but what about fr.domain.com/es/slug/content-id since it would show the same content? I can't canonical to one of them since I need them to show in their respective country. How do I show the difference in language and country without showing duplication?
International SEO | | mattdinbrooklyn0 -
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 -
Redirect the main site to keyword-rich subfolder / specific page for SEO
Hi, I have two questions. Question 1: is it worthwhile to redirect the main site to keyword-rich subfolder / specific page for SEO? For example, my company's webpage is www.example.com. Would it make sense to redirect (301) the main site to address www.example.com/service-one-in-certain-city ? I am asking this as I have learned that it is important for SEO to have keywords in the URL, and I was thinking that we could do this and include the most important keywords to the subfolder / specific URL. What are the pros and cons of this? Should I create folders or pages just the sake of keywords? Question 2: Most companies have their main URL shown as www.example.com when you access their domain. However, some multi-language sites show e.g. www.example.com/en or www.example.com/en/main when you type the domain to your web browser to access the site. I understand that this is a common practice to use subdomains or folders to separate different language versions. My question is regarding subfolders. Is it better to have only the subfolder shown (www.example.com/en) or should I also include the specific page's URL after the subfolder with keywords (www.example.com/en/main or www.example.com/en/service-one-in-certain-city)? I don't really understand why some companies show only the subfolder of a specific language page and some the page's URL after the subfolder. Thanks in advance, Sam
International SEO | | Awaraman1 -
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 -
Google Webmaster Tools - International SEO Geo-Targeting site with Worldwide rankings
I have a client who already has rankings in the US & internationally. The site is broken down like this: url.com (main site with USA & International Rankings) url.com/de url.com/de-english url.com/ng url.com/au url.com/ch url.com/ch-french url.com/etc Each folder has it's own sitmap & relative content for it's respective country. I am reading in google webmaster tools > site config > settings, the option under 'Learn More': "If you don't want your site associated with any location, select Unlisted." If I want to keep my client's international rankings the way it currently is on url.com, do NOT geo target to United States? So I select unlisted, right? Would I use geo targeting on the url.com/de, url.com/de-english, url.com/ng, url.com/au and so on?
International SEO | | Francisco_Meza0