Welcome to the Q&A Forum

Hi Jerome, If your SaaS vendor allows it, you should use subfolders for the countries instead of subdomains. So www.example.com/uk instead of uk.example.com, for example. The reason for this is that the subdomains won't share link equity as effectively. You should implement hreflang -- Moz has a great introduction to the topic here -- on all equivalent pages (I'll explain what I mean by that in a second). By all means choose sensible default currency options (for example GBP should be the default currency in the /uk directory), but preferably do allow users to change that default value if they wish. If they do change it, do not direct them to a different URL. Use a cookie to store their currency preference. Now, more on 'equivalence'. The point of hreflang is so that you can have identical or very similar pages targeting different country/language combinations, and have Google discard these pages as duplicate content. The pages don't have to be completely identical. For example, Americans and Brits use different spellings for common words. If my product was online math(s) lessons, my two equivalent URLs may look like this: www.mystore.com/us/online-math-lessons www.mystore.com/uk/online-maths-lessons The language, tone, and general marketing pitch of each page may be different, and tailored to their respective audiences, but they're each fundamentally selling the same product. So I would add the following hreflang tags to these pages (both tags on both pages): Be careful to use the correct country codes: en-UK is not valid, for instance, but en-GB is. Read Google's guidelines on the topic.