Forum Moderators: Robert Charlton & goodroi
www.example.com/widgets/blue At the www sub-directory level without content negotiation...
www.example.com/widgets/blue/ At the host level...
widgets.example.com/blue/ At the host level with content negotiation...
widgets.example.com/blue I always recommend the use of top level keywords in the naming conventions.
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...
widgets.example.com/blue This would be my second choice...
www.example.com/widgets/blue What's your preference?
domain.com/../blue_widget/
or
domain.com/../blue_widget.html
?
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...
domain.com/widgets/
...and your widget pages would be extensionless pages within the widgets/ subdirectory...
domain.com/widgets/blue
domain.com/widgets/red
See the discussion about trailing slashes vs no trailing slashes in this thread...
Blog URL Structure for SEO
[webmasterworld.com...]