Managing URL redirects

Use URL redirects to send visitors from an old or broken storefront address to its replacement. A saved rule returns a permanent (301) redirect when the old path would otherwise show a page-not-found error.

For example, redirect /old-collection to /collections/summer after moving a collection. Check that the destination exists and is available to shoppers before sharing the old link.

Open and find redirects

1. Sign in as the owner or with Themes permission.
2. Open Menus under Online Store, then click URL redirects.
3. When records exist, use Search redirects to search the Redirect from or Redirect to value.
4. Use Sort to arrange by Redirect from, Redirect to, or Created. Use the page controls for additional results.
5. Open a row, or choose Edit in its actions menu, to change a rule.

This is the actual demo list. Select any image to enlarge it.

Create a redirect

1. Click Create redirect.
2. In Redirect from, enter the old store path, such as /old-collection.
3. In Redirect to, enter the replacement store path, such as /collections/summer, or a complete https:// or http:// URL for another website.
4. Check both values, then click Save in the modal.
5. Find the saved rule in the list and test its old address on your storefront.

This is an unsaved example; no redirect was created for the screenshot.

The source is a path in your store, not a rule for another domain. Use a leading slash for clarity. Source paths are normalized to lowercase, with trailing slashes removed; if you paste a full source web address, its host is discarded and its path is used. For example, /Old-Collection/ is stored as /old-collection.

The form supports up to 500 characters for Redirect from and 1,000 for Redirect to. The same source path can have only one rule. If it already exists, edit that rule rather than creating another one. A local path cannot redirect to itself.

Use the final destination directly and check that it does not lead back to the old address through another rule. A destination is not guaranteed to exist simply because the redirect saved successfully.

Understand automatic redirects

Changing a saved product, collection, custom page, or blog post's URL handle creates a redirect from its old path to its new path automatically. A title change that leaves the handle unchanged does not create an old-to-new URL move.

Review these rules in the same URL redirects list. You can edit or delete them like manually created rules. Later handle changes can also update redirects that pointed to the previous address so they follow the new address.

This automatic behavior covers those four content types. For another changed address, including a blog category handle, review the old URL and create a rule manually if needed.

Edit and test a rule

Open its row or choose Edit in the actions menu. Change Redirect from or Redirect to and click Save. An unchanged rule has Save disabled. Editing Redirect from moves the rule to the new source; it does not leave a second rule at the previous source.

Test the complete old URL using the storefront domain, then check the final address and content. A 301 can be remembered by a browser, so use a fresh browser session when checking a changed rule if you still see its old destination.

For sources with a query string, such as /old-page?campaign=summer, an exact saved source is tried first. If there is no exact query-specific rule, a rule for /old-page can apply. The destination is the saved Redirect to value; do not assume the old query parameters will be added to it automatically.

If a real page later becomes available at the old path, that page takes precedence. A saved redirect row does not prove it is currently being used.

Import redirects from CSV

Use Import for several rules or to update existing targets in a batch.

1. Click Import and use Download sample to get the expected file structure.
2. Prepare a CSV with both headers: Redirect from and Redirect to. Each row is one rule.
3. Select the CSV to open its preview grid.
4. Check the column mappings and row values. Correct or exclude unwanted rows and resolve marked errors before proceeding.
5. Click Start import only when ready to save the rules. The action checks the data and can start the import immediately when it passes. If warnings are shown, review them before continuing.
6. Review the completed result, including created, updated, skipped, and failed rows. Correct remaining problems and check the saved list.

Example CSV:

Redirect from,Redirect to
/old-page,/pages/new-page
/old-collection,/collections/summer

Normal source, destination, existing-page, and self-redirect checks also apply to imported rules. Do not treat an import with errors as proof that every row was saved.

Export redirects

Click Export to open Export URL redirects. The preview contains the store's redirects, rather than only the current search results or current list page. Review the rows and columns to include, then click Export to download the CSV. Export is disabled when nothing is available or selected.

Keep both Redirect from and Redirect to columns if the file will be imported again. Excluding one can produce a useful reference file, but it cannot be imported as a complete set of rules without restoring the required column.

Export reads your rules and downloads a file; it does not change their targets. If list selection controls are hiding the Import/Export buttons, use Discard to clear the selected rows first.

Delete redirects

Choose Delete in a row's actions menu, or select several rows on the current page and use Delete in the selection controls. Review the count and confirm only when ready. Changing page, search, or sort clears the current selection.

Troubleshooting