Create a redirect in the dashboard, enter the domain you want to redirect and where it should go, then point that domain's DNS to RedirHub. As soon as the DNS change is detected, the redirect goes live and HTTPS is issued automatically. A root domain such as example.com also covers www.example.com.
This guide walks you through your first redirect, from signing up to a working HTTPS redirect. All you need is a domain you own and access to its DNS settings. New to RedirHub? Start with What is RedirHub?.
Step 1: Create an account or log in#
Go to the RedirHub dashboard and sign up or log in. The 14-day free trial is enough to follow this guide.
Step 2: Enter the URLs to redirect from#
Open Redirects, click New redirect and choose Single import. Enter the domain or URL you want to redirect, for example old-domain.com. You can add several URLs at once if they should all go to the same destination. Then click Next.
You don't need to add www separately. A redirect for example.com also handles www.example.com, including the same paths, as long as www also points to RedirHub in DNS (Step 4).
Add www as its own source only when it should go somewhere different from the root domain. The root domain and its www version count as one domain on your plan.
Moving many URLs, for example during a website migration? Choose Import from CSV instead and upload all your redirects in one go.
Step 3: Set the destination, method and forwarding#
- Destination: the full URL visitors should land on, for example https://www.new-domain.com. Use Add destination if you want to split traffic across several URLs.
- Method: 301 for permanent moves, 302 while you are testing. See Redirect Methods Explained for Frame, Custom HTML, 307 and 308.
- Forwarded Options: turn on Path forwarding to keep the path (old-domain.com/about → new-domain.com/about) and Query forwarding to keep parameters such as UTM tags. For more control, see Destination URL Variables.
Click Create. The redirect is saved and starts working as soon as DNS points to RedirHub.
Step 4: Point your DNS to RedirHub#
Click View redirects, then Check DNS next to your domain. The dashboard shows the Required DNS Values next to what is currently set. Log in to your DNS provider and update the records to match:
- Root domain (example.com): an A record, plus the TXT record shown for verification.
- Subdomains, including www (www.example.com, go.example.com): a CNAME record.
- Remove any other A, AAAA or CNAME records for the same names, otherwise some visitors keep reaching the old server.
More detail in What DNS changes are needed. Provider guides: GoDaddy, Cloudflare, Namecheap and more in the Support center.
Step 5: Wait for DNS verified and HTTPS#
DNS changes can take up to 24 hours to spread, and RedirHub detects them automatically. When your domain shows DNS verified, the redirect is live. The SSL certificate is then issued on its own and the status changes to Secured. See How long does the DNS change take? and Automatic HTTPS.
Step 6: Test your redirect#
Open your old URL in a private browser window and check the homepage, a deeper page, and the www version. If something doesn't work yet, see Troubleshooting new redirects.