Magento 2 module which can find potential url related problems in your catalog data
The purpose of this module is to give store owners of a Magento 2 shop insight into what url-related problems they have in their products, categories and url rewrites.
It was explicitly chosen not to have automated fixers for these problems, since fixing these issues can have a significant SEO impact.
It should be up to the store owner to figure out how he/she wants to fix these problems. Doing this with an automated tool might have a negative impact on SEO rankings, hence why it only reports problems and doesn't try to fix them.
url_keyattribute values within the same parent
url_keyattribute values on the same store view
This module should be compatible with Magento 2.1.x, 2.2.x, 2.3.x and 2.4.x versions.
Some code in this module is using old ways of doing things. It could have been written in a more modern way (using message queues instead of cronjobs, use newer syntax for UI components, ...). But we wanted this module to be compatible with older versions of Magento, so we've chosen this route for now.
The module should be compatible with PHP 7.0, 7.1, 7.2, 7.3 and 7.4
You can use composer to install this module:
composer require baldwin/magento2-module-url-data-integrity-checker
Or download the code and put all the files in the directory
After which you can then activate it in Magento using:
There are some automatic cronjobs running every night at 02:10, 02:15, 02:20 and 02:30 which will run the various checkers of this module.
You can also opt to manually refresh one of the checkers in the Magento admin, which will schedule one of the cronjobs to be ran the next minute. You'll have to wait a few minutes (depending on the number of problems and how big your catalog is) before you'll see the results appearing. You'll need to refresh the page yourself btw, it won't happen by itself.
There are also some cli commands you can execute, which will give you instant feedback about found problems, and will also store that data so you can see them in the Magento admin:
In the Magento admin, you can find the results in:
The results of the checkers are currently stored in the directory
After cloning your fork:
auth.jsonfile with your credentials for https://repo.magento.com/
make checkdoesn't report problems with proposed changes