Provide a user friendly overview of everything which is wrong with url related data and a way to fix those

Hi

Magento has been struggling with many many url key, url path, url rewrite problems since Magento 2 was released. Most of these things happen when using translated url keys over multiple store views.
Many of these issues are still not properly fixed in 2.3.0. But people using Magento are struggling to find out what specific url-related issues they have which can cause all kinds of unexpected things to happen in Magento.

So next to fixing all those bugs, we also need to provide an overview of all incorrectly data which has accrued over the years in buggy Magento versions. Only fixing the bugs is not enough, as they won't fix the incorrect data.

Here are some suggestions:

1. Create an overview of url key's of products which are duplicated in the same storeview (example bug which can cause this: https://github.com/magento/magento2/issues/21737)
2. Create an overview of products with empty url key fields (example bug which can cause this: We recently imported product prices using a csv file and the import functionality in the backend of Magento, and all of the sudden around 22% of the imported products had their url key field being set to an empty string, I don't have exact steps to reproduce unfortunately)
3. Create an overview of products which have a non-empty url path field (example bug which can cause this: https://github.com/magento/data-migration-tool/issues/541)
4. Create an overview of categories having incorrect url paths (example bug which can cause this: https://github.com/magento/magento2/issues/16202)
5. Create an overview of url rewrites which haven't been generated correctly (based on category/product data + certain configuration settings) (example bug which can cause this: https://github.com/magento/magento2/issues/11615)
6. ...

There are tens/hundreds of bug reports on github touching many of these pain points, sorry for only linking the ones I created myself, but I haven't much time at the moment to make an overview of all these reported bugs.

Then, next to those overviews, we also need a user friendly way of fixing all this incorrect data somehow.

I'm opening this issue since I'm getting so tired of having to deal with all these bugs day in day out. It's a wonder if a week passes by where I'm nog hearing about some issue a client of ours has which is caused by all these bugs and it's very frustrating to see that there is no way for the client to be able to fix these things by themselves, usually you have to solve it by writing a bunch of SQL queries to fix stuff directly in the database, which is no fun at all.

Thanks for considering!

No files, tests, or entry points are named. Start by narrowing the requested URL-data reports and repair workflow into a defined scope, then establish how completion will be verified for each listed problem.