Redirecting one domain to another is a common and useful task: it sends anyone who visits one domain automatically to a different one, so you can consolidate a brand, point secondary extensions at your main site, forward an old domain to a new one, or capture typo traffic. It is straightforward to set up, but getting the details right — especially using the correct type of redirect — matters for both visitors and SEO.

This guide explains how to redirect a domain to another: what a redirect is, the crucial difference between permanent and temporary redirects, the methods available (registrar forwarding, DNS, or server-side), a step-by-step, common uses, and the SEO best practices to follow. By the end you will know how to set up a clean, effective domain redirect.

What a domain redirect is

A domain redirect — also called URL forwarding — automatically sends visitors from one domain to another. When someone types or clicks the source domain, their browser is immediately taken to the destination domain instead, without them having to do anything. It is the mechanism behind consolidating domains, forwarding old addresses, and pointing extra extensions at a main site.

So a redirect is essentially a rule that says “whenever someone comes to this domain, send them to that one.” The source domain does not host its own content; it simply forwards everyone to the destination, which is where your actual site lives.

Redirects are widely used because domains often need to funnel to a single canonical site: secondary extensions, misspellings, rebranded addresses, and old domains all commonly point to one main destination. Understanding how to set one up — and which type to use — lets you manage all of these cleanly.

Permanent vs temporary redirects

The most important distinction in redirects is between permanent and temporary, because it affects both behaviour and SEO. A 301 redirect is permanent: it tells browsers and search engines that the move is permanent, and crucially, it passes the source domain’s authority and link equity to the destination. This is the SEO-friendly choice for lasting redirects.

A 302 redirect is temporary: it signals that the redirect is only for now and the original may return, so search engines generally do not transfer authority to the destination. It is appropriate only when the redirect genuinely is temporary — for example, during short-term maintenance.

For almost all domain-to-domain redirects — consolidating a brand, forwarding secondary extensions, moving to a new domain — you want a permanent 301 redirect, because it both sends visitors correctly and preserves your SEO value by passing authority to the destination. Using a 302 by mistake for a permanent move can cost you rankings, so choosing the right type is essential.

The methods to redirect a domain

There are a few ways to set up a domain redirect, and the easiest depends on your setup. Here are the main methods:

• Registrar or host forwarding: the simplest method — most registrars and hosts offer a domain forwarding feature where you set the source domain to redirect to a destination in your domain settings.
• DNS-level forwarding: some providers offer forwarding configured through DNS, achieving the same redirect.
• Server-side redirect: for more control, you can set up the redirect on your web server — for example, using rules in a configuration file (like .htaccess) or your hosting control panel’s redirect tool.

For most people, the registrar or host forwarding feature is the easiest and perfectly sufficient — a couple of clicks in your domain settings. The server-side method offers more control and is useful when you are redirecting specific paths or need fine-grained rules. All achieve the same core result: sending visitors from one domain to another.

How to set up a redirect: step by step

Using the most common method — your registrar or host’s forwarding feature — setting up a domain redirect is quick. First, log in to the account where the source domain (the one you want to redirect) is managed.

Find the domain forwarding or redirect option in your domain settings, select the source domain, and enter the destination domain you want visitors sent to. Choose a permanent (301) redirect for a lasting move, and if the option is available, ensure it covers both the bare domain and the www version. Save the change.

After saving, allow a little time for it to take effect (and for any DNS to propagate), then test it by visiting the source domain and confirming you are sent to the destination. That is the whole process for a standard domain-to-domain redirect. For server-side redirects, you would instead add the appropriate redirect rule in your server configuration or your host’s redirect tool, but the forwarding feature covers most needs simply.

Common uses for domain redirects

Domain redirects solve a range of everyday needs, most involving funneling traffic to one main site. Here are the most common.

In each case, a permanent 301 redirect sends both visitors and search engines to your one canonical destination, consolidating traffic and authority. Whether you are rebranding, protecting your name across extensions, catching typos, or standardizing on a www or non-www version, the redirect is the tool that unifies everything onto a single main site.

SEO best practices for redirects

Redirects have real SEO implications, so a few best practices keep them clean. First and foremost, use a 301 (permanent) redirect for any lasting move, so that authority and link equity transfer to the destination — this is what preserves your rankings when consolidating domains or moving to a new one.

