What's the best homepage experince for an international site?
-
Greeting Mozzers.
I have a question for the community, which I would appreciate your input on.
If you have a single gTLD that services multiple countires, what do you think is the best homepage UX for the root homepage and why?
So the example would be you own website www.company.org and target content to Germany, Japan and Australia with content through the folder structure eg. www.company.org/de-de
If someone comes to the www.company.org from a region, would you:
- Redirect them based on location IP – so if from Germany they land on www.company.org/de-de
- Let them land on the homepage which offers location selection
- Let them land on a page with content and offer location selection eg. pop-up or obvious selection box
- Something I’ve not thought of…
I'd appreciate your input.
Thanks
-
Hello Robert,
This is a question many businesses struggle with, as you might imagine. There really is no "perfect" solution for every situation so I won't try to speak in best practices other than to say don't annoy the user. If I'm trying to get to your .com home page but I just happen to be travelling in Germany for business an automatic redirect to the German page would drive me nuts.
If it were my site I'd probably take the third option. Specifically, I'd sniff out the geolocation based on their IP address and serve a custom pop-up in the language of that country offering something like "Would you like to see the [Country-Language] version"?
If I'm in Germany and land on the English default ".com" page I will not be surprised or frustrated by a pop-up or a custom message on the page asking "Möchten Sie die deutsche Version zu sehen?". I'd probably just X-out of it and move on.
That's pretty much what this site does when I view from a US location: https://www.gsport.no/herre/klaer/bukse-shorts .
It asks me, in English, if I want to translate to English, and offers two clear options along with a third x-out option. Or I could ignore it because it's pretty unobtrusive on desktop.
No matter which approach you choose, be sure to research best practices on using attributes and tags like rel="alternate" hreflang="x" and rel="canonical".
I'll leave this question open for discussion since there are many potential approaches that might answer your question.
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
-
International SEO & redirects - do these solutions make sense?
I’m currently working on SEO for an international website with subdirectories set up for each international version. The site is has never had any SEO previously and is having a lot of indexing and visibility issues. Also geotargeting seems very off in search results. I’ve diagnosed various issues and want to check my assumptions and solutions below make sense... The root domain uses a 302 redirect to display content from the /en-GB page. (302 redirects seem to be a default language fallback setting configured in the CMS) and they’re used for most key pages. I’m concerned these redirects are contributing to a lot of the issues with incorrect indexing. The en-GB is the default language version of the site. So far, the en-GB has been set as the canonical version too. Both the root domain and this subdirectory URL display the same content. (en-US is also a near duplicate page). All other international homepages appear only on their subfolder URL. Various SEO tools have been showing redirect loops (caused by language changing parameter versions of URLs being crawled that don’t have redirects on them) and issues with hreflang and canonicals. I believe the hreflang tags and canonicals have been ignored due to relative URLs being used for each, as search results don’t always contain the desired versions of the URLs (in terms of regional version and preferred canonical versions). My questions are: Could these 302 redirects be conflicting with hreflang tags? If so, I’m thinking they should be removed (if not made 301s). GSC doesn’t like the fact these are on key pages, as redirected pages are listed in the sitemap. Will changing hreflang tags and canonical tags to absolute URLs possibly be enough to fix these issues from what you can tell? (Or will redirects need to go too?) Is the en-GB correctly set as the canonical when the root domain is also accessible, indexed and using this page’s content within the CMS too? (I feel like the root domain should be the canonical version, but not sure that works together with other language version subfolders or with a redirect in place from root to subfolder). As an extra point to the last question, GSC has recently chosen the root domain as the canonical (despite en-GB being set as user preference) and is now choosing to deindex some international versions of the homepage as a result. Hoping that getting the hreflang tags fixed and possibly redirects removed should correct this ASAP. But perhaps this also confirms en-GB should be the canonical and marked X-default too. I hope that all makes sense and sorry it’s a small collection of related questions. Really appreciate any replies.
International SEO | | MMcCalden0 -
International Sites and Duplicate Content
Hello, I am working on a project where have some doubts regarding the structure of international sites and multi languages.Website is in the fashion industry. I think is a common problem for this industry. Website is translated in 5 languages and sell in 21 countries. As you can imagine this create a huge number of urls, so much that with ScreamingFrog I cant even complete the crawling. Perhaps the UK site is visible in all those versions http://www.MyDomain.com/en/GB/ http://www.MyDomain.com/it/GB/ http://www.MyDomain.com/fr/GB/ http://www.MyDomain.com/de/GB/ http://www.MyDomain.com/es/GB/ Obviously for SEO only the first version is important One other example, the French site is available in 5 languages and again... http://www.MyDomain.com/fr/FR/ http://www.MyDomain.com/en/FR/ http://www.MyDomain.com/it/FR/ http://www.MyDomain.com/de/FR/ http://www.MyDomain.com/es/FR/ And so on...this is creating 3 issues mainly: Endless crawling - with crawlers not focusing on most important pages Duplication of content Wrong GEO urls ranking in Google I have already implemented href lang but didn't noticed any improvements. Therefore my question is Should I exclude with "robots.txt" and "no index" the non appropriate targeting? Perhaps for UK leave crawable just English version i.e. http://www.MyDomain.com/en/GB/, for France just the French version http://www.MyDomain.com/fr/FR/ and so on What I would like to get doing this is to have the crawlers more focused on the important SEO pages, avoid content duplication and wrong urls rankings on local Google Please comment
International SEO | | guidoampollini0 -
How to best set up international XML site map?
Hi everyone, I've been searching about a problem, but haven't been able to find an answer. We would like to generate a XML site map for an international web shop. This shop has one domain for Dutch visitors (.nl) and another domain for visitors of other countries (Germany, France, Belgium etc.) (.com). The website on the 2 domains looks the same, has the same template and same pages, but as it is targeted to other countries, the pages are in different languages and the urls are also in different languages (see example below for a category bags). Example Netherlands:
International SEO | | DocdataCommerce
Dutch domain: www.client.nl
Example Dutch bags category page: www.client.nl/tassen Example France:
International domain: www.client.com
Example French bags category page: www.client.com/sacs When a visitor is on the Dutch domain (.nl) which shows the Dutch content, he can switch country to for example France in the country switch and then gets redirected to the other, international .com domain. Also the other way round. Now we want to generate a XML sitemap for these 2 domains. As it is the same site, but on 2 domains, development wants to make 1 sitemap, where we take the Dutch version with Dutch domain as basis and in the alternates we specify the other language versions on the other domain (see example below). <loc>http://www.client.nl/tassen</loc>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="http://www.client.com/sacs"
/></xhtml:link<br> Is this the best way to do this? Or would we need to make 2 site maps, as it are 2 domains?0 -
International SEO question domain.com vs domain.com/us/ , domain.com/uk etc.
Hi Mozzers, I am expanding a website internationally. I own the .com for the domain. I need to accommodate multiple countries and I'm not sure if I should build a folder for /us/ for United States or just have the root domain .com OPTION 1:
International SEO | | jeremycabral
domain.com/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan OPTION 2:
domain.com/us/page-url -- United States
domain.com/de/page-url -- Denmark
domain.com/jp/page-url -- Japan My concern with option 2 is there will be some dilution and we wouldn't get the full benefit of inbound links compared to Option 1 as we would have geo ip redirection in place to redirect users etc. to the relative sub-folder. Which option is better from an SEO perspective? Cheers, Jeremy0 -
International advice.... can anyone help and check my site?
Hi ALL, I'm running 3 sites, internationally .com, com.au and co.nz Can anyone please look at my site and give me feedback about the hreflang tags, I ran a W3C and i have errors stating https://validator.nu/?doc=http%3A%2F%2Fzenory.co.nz for www.zenory.com and its relevant domains
International SEO | | edward-may0 -
Ranking in Different Countries - Ecommerce site
My client has a .com ecommere site with UK-based serves and he wants to target two other countries (both English speaking). By the looks of it, he wouldn't want to create separate local TLDs targeting each country, I therefore wanted to suggest adding subdomains / subfolders geo-targeted to each country that they want to target, however, I'm worried that this will cause duplicate content issues... What do you think would be the best solution? Any advice would be greatly appreciated! Thank you!
International SEO | | ramarketing0 -
B2B International Subdirectory - How Unique is Unique?
With the power to upload unique xml sitemaps for a subdirectory targeting the UK, geo-target the UK in WebmasterTools, and the ability to adjust content to adhere to en-gb standards, would it still be essential for a site to re-write all of it's content if it wanted to rank well or could we just use the same content as our en-us pages with the dialect changes and other tools mentioned above? Not interested in unique TLDs or subdomains.
International SEO | | SEOPPCDP0 -
Ranking well internationally, usage of hreflang, duplicate country content
I'm trying to wrap my head around various options when it comes to international SEO, specifically how to rank well in countries that share a language, and the risk of duplicate content in these cases. We have a chance to start from scratch because we're switching to a new e-commerce platform, and we were looking into using hreflang. Let's assume an example of a .com webshop that targets both Austria and Germany. One option is to include both language and region in the URL, and mark these as such using hreflang: webshop.com/de-de/german-language-content (with hreflang de-de)
International SEO | | DocdataCommerce
webshop.com/de-at/german-language-content (with hreflang de-at) Another option would be to only include the language in the URL, not the region, and let Google figure out the rest: webshop.com/de/german-language-content (with hreflang de) Which would be better? The risk of inserting a country, of course, is that you're introducing duplicate content, especially since for webshops there are usually only minor differences in content (pricing, currency, a word here and there). If hreflang is an effective means to make sure that visitors from each country get the correct URL from the search engines, I don't see any reason not to use this way. But if search engines get it wrong, users will end up in the wrong page and will have to switch country, which could result in conversion loss. Also, if you only use language in the URL, is it useful at all to use hreflang? Aren't engines perfectly able to recognize language already? I don't mention ccTLDs here because most of the time we're required to use a .com domain owned by our customer. But if we did, would that be much better? And would it still be useful to use hreflang then? webshop.de/german-language-content (with hreflang de-de)
webshop.at/german-language-content (with hreflang de-at) Michel Hendriks
Docdata Commerce0