A domain redirect is the instruction that tells a browser where to go when someone visits a URL you no longer use as your main address. Setting one up correctly keeps visitors from hitting dead ends, protects your search rankings, and ensures your SSL certificate covers the destination properly. There are two main ways to redirect a domain, and which one you use depends on how much control you have over your hosting setup. A redirect is also different from a domain transfer, which moves ownership of the domain itself from one registrar to another. A redirect just sends visitors somewhere new. It does not change who owns or manages the domain.
What are the two main ways to redirect a domain?
Both methods accomplish the same goal. Someone visits one URL and ends up at another. The difference is where the redirect happens and how much control you have over it.
Domain forwarding at your registrar
Domain forwarding is set up inside your registrar account, the same place where you manage your domain registration. Your registrar handles the redirect before any request reaches your hosting server. You enter the destination URL, choose the redirect type, and the registrar does the rest.
This method requires no access to a hosting server and no code. It is straightforward and works well when you want to point a domain at a completely different website, forward a second domain to your main one, or redirect a domain you own but do not actively host.
The limitation is control. Registrar-level forwarding is typically less flexible. Some registrars only support basic redirects, and the options for setting up proper what a 301 redirect is and handling www and non-www versions separately may be limited depending on the provider.
Server-side redirect via your hosting control panel or config file
A server-side redirect is set up on the hosting server where your website runs. Depending on your setup, this is done through your hosting control panel, a configuration file, or your website platform's domain settings.
This method gives you full control. You can specify exactly what gets redirected, separate the www and non-www handling, set the correct redirect type, and layer it with your SSL setup. It is the preferred method when you are moving an entire website to a new domain and want to protect your search rankings in the process.
If you are unsure how domains and hosting connect, the chapter on domain vs hosting explains how the two work together.
When should you use domain forwarding vs. a server-side redirect?
The right method depends on what you are redirecting and how much control you need. Here is when each option makes the most sense. Registrar-level domain forwarding works best in these situations.
- You own a second domain and want to point it at your main site
- You have a domain you are not actively hosting and want to forward it somewhere
- You do not have access to your hosting server or control panel
- The redirect is simple and does not need to handle path-level logic
A server-side redirect is the better choice in these situations.
- You are renaming your brand and moving your entire website to a new domain
- You want to redirect specific pages or sections, not just the root domain
- You need to control how www and non-www versions are handled independently
- SEO is a concern and you need a clean permanent redirect to transfer ranking signals
What to check before you set up a redirect
Skipping pre-redirect checks is the most common reason things go wrong. Go through each of these before you do anything.
Confirm SSL is active on the destination URL
Before redirecting traffic anywhere, make sure the destination URL has a valid SSL certificate and loads over HTTPS. If someone is redirected from your old domain to a destination with no SSL, browsers will block the page or show a security warning. The redirect itself will not fix a missing certificate. Set up SSL at the destination first.
Verify the destination URL works correctly
Open the destination URL in a fresh browser tab before the redirect goes live. Check that it loads, that the page is the right one, and that the URL itself is not already redirecting somewhere else. A redirect chain, where URL A redirects to URL B which redirects to URL C, slows down page loads and weakens SEO signals. Keep the path direct.
Check your DNS settings
Domain redirects depend on DNS pointing correctly. Before setting up the redirect, confirm that the domain you are redirecting is still under your control and that its DNS records have not been changed in a way that would interfere. If you are using registrar-level forwarding, the registrar typically manages this automatically. For server-side redirects, your domain's nameservers must point to the correct hosting server.
How to redirect a domain using registrar-level forwarding
The exact steps vary between registrars, but the process follows the same pattern across all of them.
Step 1 - Log in and find the domain forwarding setting
Log in to your registrar account and navigate to the domain you want to redirect. Look for an option labeled Domain Forwarding, URL Forwarding, or Redirect. It is usually found in the domain management settings.
Step 2 - Enter the destination URL
Enter the full destination URL including HTTPS. For example, if you are forwarding an old domain to your main website, enter the complete address of your homepage or the specific page you want visitors to land on.
Step 3 - Choose the redirect type
Where your registrar gives you a choice, select a permanent redirect rather than a temporary one. A permanent redirect tells browsers and search engines that the move is final, which preserves any search rankings and signals associated with the old URL.
Step 4 - Set up forwarding for both www and non-www
A domain can be accessed two ways. Visitors might type www.yourdomain.com or just yourdomain.com. Set up forwarding for both versions. If only one version is redirected, anyone who types the other version will land on an error page. Most registrars let you configure both in the same forwarding settings.
Step 5 - Save and wait for DNS to update
Save your forwarding settings. DNS changes can take anywhere from a few minutes to 48 hours to fully propagate, though most registrar-level changes take effect within a few hours. Use a DNS checker tool to confirm the redirect is live before considering it done.
How to redirect a domain using a server-side redirect
Server-side redirects are set up in your hosting environment. The exact method depends on your hosting setup.
Step 1 - Access your hosting control panel or configuration
Log in to your hosting account and look for redirect settings, usually found in the domain or website management section. Some hosting platforms have a built-in redirect tool. Others require you to edit a configuration file directly, such as an .htaccess file on Apache servers.
Step 2 - Add the redirect rule
In the redirect settings, add a rule that maps the old domain to the new destination URL. Set the redirect type to permanent. If your hosting platform lets you configure redirects for www and non-www separately, set up both rules at this step.
Step 3 - Make sure SSL covers the destination
Before saving, confirm that your destination URL is loading over HTTPS. If you are moving your site to a completely new domain, you will need an SSL certificate set up and active at the new domain before the redirect goes live. Sending traffic to an HTTP destination can trigger browser warnings and break the redirect experience.
Step 4 - Test the redirect before announcing anything
Visit your old domain in a browser and confirm it lands at the correct destination. Check both the www and non-www versions. Use a redirect checker tool to confirm the response code is a permanent redirect rather than a temporary one. Only once both versions check out should you move forward with any communications or announcements.
What to check after the redirect is live
Test both www and non-www
Type both versions of your old domain into a browser and verify that both land at the correct destination. This is the single most common thing that gets missed after a redirect is set up.
Check for redirect chains
Run a redirect trace using a free online tool. You are looking for a clean single-hop redirect from your old domain to your destination. If the trace shows two or more hops, find and remove the intermediate step.
Verify the destination loads over HTTPS
Open the final destination URL and confirm the browser shows a secure connection. If there is a certificate warning, resolve the SSL issue at the destination before the redirect goes any further.
Check that email still works
A domain redirect does not affect email on its own, because email runs through DNS records that are separate from the redirect setting. However, if DNS changes were made as part of the redirect setup, double-check that your MX records are still pointing correctly. Send a test email to and from the domain to confirm delivery.
Common mistakes when redirecting a domain
- Redirecting to the wrong URL. Enter the destination URL carefully and test it directly before pointing any traffic at it. A typo in the destination address means everyone who visits your old domain goes nowhere useful.
- Forgetting SSL on the destination. A redirect that lands on an HTTP page or a page with an invalid certificate will trigger browser security warnings. Set up SSL at the destination before activating the redirect.
- Only setting up the redirect for one version. If www.yourdomain.com redirects correctly but yourdomain.com does not, or the other way around, half your traffic hits a dead end. Always configure both versions.
- Creating a redirect chain. If the destination URL already redirects somewhere else, fix the chain by pointing the first redirect directly to the final destination.
- Using a temporary redirect instead of a permanent one. Temporary redirects do not transfer search engine signals. If the move is permanent, use a permanent redirect type from the start.
- Not checking email after the redirect. DNS changes made during a redirect setup can accidentally affect MX records. Always verify email is working after any DNS change.
How WEMASY handles domain redirects
When you connect a custom domain to a WEMASY website, WEMASY handles SSL automatically for that domain. If you want to redirect an old domain to your WEMASY site, you set up forwarding at your registrar pointing to your WEMASY domain. WEMASY takes care of the SSL and the hosting side. No server configuration needed on your end. See what is included with each plan at WEMASY pricing.
Frequently asked questions
How long does a domain redirect take to work?
Registrar-level domain forwarding usually takes effect within a few hours, though DNS propagation can take up to 48 hours in some cases. Server-side redirects that do not require DNS changes tend to take effect almost immediately. Use a DNS propagation checker to confirm when the redirect is active in your region. With WEMASY's website builder, you can set this up directly on your website.
Can I redirect a domain to a subdomain?
Yes. You can redirect a domain to a subdomain such as store.yourdomain.com or blog.yourdomain.com. The process is the same as redirecting to any other URL. Enter the full subdomain address as your destination, make sure it has SSL active, and set up the redirect for both www and non-www versions of the source domain.
Will redirecting a domain affect my SEO?
A permanent redirect signals to search engines that the move is final and passes the ranking signals from the old URL to the new one. If set up correctly, a permanent redirect preserves most of the SEO value associated with your old domain. A temporary redirect does not transfer those signals, so if the move is permanent, always use a permanent redirect type.
Do I need to redirect both www and non-www versions?
Yes. Visitors can reach your domain by typing it with or without www in front, and each version is treated as a separate URL. If only one version is set up with a redirect, anyone who types the other version will land on an error page. Always configure both versions as part of your redirect setup.
What happens to my email when I redirect a domain?
A domain redirect on its own does not change your email. Email delivery depends on MX records in your DNS, not on the redirect itself. As long as your MX records are not changed during the redirect setup, your email continues working normally. If DNS changes were made alongside the redirect, check your MX records and send a test email to confirm everything is still routing correctly.
The next chapter covers what domain authority is and how it affects where your domain ranks in search results.