I think that you can do a virtual machine instance of OpenCart and see what the system returns by viewing page source. I haven't personally used Shopify but as a hosted solution, you'll have to test to see how that works out. Then do an audit of the code both spit out.  Remember, the on-page optimization is only one part of your solution.

Thanks Saijo,

We are trying to silo product types/categories and break them into different sitemaps. I'm familiar with SF but I don't think it will create sitemaps with the granularity that we are looking for.

I'm using XMLSpy but I'm finding it hard to break out blocks of content.

To my knowledge, Screaming Frog doesn't allow you to create an XML sitemap. Perhaps Excel allows you to format the output from SF but I'm not sure. I did find a utility called XMLSpy which, though pricey, allows me to do some of the sorting I was looking for. Once sorted, I can manually pull out sections to segment my sitemap. It is a pain in the neck because I can determine a silo and do it automatically. That being said, I think I can develop a sitemap template and have our new web programmer to develop a way to auto generate a group of segmented sitemaps.

Anyone know if there is a canned solution that works with IIS?

I have a site with around 17,000 pages and would like to create a sitemap and then segment it into product categories.

Is it best to create a map and then edit it in something like xmlSpy or is there a way to silo sitemap creation from the outset?

I am confused. So lets that I have an ecommerce site that has 20 types(books, toys…) / 20 categories each / 20 subcategories each and thousands of products under each subcategory.

When we say go flat, is it ideal to go all the way like http://www.website.com/type (20 of these), and http://www.website.com/category (400 of these) and http://www.webiste.com/subcategory (8000 of these)and thousands of product pages. So there is no page more than  1 directory level down. Does this mean flat architecture?

I am confused. So lets that I have an ecommerce site that has 20 types(books, toys…) / 20 categories each / 20 subcategories each and thousands of products under each subcategory.

When we say go flat, is it ideal to go all the way like http://www.website.com/type (20 of these), and http://www.website.com/category (400 of these) and http://www.webiste.com/subcategory (8000 of these)and thousands of product pages. So there is no page more than  1 directory level down. Does this mean flat architecture?