404 when moving to Magento 2Pradip Shah
When migrating platforms for example from WooCommerce to Magento or from Magento 1 to Magento 2, it is imperative that we move all URLs to ensure proper SEO authority is retained after the move as well as real users get a smooth Customer Experience (CX).
If it is not possible to maintain the same URLs, ensure redirects are made. This is especially true of a move from WooCommerce and also true when as part of the move the store is reorganized. When migrating data, an automated custom URL redirect process is recommended.
In spite of the best planning and intentions it is likely some URLs may be missed and redirects may not be setup.
Failing to do so has 2 negative effects
- BOTS, especially Google may visit the new site with the older URL and receive a 404. This can reduce your site rating on Google.
- Users that may have bookmarked or use browser history may get a 404 and get a bad CX resulting in visitors bouncing and reducing brand value.
Google Analytics does not show 404s. Google search console may show if the count is high. Neither of these is a reliable source to know what was missed.
Only the server knows for sure it severed a 404 and would have logged it in the apache or nginx access and/or error log files. On a new migration we recommend automating a 404 report from the log file, atleast once a day.
If using our luroConnect / Edge product, the dashboard can be used to setup a real-time alert for any 404 returned. This can then be actioned by developers or the agency to include a redirect.