If a category is removed from your catalog, you can use a category rewrite to redirect links to the URL of another category in your store. Think in terms of target / original request or redirect to / redirect from. Although people might still navigate to the former page from search engines or outdated links, the redirect causes your store to switch to the new target.
When automatic redirects are enabled and you save a category, all product and category rewrites are generated in real time and stored in rewrite tables by default. This process could result in significant performance issues for categories with many assigned products. The solution is to change this default and skip the generation of category/products URL rewrites of products for category save. In this case, product rewrites are generated only for the canonical product URL. See Automatic product redirects for more information.
To avoid mistakes, write down the redirect to path and redirect from path and include the URL Key and suffix (if applicable).
If you are not sure, open each category page in your store, and copy the path from the address bar of your browser.
In the process of redirection, all GET parameters specified in the URL are removed for security reasons.
On the Admin sidebar, go to Marketing > SEO & Search > URL Rewrites.
Before you proceed, do the following to verify that the request path is available:
In the search filter at the top of the Request Path column, enter the URL key of the category that is to be redirected and click Search.
If there are multiple redirect records for the page, find the one that matches the applicable store view and open the redirect record in edit mode.
In the upper-right corner, click Delete. When prompted, click OK to confirm.
When you return to the URL Rewrites page, click Add URL Rewrite.
Set Create URL Rewrite to
For category and choose the target category in the tree that is the destination of the redirect.
In the URL Rewrite section, do the following:
If you have multiple stores, select the Store where the rewrite applies.
For Request Path, enter the URL key of the category that the customer requests. This is the redirect from category.
The request path must be unique for the specified store. If there is already a redirect that uses the same request path, you receive an error when you try to save the redirect. The previous redirect must be deleted before you can create one.
Set Redirect to one of the following:
For your reference, enter a brief description of the rewrite.
Before saving the redirect, review the following:
When complete, click Save button.
The new category rewrite appears at the top of the URL Rewrites grid.
Go to the home page of your store.
Do one of the following:
The new target category appears instead of the original category request.
|Create URL Rewrite||Indicates the type of rewrite. The type cannot be changed after the rewrite is created. Options:
|Request Path||The category that is to be redirected. Depending on your configuration, the request path might include the .html or .htm suffix, and parent category. The request path must be unique, and cannot be in use by another redirect. If you receive an error that the request path exists, delete the existing redirect, and try again.|
|Target Path||The internal path that is used by the system to point to the destination of the redirect. The target path is grayed out and cannot be edited.|
|Redirect||Determines the type of redirect. Options:
No - No redirect is specified. Many operations create redirect requests of this type. For example, every time you add products to a category, a redirect of the
Temporary (302) - Indicates to search engines that the rewrite is for a limited time. Search engines generally do not retain page rank information for temporary rewrites.
Permanent (301) - Indicates to search engines that the rewrite is permanent. Search engines generally retain page rank information for permanent rewrites.
|Description||Describes the purpose of the rewrite for internal reference.|