I can only say that this combination can get messy if the number of categories increase.
So let me ask you this: - what would that resource be called or identified with? We need that to build a URL that uniquely locates that resource. Whether it ends up as global ID or some kind of context-sensitive ID, the URL has to refer to that. Would it make sense if we created a ID called qUKjgY8a for a search result, and use the URL
http://www.example.com/search/qUKjgY8a? But then how does the user remember this to be able to locate the resource again?
3) I will be using a title less URL for my next installation, something like site.com/qUKjgY8a
.
Wait, are we talking about human readable URL?
Oh well, to me, the most fundamental driving factor is to be as human-friendly as possible and the identifiers should be made URL friendly It’s SEO practice to design a readable URL. This is easily seen when you do a search in Google, and the search results will highlight any of your search terms in the URL’s of the results. Obviously, Google looks at what is in the URL itself and not just the page.
URL design is really not that hard, it just takes understanding core principles and best practices, and then applying them. And secondly, all you need is to just escalate conversations to raging debates when simple questions are asked about proper URL usage in context of Web Architecture.
However, I believe every forum owners will see huge improvements compared to their prior rankings if they focus on URL design and create a URL management plan. The good news is that URL design is mostly a one time endeavour assuming site maintainers adhere to the management plan, at least until there is a full site rearchitecture.
But all of the whys and wherefores regarding URL planning and design are beyond the scope of this post, and instead will be the subject of many posts in the future.