On our website, we list businesses such as restaurants. So there are restaurants in USA and say, Mexico. The restaurants in Mexico could be American chains as well.

So what's the best way to handle this separation?

Is there a problem if both live on same domain, just different page name? i.e.

American Restaurant = /american-restaurant

Mexican Restaurant = /mexican-restaurant

American Restaurant in Mexico = /american-restaurant-mx

Or should they be separated by directories?

American Restaurant = /american-restaurant

Mexican Restaurant = /mx/mexican-restaurant

American Restaurant in Mexico = /mx/american-restaurant-mx

Or does it make most sense if other countries are just on a separate subdomain? This means authority and such would not easily pass over from main domain though.

American Restaurant = www.domain.com/american-restaurant

Mexican Restaurant = mx.domain.com/mexican-restaurant

American Restaurant in Mexico = mx.domain.com/american-restaurant-mx

My favorite is the subdomain idea, but I'm worried about how hard it might be to get it ranked since you basically start with 0 authority all over.

  • What is the best way to handle this separation for SEO purposes? Or for UX/UI? I'd say that the best thing to do is to have all of the places in one website and organize the content in subfolders. This will for example allow you to have breadcrumbs and google (and other SE) will understand how you content is organized. For example : Your Website > Countries > States/Regions > Restaurants. As a user I think it makes sense to have it like that and this allows you user to go back one level and say, "oh let me look at the restaurants in California"...
    – EdouardF
    Oct 3 '19 at 16:10
  • @EdouardF well ideally both. Google does say best UX is best for SEO, even though we know subdomains will most likely be worse for SEO in the short term. I'm just trying to see where people stand and which one is preferable.
    – zen
    Oct 3 '19 at 16:13
  • @EdouardF if you used sub directories, would you also translate pages that are aimed at other countries. i.e. /mx/* would be in Spanish? To me it seems weird to keep multiple countries/languages on same domain since it means each audience can easily jump to another language/section without much effort.
    – zen
    Oct 3 '19 at 16:16
  • 1
    Bingo! You are absolutely right. I was not explicit, but that is what I meant.
    – closetnoc
    Oct 3 '19 at 17:48
  • 1
    I think in my case, since I'm mainly targeting countries, I might just stick with sub directories. i.e. domain.com/mx. This avoids having multiple languages/country combinations and subdomains/sub-directories as it would be hard to manage.
    – zen
    Oct 3 '19 at 18:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.