Notes from the pond
Guides to moving domains without losing traffic, and write-ups of how we run the redirect edge.
Rediray is now RedirectDuck
A new name and a new home for the project behind Rediray. September 18 marks the beginning of redirectduck.com.
Redirect chains and loops: how to find and fix them
Trace the difference between an extra hop and a loop, shorten configured chains, and check where automatic rule testing stops.
Keeping UTM parameters when redirecting a URL
Control whether incoming query parameters follow a redirect, understand duplicate keys, and test the exact URL your destination receives.
Wildcard redirects: preserve paths without writing hundreds of rules
Use a trailing wildcard and $1 to move a group of paths, then add exact exceptions and test how the rules interact.
Why your old domain still needs HTTPS
A browser must establish HTTPS with the old hostname before it can read its redirect. Check the source certificate as well as the destination.
Domain forwarding vs DNS: what actually changes?
DNS gets a request to a server. A redirect tells the browser where to go next. Here is how the two fit together when you connect an old domain.
A checklist for consolidating client domains
Audit a client's old domains, organize access, build tested redirect mappings and prepare a report with the limits of the data made clear.
Finding the old links that still get traffic
Use per-rule analytics and unmatched 404s to find old URLs worth maintaining, then export retained events or query summaries through the API.
A practical checklist for moving a domain
Map old URLs, configure redirect rules, verify DNS and HTTPS, and monitor the requests that arrive after a domain move.
301, 302, 307 or 308: which redirect to use
A practical guide to the four redirect codes supported by RedirectDuck, including permanent moves, temporary changes and request methods.
One email a month
New posts from the pond. No tracking pixels. Unsubscribe at any time.