**Description of the need**
Since URL Aliases often closely match the title of a piece of content, you could think of a node's URL Alias like its machine name...
**Proposed solution**
That got me thinking; why not make the URL Alias field part of the node's Title field, in the same way that a Machine Name field is part of the entity's Title field?

So, when you create a piece of content for which URL Aliases are enabled, they would appear next to the Title as text that's generated automatically as you enter the Title. And there'd be a button that would enable an editable field for if you wanted to change the URL Alias to something other than the default.

Based on this (and other) screenshots, I believe WordPress does (or did) something very similar:

(Source: https://www.theblogstarter.com/how-to-add-links-to-your-wordpress-blog/)
EDIT: Updated WP screenshot/source.
GitHub Issue #:
3993
Recent comments
Hello, @aubergine! Thanks a lot, I got it, all sorted out.
How to get the current page language?
In addition to what @findlabnet has said, you possibly want to be looking at metatags as you can then tell search engines which page is the canonical source for a given page. In this scenario,...
xmlsitemap module generates wrong links for languages
Not only twice — the number of languages not excluded from the sitemap can be greater than that. This feature is designed according to the corresponding recommendations. So, I can't...
xmlsitemap module generates wrong links for languages