Welcome to the Q&A Forum

Thanks for the response. I think you boiled it down to the basic questions very nicely.

If you have any research you can point me to to help me understand just how useful the extra page might be to google bot, or (on the other hand) how much traffic we may lose to the extra click, i'd be most grateful for a pointer.

thanks again!

Hello!

We are a retailer with brick and mortar stores in different cities. We have a website (ourbusiness.com), which includes

• a blog (ourbusiness.com/blog) and
• a separate ecommerce site for each store in subfolders (ourbusiness.com/Boston-store and ourbusiness.com/Atlanta-store).
• NB: We do this for non-business reasons and have no choice.

So, this is not like REI (for example) or other stores with lots of locations but one central ecommerce operation.

Most experts seem to recommend a site structure that echoes REIs. IE:

• a home page principally devoted to ecommerce (rei.com)
• includes an Our Locations-type page (rei.com/stores) which links to local store pages like
• (rei.com/stores/fresno)

I understand how this would help REI, since their homepage is devoted to ecommerce and they need a store locator page that doesn't compete with the shopping experience.  But since we can't send people to products directly from our home page, is there any reason for us not to put the store locator function right on the home page?

That is, is there any reason in our case to prefer (A) ourbusiness.com/our_locations/Boston_store  over (B) ourbusiness.com/Boston-store?

As i see it, the extra page (/our_locations/) could actually hurt, as it puts products one click further away from customers, and one link deeper for bots.

On the other hand, it may make the multi-store structure clearer to bots (and maybe people) and help us in local search.

Finally, would it make a difference if there were 10 stores vs 2?

Thanks for any thoughts!