Second, avoid redirect chains and loops. A chain (domain A redirects to B, which redirects to C) adds delay and can dilute the benefit, so redirect directly to the final destination. A loop (redirects that circle back) breaks entirely. Point each source straight to the final target.

Third, be consistent about your canonical version — decide whether your main site is the www or non-www form and redirect the other to it, so you have one definitive address. Following these practices ensures your redirects both work smoothly for visitors and pass your SEO value cleanly to your canonical destination, rather than leaking authority or creating confusion.

Verifying your redirect works

After setting up a redirect, verify it behaves correctly. Visit the source domain in your browser and confirm you are automatically taken to the destination — test both the bare domain (sourcedomain.com) and the www version (www.sourcedomain.com) if you set up both, to make sure all forms redirect properly.

For SEO-sensitive redirects, it is worth confirming that the redirect is a 301 (permanent) rather than a 302, which you can check with a redirect-checking tool that shows the redirect type. This ensures authority will transfer as intended, especially important when you have moved to a new domain and want to preserve rankings.

If the redirect does not work immediately, allow for propagation and any caching to clear, then test again in an incognito window or on another network. Once confirmed, your redirect runs automatically, quietly sending everyone from the source domain to your destination. A quick verification is worth it to be sure the forwarding — and its type — is set up exactly as you intend.

FAQs

How do I redirect one domain to another?

The easiest way is your registrar or host’s domain forwarding feature: log in where the source domain is managed, find the forwarding/redirect option, select the source domain, enter the destination, choose a permanent (301) redirect, cover the www version too, and save. Then wait briefly and test. Server-side redirects are an alternative for more control.

What’s the difference between a 301 and 302 redirect?

A 301 is permanent — it tells search engines the move is permanent and passes the source’s authority and link equity to the destination, making it the SEO-friendly choice for lasting redirects. A 302 is temporary and generally doesn’t transfer authority, appropriate only when the redirect really is short-term, like brief maintenance. Use 301 for permanent domain moves.

What are the ways to redirect a domain?

Registrar or host forwarding (the simplest — a setting in your domain management), DNS-level forwarding (offered by some providers), or a server-side redirect (rules in a config file like .htaccess or your host’s redirect tool, for more control). For most domain-to-domain redirects, the forwarding feature is easiest and perfectly sufficient.

What are domain redirects used for?

Common uses: consolidating a rebrand (old domain to new), pointing secondary extensions (yourbrand.net/.org to yourbrand.com), capturing misspellings (typo domains to your main site), and standardizing on a www or non-www version. In each case a 301 redirect funnels visitors and search authority to your one canonical destination.

Do domain redirects affect SEO?

Yes. Use a 301 (permanent) redirect so authority and link equity transfer to the destination, preserving rankings when you consolidate or move domains. Avoid redirect chains (which add delay and dilute the benefit) and loops (which break entirely), and be consistent about your canonical www or non-www version. Done right, redirects pass SEO value cleanly.

How do I check my redirect is working?

Visit the source domain and confirm you’re sent to the destination, testing both the bare and www versions. For SEO, use a redirect-checking tool to confirm it’s a 301 (permanent) rather than a 302. If it doesn’t work immediately, allow for propagation and caching, then retest in an incognito window or another network.

The bottom line

Redirecting one domain to another automatically sends visitors from a source domain to a destination, and it is the tool behind consolidating a rebrand, pointing secondary extensions at your main site, forwarding an old domain to a new one, and capturing typo traffic. Setting one up is usually as simple as using your registrar or host’s domain forwarding feature — select the source, enter the destination, and save — though server-side redirects offer more control when you need it. The single most important detail is the redirect type: use a permanent 301 for any lasting move, because it both sends visitors correctly and passes your authority and link equity to the destination, preserving your SEO value.

Follow a few best practices and your redirects stay clean: choose 301 for permanent moves (302 only for genuinely temporary ones), avoid redirect chains and loops by pointing straight to the final destination, and standardize on one canonical www or non-www version. Cover both the bare and www forms, then verify by visiting the source domain and, for SEO-sensitive moves, confirming the redirect is a 301 with a checking tool. Set up correctly, a domain redirect runs automatically and funnels all your traffic and authority to a single canonical site — exactly what you want when unifying domains onto one main destination.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. Redirect a domain via your registrar/host forwarding feature (or a server-side rule): point the source to the destination, use a permanent 301 (passes SEO authority; 302 is temporary), cover the www version, avoid chains and loops, and verify with a redirect checker.