| 5:06 pm on Jan 14, 2008 (gmt 0)|
It doesn't matter any more. The page content and title do.
| 5:09 pm on Jan 14, 2008 (gmt 0)|
At the www level with content negotiation...
At the www sub-directory level without content negotiation...
At the host level...
At the host level with content negotiation...
I always recommend the use of top level keywords in the naming conventions.
| 4:37 pm on Jan 15, 2008 (gmt 0)|
I try to name my directory structures logically using relevent keywords.
www.widgets.com/purple-monkey-dishwasher/bluewidget.html isnt that useful.
| 4:54 pm on Jan 15, 2008 (gmt 0)|
These days, for me, the shorter the better. I've found that using logical top level keywords (single) works well from a usability standpoint.
Once I start seeing two or more hyphens appearing in any level of the path, the hairs on my neck rise. So, a few years ago I started trimming the use of hyphens and making up for order within my path structures. Keep them short and "very relevant" to the destination. If you can trim to one word at each level, that is the magic bullet.
For me, this would now be the perfect URI...
This would be my second choice...
What's your preference?
| 5:20 pm on Jan 15, 2008 (gmt 0)|
I personally favour
As i have had more success in getting pages listed with this style
| 6:45 pm on Jan 15, 2008 (gmt 0)|
One further thought suggested by the example...
In an extensionless environment, if that's what you're asking about, you don't want to turn each page into a directory. So, if you were going extensionless, the main page of your widget directory would be the default page of a directory...
...and your widget pages would be extensionless pages within the widgets/ subdirectory...
See the discussion about trailing slashes vs no trailing slashes in this thread...
Blog URL Structure for SEO