Search-term redirects and storefront routing

Search-term redirects, URL redirects, and search merchandising solve different problems. Use this guide to choose the right capability for standard Adobe Commerce search, Live Search, and Commerce Storefront powered by Edge Delivery Services.

Understand redirect types

These capabilities differ in what triggers the behavior and what the shopper sees:

  • A search-term redirect sends a shopper who enters a specific search term to a designated page.

  • A URL redirect sends a request for an old URL to a new URL, usually with an HTTP 301 or 302 response. The browser address bar changes to the new URL.

  • Search merchandising changes which products appear, or their order, in search results without changing the requested URL.

  • A URL rewrite maps one URL to another on the server. The Adobe Commerce URL Rewrite tool creates a permanent redirect (301) for the old URL. For more information, see URL rewrites.

Choose a routing capability

Use the following guidance to identify the capability that matches your requirement:

Requirement
Recommended capability
Send a specific query from standard Adobe Commerce search to a page
Configure a search term in Manage search terms, where supported.
Change product ranking or visibility in search results
Use Live Search synonyms or merchandising rules.
Redirect an old product, category, or CMS URL
Use the Commerce URL Rewrite tool when it applies to your deployment.
Redirect an Edge Delivery Services path
Use storefront or CDN routing.
Preserve legacy URLs after a storefront migration
Create and test a legacy-to-new URL redirect map.

With standard catalog search, you can configure a search term to open a content page, category page, product page, or external page where the deployment supports this capability. Use it when a shopper-entered query, such as gift cards or returns, must open a campaign or informational page.

To create or update this type of redirect, see Manage search terms. The search-term configuration is separate from the URL Rewrite tool because the trigger is the shopper’s query, not an existing URL.

NOTE
Confirm that the storefront uses standard catalog search and supports native search-term redirects. The behavior and available configuration can differ for Live Search, Adobe Commerce as a Cloud Service, or a headless storefront.

URL redirects and rewrites

Use a URL rewrite when the source is an existing URL rather than a shopper-entered search term. Common examples include redirecting:

  • An old product URL to a new product URL.

  • A retired category URL to a replacement category URL.

  • An outdated CMS page URL to a new content page URL.

For deployments that support the URL Rewrite tool, go to Marketing > SEO & Search > URL Rewrites to create the redirect. For step-by-step guidance, see URL rewrites.

NOTE
The URL rewrites topic applies to PaaS only. For Adobe Commerce as a Cloud Service or an Edge Delivery Services storefront, use the routing guidance for that storefront instead.

Live Search replaces the default storefront search experience and provides capabilities such as synonyms, facets, and merchandising rules.

Use Live Search when you need to change search relevance, product ranking, or product visibility. Use synonyms when different words should return similar products. Use merchandising rules when products must be boosted, buried, or ranked differently.

Live Search search behavior should not be treated as a drop-in replacement for every native Commerce search-term configuration. When a query must navigate to a content or campaign page, implement the redirect in the storefront or edge-routing layer that receives the request. For more information, see the Live Search documentation.

Edge Delivery Services

For a storefront powered by Edge Delivery Services, manage redirects in the storefront or edge-routing layer. Do not assume that Adobe Commerce Admin URL rewrites control every request.

When you use document authoring, maintain redirect mappings in the site’s redirect configuration. For redirects that must execute before a request reaches the origin, use the appropriate CDN or edge configuration. For related SEO guidance, see SEO guidelines for Commerce Storefront.

Migrate from Luma

Treat redirect migration as part of the storefront migration. Preserve the customer journey and SEO intent, then reimplement routing for the target storefront.

Before switching traffic to the new storefront:

  1. Export and inventory existing Luma URLs and search-term landing pages.

  2. Classify each item as a search-term redirect, URL redirect, or merchandising rule.

  3. Map every legacy URL to its new storefront path.

  4. Implement each redirect at the layer that receives the request.

  5. Test status codes, query parameters, canonical URLs, locale paths, and redirect loops.

  6. Monitor logs and analytics after launch for unresolved legacy URLs.

Troubleshoot redirects

Use the following checks when a redirect does not behave as expected across Adobe Commerce search, storefront routing, and store views.

Issue
What to check
A search term does not redirect
Confirm that the storefront uses standard catalog search, the search query matches the configured term, and the search term is assigned to the correct store view. If Live Search is enabled, verify that the redirect is implemented in the storefront or edge layer.
A redirect works on Luma but not on Edge Delivery Services
Confirm that the redirect is configured in the Edge Delivery Services storefront or CDN routing layer. Adobe Commerce Admin URL rewrites might not receive the request.
Live Search returns results instead of redirecting
Use Live Search rules for product ranking and visibility. For navigation to a content or campaign page, configure the redirect in the storefront or edge layer.
A redirect works in one store view but not another
Check the store view assigned to the search term or URL rule. Test the full locale path and query in each affected store view.

More help on this topic

recommendation-more-help
commerce-admin-help-merchandising-promotions