Magento Commerce, 1.14.x

Magento 1.x Software Support Notice
For Magento Commerce 1, Magento is providing software support through June 2020. Depending on your Magento Commerce 1 version, software support may include both quality fixes and security patches. Please review our Magento Software Lifecycle Policy to see how your version of Magento Commerce 1 is supported.

Creating URL Redirects

The URL Redirect tool can be used to create product and category redirects, and custom redirects for any page in your store. When the redirect goes into effect, any existing links that point to the previous URL are seamlessly redirected to the new address. The following instructions show how to use the URL Redirect tool to create three different kinds of redirects:

All redirects reference a “Target Path” and “Request Path,” as shown in the following examples. The “Request Path” is the old URL, and the “Target Path” is where you want the URL to go from now on.

You can use redirects to create additional URLs for items, as a temporary seasonal change, or as a permanent change. Redirects can be created for any valid path, including CMS content pages. Internally, the system references products and category by ID. No matter how often the URL changes, the ID remains the same. Here are some ways you can use URL redirects:

  • Original URL
  • Additional Product URL
  • Additional Category URL
URL Redirect Management
URL Redirect Management
  • Field Descriptions




    Indicates the type of redirect to be made. The type cannot be changed after the redirect is created. Options include:




    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:


    A Request Path must be unique, and not have been used previously.If you have made several attempts to redirect the same page, you should 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:


    Redirect Type

    Indicates whether the redirect is temporary or permanent. Options include:


    Temporary (302)

    Permanent (301)


    Describes the purpose of the redirect. This field is for reference and is not visible to customers.