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
-
Setting up international site subdirectories in GSC as separate properties for better geotargeting?
My client has an international website with a subdirectory structure for each country and language version - eg. /en-US. At present, there is a single property set up for the domain in Google Search Console but there are currently various geotargeting issues I’m trying to correct with hreflang tags. My question is, is it still recommended practise and helpful to add each international subdirectory to Google Search Console as an individual property to help with correct language and region tagging? I know there used to be properly sets for this but haven’t found any up to date guidance on whether setting up all the different versions as their own properties might help with targeting. Many thanks in advance!
International SEO | | MMcCalden0 -
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 -
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 -
Direct traffic is up 2100% (due to a bot/crawler I believe)
Hi, The direct traffic to website www.webgain.dk has increased by over 2100% recently. I can see that most of it is from US (my target audience is in Denmark and the website is in danish).
International SEO | | WebGain
What can I do about this? All this traffic gives my website a bounce rate of 99.91% for direct traffic. I believe it is some sort of bot/crawler. 2100percentboost.png0 -
How to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries?
Dear all, what is the best way to fix the duplicate content problem on different domains (.nl /.be) of your brand's websites in multiple countries? What must I add to my code of websites my .nl domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? What must I add to my code of websites my .be domain to avoid duplicate content and to keep the .nl website out of google.be, but still well-indexed in google.nl? Thanks in advance!
International SEO | | HMK-NL3 -
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 -
SEO for Subdomains for different languages .com/fr, .com/es
Hi All, I was wondering how best to to approach optimisation of a site that exists on a single .com domain, but has different subfolders for different languages. The site is a .com and it has subfolders for French, Spanish, Russian and English. The business is situated in France and the vast majority of clients are French and English speakers. I've read that it's possible to geo target these subfolders using webmaster tools however I believe this is an inferior method of optimisation than having tld's. Just wondered if anyone had experience of htis and could provide any advice ? As they won't be rebuilding the site for another year or so I wondered if there were any quick wins? My second question is to do with how best to set these campaigns up within SEO Moz. would it be better to track at a subdomain or subfolder leverl (for different languages)? If someone could advise I would greatly appreciate it! Thanks, vantresca
International SEO | | vanvallejo0