Magento Commerce, 2.2.x

Magento 2.2.x Notice: As outlined by the Magento Software Lifecycle Policy, Magento 2.2.x has reached the End-of-Support and will no longer receive quality fixes or documentation updates. To maintain your site's performance, security, and PCIPayment Card Industry: Refers to debit and credit cards and their associated businesses. compliance, upgrade to the latest version of Magento.

The online Magento 2.2.x User Guide is scheduled for removal, but will remain available in PDF for Open Source, Commerce, and Commerce for B2B.

Custom Rewrites

A custom rewrite can be used to manage miscellaneous redirects, such as redirecting a page from your store to an external website. For example, you might have two Magento websites, each with their own domainThe address of a website on the web; what the customer types in their browser address bar to access the store.. You can use a custom redirectA method used to alert browsers and search engines that a page has been moved. 301 Redirect: Permanent change 302 Redirect: Temporary change to reroute requests for a product, categoryA set of products that share particular characteristics or attributes., or page to the other website. Unlike other redirect types, the target of a custom redirect is not chosen from a list of existing pages in your store.

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
  • Field Descriptions



    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 path to the product, category, or CMS page that is to be redirected. Depending on your configuration, the Request Path might include the .html or .htm suffix.

    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 path or URL that is the destination of the redirect.


    Determines the type of redirect. Options :


    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.