Before you begin, you should know exactly what you want the redirect to accomplish. Just remember— the “Request Path” is the old URL, and the “Target Path” is where you want the URL to go from now on. To manage multiple paths that lead to the same product, see: Canonical Meta Tag.

New Product Rewrite

Step 1: Get the Product ID of the Target URL

1.

On the Admin menu, select Catalog > Manage Products.

2.

Find the product in the list that is the destination of the rewrite and take note of its product ID.

Step 2: Create the Product Rewrite

1.

On the Admin menu, select Catalog > URL Rewrite Management.

2.

In the upper-right corner, click the Add URL Rewrite button.

3.

Set Create URL Rewrite to “For product.”

Create URL Rewrite for Product

4.

In the list, find the product that you want to redirect, and click the record.

5.

Scroll down to the bottom of the Select Category tree, and click the Skip Category Selection button.

6.

In the URL Rewrite Information section, do the following:

URL Rewrite Information

a.

If you have multiple stores, set Store to the specific view where the rewrite applies.

b.

In the Request Path field, enter the URL key of the page to be redirected.

c.

Set Redirect to one of the following:

• Temporary (302)
• Permanent (301)

d.

For your own reference, enter a brief description of the rewrite.

7.

When complete, click the Save button.

Your new product rewrite now appears at the top of the list.

Step 3: Refresh the Index

1.

On the Admin menu, select System > Index Management.

2.

Select the Catalog URL Rewrites checkbox.

3.

Set the Actions control to “Reindex Data,” and click the Submit button.

Refresh Catalog URL Rewrite Index

Step 4: Test the Rewrite

Test the rewrite from your store, to make sure that it works correctly.

• Field Descriptions

  Field	Description
  Create URL Rewrite	Indicates the type of rewrite to be made. The type cannot be changed after the rewrite is created. Options include: For Category For Product Custom
  ID Path	The ID of the target page. The ID Path and Target Path refer to the same page.
  Request Path	The URL of the page that is to be redirected. Depending on your configuration, the Request Path might include the .html suffix and category. For example: brandname brand/brandname catalog/category/view/id/56 private-sale-shoes/prima-pump.html brand/brandname.html A Request Path must be unique, and must not have been used previously. If you have made several attempts to redirect the same page, delete any unsuccessful redirects and refresh the cache.
  Target Path	The URL that points to the destination page. The Target Path can be a different CMS page, or the result of a search. To avoid getting a 404 "Page Not Found" error, the path must exactly match what the system expects to find. The following examples are valid target paths: brandname brand/brandname catalog/category/view/id/52 catalogsearch/advanced/result/?brand=brandname http://magentocommerce.com
  Redirect	Indicates whether the rewrite is temporary or permanent. Options include: No No redirect is specified. Temporary (302) Indicates to search engines that the rewrite is for a limited duration. Search engines do not preserve page rank information for temporary rewrites. In the URL Rewrite Management list, temporary redirects have the letter “R” in the Options column. Permanent (301) Indicates to search engines that the rewrite is permanent. Search engines generally preserve page rank information for permanent rewrites. In the URL Rewrite Management list, permanent redirects have the letters “RP” in the Options column.
  Description	Describes the purpose of the rewrite. This field is for reference and is not visible to customers.