It really depends on what you're looking to improve by shorter URLs. You said your "system," but your current URLs work fine with your existing system, whatever it is.
The URL in its long form since the formatting cut it off in your post:
Code:
http://www.someautodealer.com/vehicle-details/67158a105c566a46881200e20c47d37c/2000+buick+lesabre+limited+4-door+sedan.html
As far as your
system and the logistics of loading the vehicle, this is absolutely fine. I imagine your .htaccess is set up to look for the "67158a105c566a46881200e20c47d37c" value after "vehicle-details," and I imagine that long string is the unique hash that identifies it within the database. Then the "2000+buick+lesabre+limited+4-door+sedan.html" is just there for SEO/user-friendliness purposes.
So by your diction of "system," if it works as intended, there is nothing inherently wrong with the "system." Otherwise, you need to specify what you mean by system. Do you think the database structure and using a 128-bit vehicle hash is inefficient? Do you think your current system is slow? Do you have any technical reasons as to why the URL is not good?
You initially said "system," but then said it doesn't look good "to your eyes." So are you going for aesthetics, system efficiency, SEO improvement, or what? I don't know what you told your developer, but if you randomly came to me from a
development standpoint and told me that the URLs where no good "for the system," I would tell you the URLs work perfectly fine
from a development standpoint.
If you want to improve them from a UX/SEO standpoint, this may not be something you should be consulting with your developer on. There are a few of us who have a grasp on everything, but most developers merely program what they're told to do. If the system works and you tell the
developer it doesn't, he's going to tell you you're crazy. Simple as that.
But if you want SEO-friendly URLs, then I can see your perspective. A URL like this may be better:
Code:
http://www.someautodealer.com/2000-buick-lesabre-limited-4-door-sedan-v39.html
The keywords are closer to the root of the URL, the plus signs are removed, and the vehicle identification is reduced to "39" instead of "67158a105c566a46881200e20c47d37c." If your developer is not also well-versed in SEO/UX, he
would not understand your perspective, so it is a moot point in arguing with him. Note that you have to also understand the implications of your request. To simply change that URL, you have to pay your SEO guy to find a suitable replacement structure that will best benefit keyword placement and density then you have to pay your development guy to not only change how your system recognizes the URL
but also to restructure the entire database to change the hash structure from a 128-bit hash to a dynamic integer identification key.
You really need to clarify what your goals are in changing the URL rather than just saying it's better for the system, because then you're telling a developer that his system doesn't work when he knows he knows more about the system than you do. I also can promise you that no developer is going to appreciate you randomly throwing articles at them, because he knows damn well that you went online and found those and now consider yourself a self-proclaimed expert in the field, which then minimizes and insults his years of experience over you in the field.