**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
Worth mentioning as it was in zulip chat by @yorkshirepudding I just tested and the two work together without issue as long as you don't use the "Exclude comments from Content...
Search does not include comments
There is also Node Comments Search - this searches the node and all comments (default search is node and first page of comments) as part of the content search. Izzy's module above is a separate...
Search does not include comments
I have created a new module comment_search
Search does not include comments