WYSIWYG and Text Code Editors Forum

I'm an FP junkie and that's what I do. If I had a sports related site and was covering different types of sports, I might do something like this...

root/baseball/angels/
root/football/giants/
root/basketball/lakers/

Then in my root directory (the main one) I'd include a site directory (or site map) that leads to those sub-directories. I typically give each subdirectory its own index page so you can use addresses like...

http //www domain.com/baseball/angels/

That index page for that sub-directory could end up being a site map in itself with links to all pages within that sub-directory. Depends on how much content you are managing.

Try not to go any deeper than two levels deep. If you do go any deeper, expect a longer cycle on getting pages indexed. If its a site specifically for baseball, then you can bypass the /baseball/angels/ and just go with /angels/. The goal would be to keep your content as close to the root as possible. But, you also have to think about site manageability too.

P.S. To keep content closer to the root, you might try something like this...

/baseball/angels.htm
/football/giants.htm

Again, it will all be relative to the amount of content you have for each team. If its just one page, then the above would work best. If the site is strictly about baseball, then this would probably be the best...

Please excuse the basis Questions.

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...

baseball.com/angels.htm

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...

baseball.com/angels/

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...

baseball.com/angels/players/

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.

> If I understand right being on baseball only, the folder would have the htm in the folder name (Cubs.htm) and then you would include an index page for each folder?

The folder (sub-directory) name is /cubs/, not cubs.htm which is a page. The url would look like this...

baseball.com/cubs/index.htm

That's it. You would only need to give the root and sub-directory as an address...

baseball.com/cubs/

Then your pages within /cubs/ would look like this...

baseball.com/cubs/history.htm
baseball.com/cubs/players.htm
baseball.com/cubs/statistics.htm

> Would the folder index page be index.htm or something like Cubs_index.htm.

Yes, the starting page for each sub-directory would be index.htm or whatever markup language you are using (.asp, .cgi, .php, etc.).

> The reason I ask is it seems I read some place if the SE see two index or default pages you could be penalized.