After July 2021, the 2.3.x release line will no longer receive quality updates, or user guide updates. PHP 7.3 reaches end of support in December 2021 and Adobe Commerce 2.3.x reaches end of support in September 2022. We strongly recommend planning your upgrade now to Adobe Commerce 2.4.x to help maintain PCI compliance.

Custom URL Rewrites

The information on this page is intended for Adobe Commerce 2.3 customers who are on an extended support contract. The Adobe Commerce Merchant Documentation for current releases is published on the Adobe Experience League.

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 domain. You can use a custom redirect to reroute requests for a product, category, 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 / source 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.

URL rewrites - custom Add URL Rewrite

Step 1. Plan the Rewrite

To avoid mistakes, write down the URL of the redirect to page and the URL key of the redirect from page.

If you are not sure, open each page, and copy the URL from the address bar of your browser.

Custom path

Redirect to:

Redirect from:


Step 2. Create the Rewrite

  1. On the Admin sidebar, go to Marketing > SEO & Search > URL Rewrites.

  2. 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 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.

  3. When you return to the URL Rewrites page, click Add URL Rewrite.

  4. Set Create URL Rewrite to Custom.

  5. Under URL Rewrite Information, do the following:

    • If you have multiple store views, select the Store where the rewrite applies.

    • In the Request Path field, enter the URL key and path—if applicable—of the product, category, or CMS page that is to be redirected.

      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.

    • In the Target Path field, enter the URL of the destination. If the target is located on another website, enter the fully qualified URL.

    • Set Redirect to one of the following:

      • Temporary (302)
      • Permanent (301)
    • For your reference, enter a brief description of the rewrite.

    URL rewrite information Custom URL Rewrite

  6. Before saving the redirect, review the following:

    • The Request Path contains the URL key or path of the original redirect from page.
    • The Target Path contains the URL of the redirect to page.
  7. When complete, click Save.

    The new rewrite appears in the grid at the top of the list.

    Custom URL rewrite - saved Saved URL Rewrite

Step 3. Test the Result

  1. Go to the home page of your store.

  2. Do one of the following:

    • Navigate to the original redirect from page.
    • In the address bar of the browser, enter the name of the original redirect from page immediately after the store URL and press Enter.

    The new target page appears instead of the original page request.

Field Descriptions

Create URL Rewrite Indicates the type of rewrite. The type cannot be changed after the rewrite is created. Options: Custom / For category / For product / For CMS page
Request Path The CMS page that is to be redirected. The Request Path must be unique, and cannot be in use by another redirect. If you receive an error message 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. The target path is grayed out and cannot be edited.
Redirect Determines the type of redirect. Options:
No - No redirect is specified.
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.
Description Describes the purpose of the rewrite for internal reference.

In the process of redirection, all GET parameters specified in the URL will be removed due to security reasons.