How are Adobe Commerce URL rewrites scoped to a store view?

Definition: An Adobe Commerce URL rewrite maps a request path to a target path for a selected Store in the Admin. The request path identifies the URL key or path being redirected, and the target path identifies the destination.

Key facts

• Adobe's URL rewrites documentation says the tool changes URLs associated with products, categories, or CMS pages.
• The same documentation says Commerce supports product, category, CMS page, and custom URL rewrite types.
• In the custom rewrite workflow, Adobe instructs you to select the Store where the rewrite applies when multiple store views exist.
• The custom rewrite instructions require the Request Path to be unique for the specified store. An existing redirect with that path causes an error when you save.
• The Target Path is the destination URL. Adobe also lists Temporary (302) and Permanent (301) as redirect choices.

What does the Store selection control?

Adobe's custom URL rewrite instructions use Store as the selector label. When multiple store views exist, the administrator selects the Store where the rewrite applies. The same instructions tell the administrator to look for the redirect record that matches the applicable store view when more than one record exists for a page.

The uniqueness rule is scoped to that selection: Adobe states that the Request Path must be unique for the specified store. If a redirect already uses the same Request Path, the administrator must delete the previous redirect before creating another one.

How do Request Path and Target Path differ?

The Request Path is the URL key or path of the original page, which Adobe describes as the redirect from page. The Target Path is the URL of the redirect to page. For a destination on another website, Adobe requires a fully qualified URL.

Adobe's example separates the two values:

Redirect to:
http://www.different-website.com/page.html

Redirect from:
category/product.html

The first value is the destination entered as Target Path. The second is the path entered as Request Path. A custom rewrite can therefore use a local storefront path as its request and an external fully qualified URL as its target.

How can you check a rewrite before saving?

In Admin, Adobe's workflow is Marketing > SEO & Search > URL Rewrites, followed by Add URL Rewrite. Set Create URL Rewrite to Custom, choose the applicable Store, and enter the Request Path and Target Path. Before creating the record, search the Request Path column for the URL key of the page being redirected. If an existing record matches the applicable store view, open it and delete it before continuing.

After saving, Adobe's test procedure starts at the store home page. Open the original redirect-from page, or enter that path immediately after the store URL in the browser address bar. The new target page appears instead of the original page request.

Related terms

• When does an Adobe Commerce URL rewrite issue an HTTP redirect?
• How are product and category URL suffixes configured in Adobe Commerce?

FAQ

Is the Request Path unique across every store view?

Adobe states that the Request Path must be unique for the specified Store. The documented validation rule is therefore expressed against the selected store scope.

Can the Target Path point to another website?

Yes. For a custom rewrite, Adobe instructs the administrator to enter the destination URL and use a fully qualified URL when the target is on another website.

Which redirect types can be selected?

Adobe lists Temporary (302) and Permanent (301) in the custom rewrite form. The selected value determines the redirect type for that rewrite.

Sources

1. Adobe, "URL rewrites | Adobe Commerce", October 8, 2026
2. Adobe, "Custom URL rewrites | Adobe Commerce", October 8, 2026

---

Check how a page reads to answer engines. Open the GEO score analyzer