Redirects

You manage redirects on your storefront using a spreadsheet. No code changes are required.

Redirect behavior

Redirects override existing pages

If you create a redirect for a URL that already has a published page, the redirect takes precedence and the published page becomes unreachable at that URL. The page content is not deleted. Removing the redirect rule restores access if the page was still published. If it was unpublished, you also need to republish it.

The redirect sheet matches URL paths only. The Source column accepts a relative path, so query parameters are not part of the match. This means it cannot distinguish between URLs that differ only in their query parameters. For example, /search?q=shoes and /search?q=bags are both treated as the path /search. If you need to redirect specific search terms, ask your developer to set up search redirects instead.

The redirect sheet can hold up to 100,000 entries. See File and content limits if you are managing a large legacy catalog migration. Once your redirects are live, submit your sitemap to Google Search Console so search engines discover the updated URL structure faster.

Go deeper

See Redirects on AEM.live .