After lots of experimentation I think the stack overflow approach is best (assuming the slug part is generated in the links but ignored).
First of all you already have the record id therefore you do not need to look-it up. Second you can edit the slug (because for example of a mistake) and you do not break the url. It is still very readable. If somebody needs to dictate the url over the phone, they only need to get the numeric part right. The numeric part can be compressed using a URL shortened and does not need to be a number. Massimo On Monday, 9 July 2012 18:38:20 UTC-5, Francisco Costa wrote: > > Some web applications with restful URLs like Foursquare ( > https://foursquare.com/v/restaurante-baobab/*4bed589a75feef3b8d0197e6*<https://foursquare.com/v/restaurante-baobab/4bed589a75feef3b8d0197e6>) > > put ID's at the end of the URL, some others like StackOverflow ( > http://stackoverflow.com/questions/*11394640* > /pros-and-cons-of-ids-at-the-end-of-the-url<http://stackoverflow.com/questions/11394640/pros-and-cons-of-ids-at-the-end-of-the-url>) > > put them in the middle, just before the title slug.. > > There are even others like Quora ( > http://www.quora.com/Is-there-any-difference-in-terms-of-SEO-between-the-URL-REST-formats-on-Quora-and-StackOverflow) > > that don't put them at all, only use the slug. > > In your opinion wish one is best for information management and > performance? What is the impact in terms of SEO? >
