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 -
Tracking International Keywords
Hi I haven't had much luck tracking keywords on my international sites let alone discovering new keywords. What are some strategies/suggestions to accomplishing this? Currently I have campaigns set-up for the UK, Germany, France, and China in additional to our main US-Canada campaign.
International SEO | | Julie.P0 -
Question regarding international SEO
Hi there, I have a question regarding international SEO and the APAC region in particular. We currently have a website extension .com and offer our content in English. However, we notice that our website hardly ranks in Google in the APAC region, while one of the main languages in that region is also English. I figure one way would be to set up .com/sg/ (or .com/au/ or .com/nz/), but then the content would still be in English. So wouldn't that be counted as duplicate content? Does anyone have experience in improving website rankings for various English-speaking countries, without creating duplicate content? Thanks in advance for your help!
International SEO | | Billywig0 -
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 -
How to make Google consider my international subdomain relevant?
We have recently started to look deeper into international SEO. We have search engine optimized our international landing pages, title tags and meta descriptions with keywords etc. so each of the international language we support is SEO'ed for the local market. We support 12 languages, and each of them are located on a subdomain. That means if we say our site is helloworld.com, a person from Germany that lands on this site can switch to German and will then be redirected to de.helloworld.com and all content will be in German. Our problem is that we develop cloud-based software, we have a significant amount of traffic, but whenever we get media coverage or people link to us from anywhere in the world they always link to the root domain which in this case then would be helloworld.com. That means if I go to google.de and type in the exact meta description or title tag we use in German, the Google search engine can't even find us because "I assume" Google don't consider our de.helloworld.com relevant because nobody has ever linked to this site. I would appreciate very much if anyone can give me some advice on how I can address this issue. Thanks a lot! Allan
International SEO | | Todoist0 -
Multi Regional website - Folder strategy
Hello Seomoz people ! I've been struggling for some time now with an international website project. It's gonna be an:international website with joomla. To sum up: We have an international company The company has 13 subsidiaries worldwide (same products, different names) The company doesn't have enough resources to get 13 independent websites Some subsidiaries work in one country / one language, some others on a region (several countries, several languages) Thanks to your community we decided to: Get a main website company.com Get subsidiaries folders (middle east, oceania and south america will be easier to link to their subsidiary) .com/asia .com/middle-east .com/oceania .com/south-america .com/uk .com/usa .com/fr .com/es .com/de .com/ma .com/dz .com/it We also need to: Get some websites in different languages .com/asia-cn .com/asia-en etc. Now how do we do to manage: Regional websites (the first 4th on the upper list) Google allows to affect a website to a country not region Will they compete with the .com ? How do we set up them for google ? How do we avoid duplicate content and keep local ranking .com/asia-en/services1.html will have the exact same content that_.com/services1.html_ If we use canonical from _.com/asia-en/services1.htm_l to _.com/services1.html , d_oes that mean /asia will not rank in asia ? Hope you can help us to figure us the best solution for this good project ! Thanks a lot. Florian
International SEO | | AymanH1 -
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 -
Does hosting content for one country in another country negatively affect its SEO ranking?
Hi, my content is primarily for Australian audiences, however due to a general lack of competitive hosting infrastructure, I tend to host a lot of content in the US. A 2007 article I read implied that it's not a good idea - does anyone have a definitive 2011 answer? Cheers, Jez
International SEO | | jez0000