TYPO3 Core

I think this feature isn't needed, because you can set the slug of the page individually. Take for example the structure:

page-1
page-1 -> subpage-1-1
page-1 -> subpage-1-2 -> subsubpage-1-2-1

You can change your slug e.g. to

/subpage-1-2 instead of /page-1/subpage-1-2

so that page-1 isn't shown in slug for subpage-1-2

Any subsequent pages of subpage-1-2 will also omit page-1, because the slug of the parent page is taken into account when generating a new page under subpage-1-2.

This behaviour is more flexibel than with RealURL, because you can change the complete slug of the page, not only the segment of the page (where you need a possibility to omit a segment).

To make it short, just set the slug of your landing page to the slug you want. That's it.

For new projects you are absolutly right.
But at least a update solution for projects with used exclude function of realurl over several years on thousands of pages could/should be shipped with 9.5.

For your example it works!
But if you want subpage-1-1 or subpage-1-2 to be excluded from speaking url, you have to edit every slug on third level.
I think it's bad to say the editor has to care for this.

I think even for new projects this is a nice to have feature.
When editiors create new pages and in-between Page segment schould not be shown then the editor has to edit the slug every Time they create a page.
In that regard it would be much easier to simply tell the parent page to not show in a slug, so that editors don't have to bother with the slug.

Another Point is, when you use sluggenerator (for example: 3rd-Party extensions) so rearrange the whole page tree after an upgrade. Here you need to go into every Page to press the refresh button and modify the Slug after. it would be much more comfortable to exclude some specific pages and let the rest autogenerate.

Thanks for the transparent and professional solution. Looking forward to third party extensions on this feature.

It should be possible because (e.g. a extension with list and detail/show page):
a) Length of the URL for SEO
b) 'detail/show' as detailpage-title is not a (SEO-)category
c) Sometimes you do not know exactly how to name a "detail" page - cause of its content which is a direct child-category from the list-page... belongs to b)
d) IMPORTANT Independent content of the list page (ie anything that does not belongs to the plugin) should not appear on the detail page (SEO - DuplicateContent), in addition, the user must scroll again (Current solution one plugin/page for list and detail view)
e) and so on

Sorry but i don't know how to fix this with your hook @Benni Mack Mack ?

I believe in TYPO3 version 9.4, at least before 9.5.5 it was possible to do something like this in the routeEnhancers in the yaml config ('/../'):

-
routePath: '/../{news_title}'
_controller: 'News :: detail'
_arguments:
news_title: news

That worked great too, can you reinstall that please?

I tried https://github.com/b13/masi and it worked so far, except from the migration command. I migrated the db fields with db admin. It is currently not available via packagist or ter.