Build a small test set before changing rules

Write down the old URL, intended destination, expected status, and any query values that must survive. Choose a representative page for each rule family, including host or scheme normalization, slash normalization, and an actual content move. Include one URL that should still return 404.

Record the current responses with the browser Network panel and Preserve log enabled. The Redirect Checker can inspect public GET hops when its API is configured. A browser may also follow a JavaScript redirect or show a cached result, so compare like-for-like observations before concluding the server rules differ.

Try the Redirect Checker →

Trace each Location to the next response

A chain keeps moving through intermediates. A loop returns to an earlier URL and never reaches its destination. For example, a host rule can add www while a separate application rule removes it. Look at the actual Location response at the transition where the URL starts repeating.

In this example the old link moves through an intermediate path. Change the rule serving the old path to point directly to the final help page. If another rule must still normalize the host, make sure both rules agree on the final host and path.

Before: /support/shipping/ → /help/shipping → /help/delivery/
After:  /support/shipping/ → /help/delivery/
Final:  /help/delivery/ returns 200

Try the HTTP Headers Checker →

Choose the status for the move

Use 301 or 308 for a permanent move and 302 or 307 for a temporary change. For requests with a body, 307 and 308 preserve the method, while user agents may change POST to GET after a 301 or 302. Test write routes in staging using the actual client contract before changing their behavior.

Map old pages to useful equivalents. A removed item with no substitute can return the intended error status. Sending every discontinued URL to the homepage makes it hard for visitors to find the expected information.

Retest the migration and update its references

After changing one rule family, replay the test set in a fresh session. Check the final status, host, content, and any query fields that matter. Update internal links, canonicals, and sitemap entries to the destination so new visits avoid the legacy path. Keep the old redirect in place while old links still need it.

  • Collect each hop and its Location.
  • Verify the destination answers the same user need.
  • Test both a working old link and a deliberate 404.
  • Record which proxy, host, or app owns the final rule.

References and further reading