> The reason I ask is it seems I read some place if the SE see two index or default pages you could be penalized.
I also remember reading something about that a while back. I don't lend any validity to the statement. Its only logical that when you start breaking content down, that you have a starting page or home page for each section. Why can't it be called index.htm? Someone may be able to chime in and prove me wrong, but I've been doing it this way for years. Whose to say it is the right way, its my way and it works fine.
I look at content a little differently. My goal is to break that content down to its least common denominator. From there I start building directory structure. Let's use baseball as an example. For example purposes, I'm picking the domain baseball.com.
I don't keep up with sports so please forgive my use of terminology.
If I have only one page for each team, then I'm going to concentrate at the root level. For example...
If I have multiple pages for each team which is most likely the case, I'm going to build sub-directories for each one. For example...
Note that I've not specified a page name because I am going to use an index page for each sub-directory.
Now, if I find that I have to provide a page for each team player, then I'm going another sub-directory deep like this...
I think you kind of get the point of where I'm going with this. Your content is going to determine how far you need to travel in a directory structure for organization and management purposes. Its only logical that each sub-directory be treated as a site in itself. Your building a network, and this is a long term strategy so you need to plan carefully.
Please note that my above example is based on straight html. If you bring dynamics into the equation, then its a different playing field because there are very few limitations if done correctly. Just remember, treat each sub-directory as its own entity. Based on my experience, this works well.