Before you begin, make sure that you understand exactly what the redirect should accomplish. 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 product page in your store, and copy the path from the address bar of your browser. When creating a product redirect, you can either include or exclude the category path. For this example, we create a product redirect without a category path.
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 page 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 it in edit mode.
In the upper-right corner, click Delete. When prompted, click OK to confirm.
In the upper-right corner of the URL Rewrites page, click Add URL Rewrite.
Set Create URL Rewrite to
In the grid, find the product that is the target (destination) of the redirect and click the row.
Below the category tree, click Skip Category Selection.
For this example, the redirect does not include a category.
The Add URL Rewrite for a Product page displays a link to the target in the upper-left corner, and the Target Path field displays the system version of the path, which cannot be changed. Initially, the Redirect Path field also displays the target path.
If you have multiple store views, set Store to the view where the rewrite applies. Otherwise, a rewrite is created for each view.
For Request Path, replace the default by entering the URL key and suffix (if applicable) of the original product request. This is the redirect from product that you identified in the planning step.
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 Type to one of the following:
For your own reference, enter a brief Description of the rewrite.
Before saving the redirect, review the following:
When complete, click Save.
The new product rewrite now 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 product appears instead of the original product request.
|Create URL Rewrite
|Indicates the type of rewrite. The type cannot be changed after the rewrite is created. Options:
For category /
For product /
For CMS page
|The product that is to be redirected. Depending on your configuration, the Request Path might include the
.htm suffix, and 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.
|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.
|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
No type is created each store view.
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.
|Describes the purpose of the rewrite for internal reference.
You can quickly update URL rewrites for multiple or all products simultaneously using the following steps.
On the Admin sidebar, go to Catalog > Products.
Select all the products for which you want to update URL rewrites.
Under Actions, choose Update attributes to update multiple or all rewrites.
Under PRODUCTS INFORMATION, click the Websites tab.
In the Add Product To Websites section, select all websites for which you want to restore URL rewrites.
When ready to update, click Save.
All selected products are readded to the selected websites and URL rewrites are regenerated.