Create a 302 Redirect in Umbraco with umbracoRedirect

umbracoRedirect is a reserved property alias used with a Content Picker. When a request reaches the source node, Umbraco sends the browser to the selected content item with a 302 Temporary Redirect.

In this example, an old campaign page is the redirect source and the current campaign page is the target. The setup makes the resulting HTTP behavior easy to verify.

Add a Content Picker to the relevant Document Type and set its alias to exactly umbracoRedirect. Give editors a description that explicitly says this creates a temporary 302 redirect.

On the source node, select the destination content item and publish. Avoid self-references and circular redirect chains.

Do not stop at “the browser ended up on the right page.” Open the Network panel and confirm the source request returns 302 and a Location header pointing at the intended destination.

A temporary redirect and Umbraco's historical redirect tracking solve different problems. A 302 tells clients and search engines that the redirect is temporary. For a permanent legacy URL move, Google recommends a server-side permanent redirect such as 301 or 308 when possible. In an Umbraco migration, use a mechanism that produces the permanent HTTP behavior you actually intend rather than using umbracoRedirect simply because it is built in.

For bulk legacy migrations, see how I import and verify Umbraco redirect URLs as HTTP 301 responses. Google also documents permanent redirect best practices for site moves.

Use umbracoRedirect when the browser should navigate to another URL. Use umbracoInternalRedirectId when the original URL must stay visible while another node's content is rendered.