Multi National Company that Doesn't Want to Implement International SEO
-
I have got an interesting situation where I have a client who wants to merge two ccTLD's into one. They currently have .fi and .com and they want to merge both sites to .com
.fi is for finland and .com for USA.
They want to merge the sites and the original plan was to use subfolders for each country and pair with hreflang.
However the team now wants to merge both sites with NO subfolders differentiating between finland or the US.
My understanding of International SEO that this is the most opposite from best practices, but is there any specific reasons why they wouldn't want to do this?
I'm struggling to find any specific reasons that I can cite to the client that would argue why we should at least do a subfolder or some sort of international seo strategy.
-
@webuniversalp1 Yes, hreflang tags need to be created for each page "appropriately" as covered in my previous response to help search engines show the right version page to the right geo/audience.
-
El tema es que vas a tener que redireccionar las dos webs, no sé si mantendrás el contenido de la .com pero si no te espera un auditoria grande dependiendo de la web, en cuanto a lo que dicen en los anteriores sobre hreflang pienso lo mismo.
-
@naeemgari Hello,
You need to use the hreflang tags for each page, with this Google will not penalize your content and will understand that they are two versions with different languages.
-
@naeemgari I agree with that.
-
Hello,
You need to use the hreflang tags for each page, with this Google will not penalize your content and will understand that they are two versions with different languages.
-
@jkhoo for international SEO the strongest signal for search engines is ccTLDs. The next best option would be a sub-folder URL structure with the correct hreflang tag declarations.
For your core keywords is there low / no search volume in Finland? From a business standpoint, managing two websites can be tedious. You need to build content & backlinks for two domains.
However, from an SEO standpoint, the preferred option would be to keep the ccTLDs. They are the best indicator of relevance to local SERPs. Think about your audience in Finland are they likely to visit a .com domain from SERPs or a .fi domain? Search engines would also prefer showing more targeted and relevant results to users. Therefore, ccTLDs for target regions and international SEO are the best options.
The next best route would be sub folders with appropriate hreflang tag declarations & xml sitemaps.
Additionally, site mergers/migrations generally result in a loss in organic traffic and visibility which can range from a quarter to over year(s).
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
-
SiteName Attribute Showing in Different Language in SERP
We are currently experiencing issues with our subdomain SiteName. Our parent company root domain is a Japanese language site, but we have an English subdomain that is for the United States primarily, and nearly rest of world for organic traffic. Our issue is that we have followed the guidelines here: https://developers.google.com/search/docs/appearance/site-names There was a large post on here with many responses including Googlers with issues others were having, but it has since been removed. Here is the code in place on our homepage: <script
Technical SEO | | Evan_Wright
type="application/ld+json"> { "@context": "https://schema.org",
"@type": "WebSite",
"name": "Mescius Developer Tools",
"alternateName": ["Mescius, inc.", "developer.mescius.com"],
"url": "https://developer.mescius.com" }
</script> Unfortunately this is what is appearing in the SERP. It is using the Japanese equivalent of our parent company. Screenshot 2024-02-23 at 3.37.55 PM.png Even though the relationship between root and subdomain should not be causing this, it seems like something is impacting this incorrect SiteName, and it is impacting CTR for the subdomain. Has anyone else experienced this and found a fix?0 -
Moving from single domain to multiple CCTLDs
Hi, I have a website targeting 3 markets (and therefor 3 languages). I was currently using a single domain with each market being targeted in the following format: www.website.com/pl
International SEO | | cellydy
www.website.com/de
www.website.com/hu It's clear to me by looking at organic results, that in my industry (Real Estate) Google is putting a large emphasis on local businesses and local domains. Top 10 organic results for all my keywords in all markets have country specific CCTLDs. I decided to migrate from a single domain strategy to a multi domain strategy. I own the domains. The new structure is www.website.com/pl -> www.website.pl
www.website.com/de -> www.website.de
www.website.com/hu -> www.website.hu All the website have been added to google search console and 301 redirects are in place and working correctly. The pages are all interlinked and have rel=alternate to each other. The sitemaps are all done correctly. My question is how do I tell Google about this. The change of address feature only works for changing one domain to one other domain. It's been a week and the old www.website.com domain is still showing up (even considering 301 redirects). Or do I just need to be patient and wait it out? Any tips?0 -
Is it worth maintaining multiple international websites
Hi I work for a British company which has two well established websites - a .co.Uk for the UK, and a .com for the US and rest of the world (in language directories). The Uk site is hosted in the Uk, the .com in US. The websites do reasonable well in Google on both sides of the Atlantic. The company is a small but quite well known brand. The company is now thinking of redirecting the .co.Uk to the .com as it would be cheaper to maintain. What would you advise? Thanks.
International SEO | | fdl4712_aol.com2 -
Google not detecting Hreflang
Hey everybody, We recently migrated our .co.uk to .com/en. Google for some reason is saying that the .com/en version has no hfrelang tags - even though they are clearly there and have had the same implementation as other language versions of the website. We also did a previous migration 6 months ago for the german version of our website and no hreflang problems there. We add our hreflang tags to our sitemap - which you can find here:
Technical SEO | | mooj
https://camaloon.com/en/web-sitemap.xml Any help or suggestions would be greatly appreciated!! Thanks 🙏0 -
Multi Regional Website Best Practices
Hi there, I have a website that is targeting 3 countries AU/US & NZ. I have set up hreflang tags for each page on each of the site however I am having difficulties getting it work right. I read this article which was a great insight into the hreflang tags. https://mza.seotoolninja.com/blog/hreflang-behaviour-insights and as a result I have implemented hreflang tags in the following manner: When users access the root domain http://[website] it will redirect the user to their locale with a 302 redirect. I have a few questions:
International SEO | | nathanfranklin
1. When building my external link profiles, I'm not sure if I should be building link profiles for http://[website]/ or for the geo graphical pages (http://[website]/aus/ etc..). Note that the http://[website]/ is never used, it just issues a 302 to the actual geographical location. 2. It seems that the hreflang tags are not working correctly. Perhaps its the result of the 302 on the root page, but in google.com.au (using the link http://www.google.com.au/search?hl=en&gl=au&pws=0&q=[branded search]) I would expect that I should see the search results for /aus/ given the fact that the hreflang tags are setup as en-au. Instead I am seeing the root domain page. Is that correct or should it be showing all the pages with /aus/. ALSO If I do a search in google thailand (http://www.google.com.au/search?hl=en&gl=th&pws=0&q=[branded search]) it returns the /aus/ version where it should be showing the /us/ using the x-default hreflang tag. In google webmaster tools I have setup 4 site profiles:
http://[website]/
http://[website]/us/
http://[website]/aus/ (Targeted to Australia)
http://[website]/nz/ (Targeted to New Zealand) Any help would be appreciated. Thanks Nathan1 -
I need suggestions. We're helping a big journal to improve their external links, even though they've a site with over 10 million monthly visits, their external links are week. Any suggestions?
Please let us know where we can find information on how to improve external links for a very big journal site. Thanks.
International SEO | | carloscontinua0 -
Multi-lingual SEO: Country-specific TLD's, or migration to a huge .com site?
Dear SEOmoz team, I’m an in-house SEO looking after a number of sites in a competitive vertical. Right now we have our core example.com site translated into over thirty different languages, with each one sitting on its own country-specific TLD (so example.de, example.jp, example.es, example.co.kr etc…). Though we’re using a template system so that changes to the .com domain propagate across all languages, over the years things have become more complex in quite a few areas. For example, the level of analytics script hacks and filters we have created in order to channel users through to each language profile is now bordering on the epic. For a number of reasons we’ve recently been discussing the cost/benefit of migrating all of these languages into the single example.com domain. On first look this would appear to simplify things greatly; however I’m nervous about what effect this would have on our organic SE traffic. All these separate sites have cumulatively received years of on/off-site work, and even if we went through the process of setting up page-for-page redirects to their new home on example.com, I would hate to lose all this hard-work (and business) if we saw our rankings tank as a result of the move. So I guess the question is, for an international business such as ours, which is the optimal site structure in the eyes of the search engines; Local sites on local TLD’s, or one mammoth site with language identifiers in the URL path (or subdomains)? Is Google still so reliant on TLD for geo targeting search results, or is it less of a factor in today’s search engine environment? Cheers!
International SEO | | linklater0