See the product in action. ― Book a free demo →
All guides
Browse all guides
Documentation
Site settings

Set up redirects and move a site gradually

Send old URLs to new pages or keep unmoved pages available through an existing site origin.

Choose the right behavior

Open Settings → Redirects. A redirect sends visitors to a destination and changes the browser address. A rewrite retrieves a response from another origin while retaining the public address. These settings affect live routing after saving; they are not waiting for a page design publish.

Add a redirect

  1. Choose Add Rule and select Redirect.
  2. Set the source path, such as /old-service, and destination, such as /services.
  3. Choose 308 for a permanent move or 307 for a temporary move.
  4. Decide whether the rule includes subpaths. If it does, choose whether to preserve the remaining path structure.
  5. Save the rule and test an exact URL and a nested URL if applicable.

For example, a rule from /news to /blog with subpaths included and preserved can send /news/product-update to /blog/product-update. Check that the destination pages actually exist.

A published page using the source path can block a rule. Read the displayed conflict and adjust the page or source path. Review rule ordering when more than one rule could apply, and avoid redirect loops.

Use a rewrite only when needed

A rewrite requires an absolute HTTP or HTTPS destination. It serves another origin behind your site address and is different from moving visitors to that address. Confirm that the upstream site supports the intended URLs and that its resources and links work correctly.

Progressive site migration

Use progressive migration when only part of an existing website has moved to Neopress:

  1. Keep the previous website available at another origin, such as legacy.example.com.
  2. Connect the original domain, such as example.com, to Neopress.
  3. In Redirects, configure Progressive site migration with the separate existing-site origin.
  4. Publish the pages that should be served by Neopress.
  5. Test both a moved URL and an unmoved URL. The public address should stay on the original domain.

The fallback origin must not send requests back to Neopress. Existing site logins, forms, cookies, scripts, or other application behavior need separate testing; routing a response does not migrate those systems.

Plan access

Redirect and migration features require an eligible paid-plan feature set, including an active Launch trial. If the site becomes archived, saved rules can remain while their execution is paused. Review the plan status when an existing rule stops applying.

Related guides