---
schema_version: "1"
id: 810e878e15f7215fd05b20b96b576da1939a8b3235b65f646c9adad8f9aa35d1
title: Automatic 301 Redirects for B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_automatic_301_redirects.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_automatic_301_redirects.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0df629ac3c2490b89e6c00287ba157f97773c6955c43f74655ac2bac57381b0f
description: A 301 redirect is the HTTP status code for a permanent URL redirection that also passes page ranking power to the redirected page. In most instances, a 301 redirect is the best method for implementing redirects in your storefront.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Automatic 301 Redirects for B2C Commerce

A 301 redirect is the HTTP status code for a permanent URL redirection that also passes page ranking power to the redirected page. In most instances, a 301 redirect is the best method for implementing redirects in your storefront.

B2C Commerce handles requests for URLs that have changed by determining whether the URL is an SEO URL and if the URL matches the expected SEO URL for the product. If the URL has changed, B2C Commerce automatically creates a 301 redirect, which preserves page rankings for products and content, even if their properties change.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note If you remove a product or content item, no redirect is created and it's possible to redirect the customer to a different page. See [Creating a Redirect from a B2C Commerce URL](https://help.salesforce.com/s/articleView?id=cc.b2c_creating_a_redirect_from_a_digital_url.htm&release=264.0.0&type=5 "The URL redirects feature redirects obsolete or unavailable B2C Commerce pages to currently available pages, or to a specific URL outside B2C Commerce. You can also schedule when a redirect becomes active and when it expires.").

## Out-Dated Storefront URL Mappings

Out-dated storefront URL mappings are handled as follows:

- Product/Content: if a request with an SEO URL references a product or content that isn't up to date because the mapping syntax changed recently (or the URL path was changed manually), the URL automatically redirects to the current product/content URL mapping. This uses the mandatory product/content ID part in the URL path and works for all instance types.
- Category/Folder/Pipeline: requests that are mismatched regarding the configured trailing-slash are automatically redirected. Out-dated URL redirect mappings are only enabled for Staging and Production instances. See [URL Archive](https://help.salesforce.com/s/articleView?id=cc.b2c_using_the_seourls_url_archive_tab.htm&release=264.0.0&type=5 "The URL Archive redirects out-dated URL mappings to the current URL mapping (as defined in your category and folder URL rules section) on your B2C Commerce Staging and Production instance. When out-dated redirects, initiated by the archive, become obsolete (for example, because a category was deleted or because of ID changes), remove them from the URL archive tab. Search for the URL path or object ID.").

## Search Refinement URLs

To avoid duplicate content, the automatic HTTP 301 redirect handling for search refinement URLs redirects out-dated URL mappings to the current URL mapping, for the following cases:

- URL contains an unmapped and enabled URL search refinement in the query string, for example, `/shoes/?prefn1=color&prefv1=blue` redirects to `/blue/shoes/`.
- URL contains multiple URL search refinement mappings with incorrect order, for example, `/blue/abrand/shoes/` redirects to `/abrand/blue/shoes/`.
- URL contains multiple URL search refinement values with incorrect order,for example, `/second-refinement|first-refinement/electronics/` redirects to `/first-refinement|second-refinement/electronics/`.
- URL doesn't contain a configured constant, for example, `/abrand/blue/shoes/` redirects to `/abrand/constant/blue/shoes/`.
- URL contains the `Search-Show` pipeline alias but is configured to be excluded, for example, `/abrand/blue/search/` redirects to `/abrand/blue/`.