Direct Answer
Create a domain redirect from old-domain.com to https://new-domain.com, choose 301 and Keep the path, and turn on Query forwarding under More options. Then point old-domain.com's DNS to RedirHub. Every URL on the old domain now lands on the same path on the new one, with its query string.
| Item | Details |
|---|---|
| Goal | old-domain.com/any/path?x=1 → https://new-domain.com/any/path?x=1 |
| You need | A RedirHub workspace (the 14-day trial is enough) and access to old-domain.com's DNS |
| Redirect type | 301 Permanent |
| Time | About 5 minutes, plus DNS propagation |
Steps#
- In Links, click Create and choose Domain Redirect.
- Redirect from: old-domain.com. Use Add another source if more domains should go to the same place. A root domain also covers its www version.
- Redirect to: https://new-domain.com.
- Choose 301 Permanent and, under Paths, Keep the path.
- Open More options and turn on Query forwarding.
- Check the What happens panel, then click Create redirect.
- Open Connect DNS for old-domain.com and add the records it shows (an A record for the root, a CNAME for www). HTTPS is issued automatically once DNS is in place.
Result#
| Request | Response | Lands on |
|---|---|---|
| https://old-domain.com | 301 | https://new-domain.com/ |
| http://www.old-domain.com/blog/post-1 | 301 | https://new-domain.com/blog/post-1 |
| https://old-domain.com/shop?utm_source=newsletter | 301 | https://new-domain.com/shop?utm_source=newsletter |
Variations#
- Some URLs moved: add path links such as old-domain.com/about-us → https://new-domain.com/about. A path link wins over the whole-domain redirect; everything else keeps its path. See Matching.
- Send everything to one page instead: choose Everything to one URL under Paths.
- Move the content into a folder, for example old-domain.com/about → new-domain.com/old-brand/about: choose Everything to one URL under Paths and put the variable in the destination yourself, https://new-domain.com/old-brand{path}. See Destination URL Variables.
- Every subdomain too (shop.old-domain.com, blog.old-domain.com): use a wildcard source on Pro; see Wildcard Subdomains.
- Many domains at once: import them with a CSV file.
Frequently asked questions
Yes, when Query forwarding is on. old-domain.com/page?utm_source=x then lands on new-domain.com/page?utm_source=x.
No. The old domain only needs DNS records that point to RedirHub; RedirHub answers the requests and issues HTTPS.
With Keep the path they land on the same path on the new domain, which may be a 404 there. Add path links for URLs that changed, or use a website migration to map them.