Create URL redirects
Redirect old paths through the site redirect loader and check query parameter behavior.
A redirect maps an old URL to a new destination. In Studio, redirects are content blocks listed under Content → Redirects. The running site must include the corresponding redirect loader for these blocks to take effect.
Add a redirect
- Open Content → Redirects and create a redirect.
- Set From to the source path, for example
/old-collection. - Set To to the destination, for example
/collections/summer. - Choose Temporary or Permanent.
- Decide whether to discard query parameters, then wait for autosave and publish.
Use a temporary redirect while the destination may change. Permanent redirects can be cached by browsers; verify the destination before using them. The reviewed editor labels temporary redirects as 307, while the v7 Worker runtime emits 302 for its temporary content redirects. Check the actual HTTP response for your runtime; see v7 redirect behavior.
Verify the result
Request the old path on the deployed site and inspect the status and Location header. Also test a URL with query parameters, such as /old-collection?utm_source=newsletter, to confirm the behavior you selected.
curl -I https://example.com/old-collectionIf saving a block has no effect after deployment, ask a developer to verify that the runtime discovers the saved redirect blocks. In the existing compatible app contract, the singular redirect block is consumed by the site's plural redirects loader.
A URL redirect does not configure a domain or certificate. Domain and apex redirect setup belongs to the hosting provider; the former managed-admin domain instructions are preserved in the legacy archive.
Implementation reference: Studio Site Editor. Reviewed 2026-10-05.