Thanks for the feedback Ryan. I may not have been very clear in my response - I know I was bouncing all over the place. usa cannot be my base URL for scalability reasons. Slowly we'll start adopting other countries websites so the top-level subdirectory needs to be broad enough to not restrict us to a specific part of the world.

My intitial thought is to opt for something like website.com/M/us-en or website.com/-/us-en where the base directory is short in hopes that it doesn't dilute the value of SEO terms later in the URL such as website.com/M/us-en/store/product-name.html. Is that something to worry about?

I've been pushing hard to get our Americas site (DA 34) integrated with our higher domain authority (DA 51) international website. Currently our international website is setup in the following format...

• website.com/us-en/
• website.com/fr-fr/
• etc...

The problem that I am facing is that I need my development framework installed in it's own directory. It cannot be at the root of the website (website.com) since that is where the other websites (us-en, fr-fr, etc.) are being generated from. Though we will have control of /us-en/ after the integration I cannot use that as the website main directory since the americas website is going to be designed for scalability (eventually adopting all regions and languages) so it cannot be region specific. What we're looking at is website.com/[base]/us-en. I'm afraid that if base has any length to it in terms of characters it is going to dilute the SEO value of whatever comes after it in the URL (website.com/[base]/us-en/store/product-name.html).

Any recommendations?

Tim, I have implemented product and recipe schema previously. So, it seems that I may have nothing to worry about on this front.

You're correct, we do currently link to products included in our recipes. I suppose you put me at ease though as I do not know enough about SEO to determine whether or not other-category information causes Google to interpret our sites purpose differently.

On another note, you did spark a thought. We are linking our products from the recipe page but those links are hidden behind a products tab. Can you offer insight into how beneficial it would be to not "hide" that information in terms of SEO?

We sell food products that, of course, can be used in recipes. As a convenience to our customer we have made a large database of recipes available. We have far more recipes than products. My concern is that Google may start viewing us as a recipe website rather than a food product website.

My initial thought was to subdomain the recipes (recipe.domain.com) but that seems silly given that you aren't really leaving our website and the layout of the website doesn't change with the subdomain.

Currently our URL structure is...

• domain.com/products/product-name.html
• domain.com/recipes/recipe-name.html

We do rank well for our products in general searches but I want to be sure that our recipe setup isn't detrimental.