← All posts
Product17 Nov 2026 · 3 min read

Changing redirect rules safely: testing, history and rollback

Use a repeatable checklist for redirect edits, understand what a stored revision restores and verify the live result after every change.

RedirectDuck team
RedirectDuck mascot

Changing a redirect can be a small edit with a wide effect. A wildcard rule may handle many paths, and a familiar old URL may still be used in a campaign or customer document.

A repeatable check is more useful than relying on memory when you change the destination.

Write down the expected result

Before editing, capture the current source, destination, status code and forwarding settings. Select a few URLs that represent the rule's work:

  • One ordinary path.
  • A nested path if the rule uses a wildcard.
  • A URL with query parameters.
  • An exact exception that should keep its own destination.

Record where each should end up. This list makes the review concrete and helps someone else check the same change.

Check the mapping and the live request

Use Rule tester to inspect the configured result. After saving an edit, run the same test cases again and compare the resolved destinations.

Then request the actual source URLs over HTTP and HTTPS. A rule match in the tester does not establish that public DNS has reached the edge, that a certificate is valid, or that the destination website serves the expected page.

Configuration synchronization also takes time. Check the live result instead of assuming that a save and an edge update are the same event.

Use history on Pro and Agency

The History & rollback page records configuration revisions. A stored revision includes the source, destination, status code, path and query forwarding, wildcard behavior, matching mode, enabled state and tags.

Choose the revision representing the configuration you want to restore. Restoring it creates a new change in history, keeping a record of the reversal rather than erasing the intervening edit.

The restore is validated against the workspace's current rules and limits. For example, a conflicting source or a missing domain can prevent a formerly valid configuration from being restored.

Know the boundary of a restore

Rule rollback changes RedirectDuck's rule configuration. It does not restore a DNS zone, undo changes to the destination website, renew a domain registration or remove responses already cached in a visitor's browser.

If you are correcting a bad permanent redirect, test with an HTTP client as well as your normal browser. An old cached result can make the server's current behavior harder to see.

Prefer small changes you can verify

For several edits, use a reviewed import or a manageable batch and keep the test URLs alongside it. Avoid combining a DNS change, a website move and a large rule rewrite unless the migration plan accounts for all three.

After a rollback, repeat the same tests used for the original change. The useful outcome is a working route for visitors, not simply a successful restore message.

Point your old domain at us

One DNS record, HTTPS included. Free for your first domain.

Start for free