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 SEO Subfolders / user journey etc
-
Hi
According to all the resources i can find on Moz and elsewhere re int seo, say in the context of having duplicate versions of US & UK site, its best to have subfolders i.e.
&
however when it comes to the user journey and promoting web address seems a bit weird to say visit us at: domain.com/en-us/ !?
And what happens if someone just enters in domain.com from the US or UK ?
My client wants to use an IP sniffer but i've read thats bad practice and should employ above style country/language code instead, but i'm confused about both the user journey and experience in the case of multiple sub folders.
Any advice much appreciated ?
Cheers
Dan
-
Thanks for your comments but im looking directly into subfolder option (since TLD not an option and sub-domain considered bad practice from what i can gather after many days research on Moz etc
As a result this is what ill issue to a clients development team in this circumstance is as follows for where sites preferred structure is sub-folders/directories:
-
Implement IP sniffing on the home page ONLY
-
Then have Sub-Folders named after the official country abbreviations which will create a better user experience than both country and language i.e. domain.com/us/ as opposed to domain.com/en-us/ or domain.com/en-gb/ etc etc. This way it will only manipulate the homepage crawling and not site-wide indexing issues.
3) Target these folders to the correct countries in Google’s and Bing’s Webmasters Tools. Use the official country and language codes in the Hreflang mark-up as per point 4.
-
Set up site maps for each subfolder and rel="alternate" hreflang= according to Google guidelines. Here's a great tool to help with correct implementation: http://www.themediaflow.com/resources/tools/href-lang-tool/
-
Specify the content language/country by adding the 'country-language' meta-tags in the html head
6) Link between each country/language version in a crawl-able and visible manner (for SE and Users)
7) Create individual profiles in GWT & Bing Webmaster Tools for each country/language sub-folder and geo-target accordingly
Create individual profiles within GAnalytics for each country/language version and configure to track internal activity between different versions
9) Localise content so has US currency, contact details, spelling etc
10) Other localisation techniques ( such as marking up contact details with schema places code)
Note RE: HrefLang & Canonicalisation:
An extra advantage of using hreflang is that it will provide a degree of canonicalisation. Should canonical tag be employed in the future never so across language versions if site expand into non English versions. More info here: http://www.youtube.com/watch?v=Igbrm1z_7Hk
-
-
Hey Dan,
The challenges with international sites are many and varied. The 'best' international strategy really depends on your resources
Here's how I see the advantages / disadvantages of each approach:
Subfolders - ranking may be 'easier' as domain authority is consolidated, but URLs are ugly
The sub-folder approach is often utilised where there's insufficient resource to market and maintain separate international ccTLDs (e.g. .co.uk, .com, .fr etc). The advantage with the subfolder approach is that you're consolidating domain authority - so the links to /en-uk/ (NB do use en-uk NOT en-gb incidentally) pass authority to /en-us/ and vice versa.
You're building one strong site, rather than trying to build two, three (or more) strong sites. However, as you've identified URLs get long and a bit ugly.
ccTLDs - Arguably nicer for users, but might not rank
Conversely, whilst ccTLDs (.co.uk, .com, .fr etc) are nicer from a user's perspective, you may struggle to rank if you're not able to spend sufficient time and resource on marketing and building links to these domains.
If you have the time and resources, I'd probably go down the ccTLD route, but if you don't, then the subfolder route is probably best.
IP redirects
In terms of the IP sniffers etc - be careful
Googlebot typical crawls from the US, and as such is likely to be redirected by your sniffer too. Essentially you're in danger of making any non-US versions invisible as far as Google are concerned. For that reason rather than doing a hard redirect I prefer Amazon's approach - if you visit Amazon.com from a UK IP you'll see a message which says: "Shopping from the UK? Visit Amazon.co.uk.".
That way users get the nudge to direct them to the right site and the bots can still crawl and index all of your content.
-
I want to start by saying I am not a user experience expert! I can tell you that from an SEO perspective, building international sites with subfolders can be advantageous because those international sites will inherit the main domain's authority and you can have one linking strategy that can benefit all areas of the site.
As for the user journey, I can provide some ideas for what we've done in the past with our clients. The first would be to have a window display on the main domain.com page that will allow a user to choose their country, and that will then forward them to the appropriate area of the site.
Another tactic we used was to purchase domain names that are unique for each country/language that would then redirect to the appropriate area of the site. We would typically only use these domains in offline marketing material (brochures, business cards etc..) and that way you can tell your prospective customers to visit you at domainuk.com instead of domain.com/en-gb/.
I hope this helps!
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 - how likely is it autoredirect via IP Address will impact rankings?
Hello, We're looking to internationalise our site so that US visitors will see the US branded version while everyone else will see the global version (currently at .com). This question specifically is about location-based auto-redirects. The literature I've read (including Google) recommends against auto-redirection: "Avoid automatic redirection based on the user’s perceived language. These redirections could prevent users (and search engines) from viewing all the versions of your site." Insofar as I understand it the theory goes as follows. Google crawls mainly from the US Auto-redirecting by US IP to the US domain will also redirect the Googlebot crawlers Because of this the crawlers will only see the US site / domain and not original .com website Crawlers can't index what they can't see Drop in rankings for the original site However, one of my colleagues has pointed out to me a company which does use auto-redirects. If a user is in the UK and type in their website they will be redirected to the UK version of the site, US will be US etc. I have checked their rankings and they are still ranking highly for relevant terms. I have been asked why they have been able to do this without impacting their visibility. Any ideas? Given their success have the risks of auto-redirecting have been overstated? How can we ensure US visitors land on the correct internationalised domain without auto-redirects in place? Looking forward to your thoughts on this as well as your experiences. Thanks in advance!
International SEO | | SEOCT0 -
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 -
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 -
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.
International SEO | | ThomasHarvey0 -
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 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
Subdomains or subfolders for language specific sites?
We're launching an .org.hk site with English and Traditional Chinese variants. As the local population speaks both languages we would prefer not to have separate domains and are deciding between subdomains and subfolders. We're aware of the reasons behind generally preferring folders, but many people, including moz.com, suggest preferring subfolders to subdomains with the notable exception of language-specific sites. Does this mean subdomains should be preferred for language specific sites, or just that they are okay? I can't find any rationale to this other than administrative simplification (e.g. easier to set up different analytics / hosting), which in our case is not an issue. Can anyone point me in the right direction?
International SEO | | SOS_Children0 -
Redirecting users based on location
My site is available in EN, DE, SW, SP, FR, IT, CH and JP. However, the EN sites ranks much better than the other languages, and even when searching in another language the EN homepage is normally the result that appears. Would it be worthwhile to automatically redirect users to the site in the same language they are searching in or country they are searching from? If so, how do I go about this? Thanks!
International SEO | | theLotter0