Before you begin, make sure that you understand exactly what the redirect is to accomplish. Think in terms of “target” and “original request”, or “redirect to” and “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.
Add URL Rewrite for Product
Step 1. Plan the Rewrite
To avoid mistakes, write down the “redirect to” path and “redirect from” path. The path includes 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.
Product with Category Path
Product without Category Path
Step 2. Create the Rewrite
On the Admin sidebar, tap Marketing. Then under Search & SEO, choose 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 that is to be redirected. Then, tap Search.
If there are multiple redirect records for the page, find the one that matches the applicable store view. Then, open the redirect record in edit mode.
In the upper-right corner, tap Delete. When prompted, tap OK to confirm.
In the upper-right corner of the URL Rewrites page, tap Add URL Rewrite.
When you return to the URL Rewrites page, tap Add URL Rewrite.
Set Create URL Rewrite to “For product”.
In the grid, find the product that is the target—or destination—of the redirect. Then, click the row.
Add URL Rewrite for a Product
Below the category tree, tap Skip Category Selection. For this example, the redirect does not include a category.
Skip Category Selection
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 will be created for each view.
In the Request Path field, type over the default entry, and enter 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 will receive an error when you try to save the redirect. The previous redirect must be deleted before you can create a new one.
Set Redirect Type to one of the following:
- Temporary (302)
- Permanent (301)
For your own reference, enter a brief Description of the rewrite.
URL Rewrite Information
Before saving the redirect, review the following:
- The link in the upper-left corner displays the name of the target product.
- The Request Path contains the path for the original “redirect from” product.
When complete, tap Save.
The new product rewrite now appears at the top of the URL Rewrites grid.
URL Rewrite Saved
Step 3. Test the Result
Go to the home page of your store.
Do one of the following:
- Navigate to the original “redirect from” product request page.
- In the address bar of the browser, enter the path to the original “redirect from” product immediately after the store URL. Then, press Enter.
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
- Request Path
- The product that is to be redirected. Depending on your configuration, the Request Path might include the .html or .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 already 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.
- 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.