Widget guide

What to name different pages

[roblaw]

We recently had a writer put togehter a 'widget guide' as content for our site. The guide is broken into 8 sections. To get the most value, I assume that naming the different pages with something related to the topic would be helpful. However, how much is too much?

1) Is this bad?:
widget-guide-part1.html
widget-guide-part2.html
etc.

2) Is this too much?:
widget-guide-do-I-need-to-buy-widgets.html
widget-guide-how-many-widgets-do-I-need.html

3) Is this too little?:
widget-guide-need.html
widget-guide-how-many.html

We are leaning toward using naming structure number 3, but if there isn't any real benefit to doing so, we would rather use the logic in number 1.

Anyone have any experience, feedback, or knowledge?

Thanks Much.

roblaw

[grandpa]

feedback

I'd keep the names easy enough to be remembered and typed. A keyword search might offer some insight into the best combination of page names and page titles.

experience

Despite my best effort to come up with some terrible page names, I have pages that rank well. Content is king.

[jo1ene]

Titles are much more important than file names. There's a bit of debate about whether file names matter anyway. I would go with #1 or #3. Don't feel bad about going with #1 if your titles are good and descriptive.

[roblaw]

Thanks to you both.

I would be concerned that there could be some sort of negative impact, in the future, when getting too goofy (long and stuffed with the title) with the actual page file names.

If someone is writing pages out of a DB, it would be very easy to simply name the file using the KW's with separators. After seeing some of the pages that come up at YHOO, I am sure that is what some people are doing. However, I was tempted to do the same after "seeing some of the pages that compe up at YHOO".

Thanks again.

roblaw