Stop letting old URLs, deleted pages, and 404 errors drive your customers and search traffic into a dead end. This category features OpenCart modules designed to help you configure 301/302 redirects, manage broken links, and update your robots.txt file directly from the admin panel. Clean up your website's SEO structure quickly without any manual file editing.
Old URLs rarely disappear on their own; they remain in search results, promotional emails, customer bookmarks, and analytics reports. Therefore, redirects in OpenCart are crucial not only when changing the catalog structure, but also when configuring friendly SEO URLs, deleting pages, handling 404 errors, and editing indexing rules via robots.txt.
A redirect after website migration is required if the domain, category structure, friendly URLs, or product paths have changed. A permanent redirect sends the correct signal to search engines and prevents users from landing on a non-existent page.
Redirection from www is used to establish a single primary canonical version of a domain. For instance, a redirect from www to non-www in OpenCart helps eliminate duplicate URLs and avoids diluting link equity between two versions of the same page.
A redirect to friendly URLs is necessary after enabling SEO URLs or updating URL patterns. The old technical URL can be routed to the new, human-readable URL, ensuring customers reach the correct section and search engine crawlers receive a proper HTTP response.
It is best practice not to simply ignore 404 errors, but to log and analyze them. For pages that have a replacement, a 301 permanent or 302 temporary redirect should be assigned. For permanently deleted content, a 410 status code is often appropriate to help search engines quickly understand that the page is gone for good.
First, inspect the website for redirect chains, verify the mapping between old and new pages, and check robots.txt settings alongside server response codes. A properly configured redirect map usually recovers the majority of lost traffic, provided the migration was executed without chaotic or conflicting rules.