If you are going to use a slash (
/) in your URL, you should have content when the URL is truncated to that point. A slash in the URL commonly represents a directory. Both users and bots often shorten URLs to the slash looking for an index page.
An alternative is to use dashes:
/post-best_funny_videos-dkKE_wd3jJ. Dashes are not commonly understood to have special meaning in the URL path. A 404 error at a URL truncated to the dash would be perfectly appropriate.
In my experience putting the ID last in the URL leads to problems with long URLs. Long URLs often get truncated by email, forums, and other content management systems. Bots see these truncated URLs and crawl them. When the ID is at the end, the information you need to reconstruct the URL is lost and you have no choice but to return a 404 error. When the ID is near the front, the ID is usually preserved and you can redirect to the correct URL.
I agree that an alpha-numeric ID near the front is not very user friendly. It is hard to read. I'd recommend switching to a numeric ID that is much easier for users to skip over. That way you can still have it near the front.
The other problem with your URLs is your use of underscores to separate words. Underscores in URLs are not good for SEO because Google treats them as part of the word, rather than word separators. In URLs, dashes should always be preferred to underscores to separate words.
Your final URL should:
- Use dashes rather than slashes so it doesn't look like you have directories.
- Use dashes rather than underscores to allow Google to parse the URL.
- Use a numeric ID rather than an alpha-numeric id for usability.
- Put the ID near the front to allow recovery from URL truncation.
A better URL would be: