How To Redirect A Website To Another Domain (The Complete 2026 Guide)

Redirecting a website to a new domain can affect everything from search rankings to how users reach your pages. The process seems simple, but small decisions such as redirect type, hosting setup and timing determine whether the move feels cohesive or disruptive. 

A clear redirect plan protects traffic, transfers authority and keeps navigation intact while you transition.

A good redirect setup comes down to knowing which type of redirect to use, how your server handles it, and what needs to happen before, during and after the switch. 

With the right workflow, you can move a site, consolidate domains or migrate platforms without losing momentum.

Why you may need to redirect your website

Redirects come up any time your old URLs shouldn’t remain the final destination. The most common situations include:

• Rebranding to a new business or product name
  Redirect the old domain to the new one so customers don’t hit dead ends.
  
  
• Switching to a shorter or more memorable domain
  Short domains improve shareability and are easier to market.
  
  
• Merging two or more sites into one
  Combine authority instead of splitting backlinks and rankings.
  
  
• Moving from HTTP to HTTPS
  Redirecting protects security signals and avoids mixed-content issues.
  
  
• Changing CMS or hosting platforms
  If URLs change during a migration, redirects keep equity flowing to the right place.
  
  
• Shifting from a country domain to a global domain
  Example: example.co.uk → example.com, while still serving localized versions.
  
  
• Cleaning up URL structure
  Old long-form URLs can redirect to shorter, more organized paths.
  
  
• Avoiding duplicate content
  If the same page exists in multiple places, redirect one canonical version.

How website redirects work

A redirect tells a browser or search engine that the content requested now lives somewhere else. When someone visits oldsite.com/page, the server can automatically forward them to newsite.com/page instead, keeping the experience seamless.

Redirect types (and how search engines treat them)

Why 301 is recommended for migrating domains

A 301 tells search engines “treat the new URL as the permanent home.”
This means:

• Link equity transfers more reliable
• Rankings move faster to the new domain
• Fewer long-term indexing issues and cannibalization
• Google updates the canonical version automatically

302/307 are useful for testing or short-term redirects, but they don’t send the same longevity signal. For a domain move, 301 is the safest way to protect traffic and authority.

Server-side redirects

These happen before the page loads. They’re reliable, fast, and the best option when moving to a new domain. Commonly configured in Apache (.htaccess), NGINX, or hosting panels.

Client-side redirects

Triggered by JavaScript after the page begins to load. Useful when redirecting based on language, cookies or behavior, but slower and not ideal for SEO-sensitive migrations.

JavaScript example:

if (userCountry === 'FR') {
  window.location.href = 'https://example.com/fr';
}

Why redirect timing matters

A redirect should fire instantly. Any delay creates flicker, hurts UX, and may stop search engines from following the new URL. Server-side is preferred for migrations because it redirects before content loads.

How to choose the right redirect method

Not every redirect works the same way. The best setup depends on how your site is hosted, whether you need to preserve URL paths, how permanent the change is, and whether the redirect needs to work across subdomains or multiple regions.

Factors to consider before choosing a method

• Hosting environment and server access
• Whether you need to preserve paths and query strings
• Subdomain support (www, blog.example.com, app.example.com)
• HTTPS and SSL configuration on both domains
• Whether you need global or location-based redirects

If you only need to move everyone from one domain to another, a simple registrar or DNS redirect might work. If you need SEO retention and path preservation, go server-level. If you want regional or device-based rules, a geo redirect tool gives you more flexibility.

Registrar vs. DNS vs. server vs. CMS redirects

A simple way to pick the right method

Choosing the right method early saves you time later, especially if you need SEO preservation, path retention, or multi-domain logic. Next, we can move into the step-by-step walkthrough.

Step by step: How to redirect a website to another domain

There is no single correct way to redirect a site. The right method depends on how your site is hosted, whether you need to keep URL paths, and how much control you want over SEO signals. 

In the steps below, you can compare the most common redirect approaches one by one, see when each option is appropriate, and follow short setup instructions to get everything live.

You can start with the simplest (registrar forwarding) or choose a more advanced method like server rules, CDN redirects or Geo Targetly if you need regional logic or path preservation.

Method 1: Redirect at your domain registrar

Registrar forwarding is the quickest way to point one domain to another. It works well when the old site is no longer active, but it offers less control than server-level redirects and usually won't preserve URL paths.

Steps

1. Log in to your registrar account
   Example: GoDaddy, Namecheap, Google Domains
2. Open the DNS or forwarding section
3. Add the new domain as the destination
4. Choose a redirect type: 301 for permanent redirects, 302 for temporary changes

Save settings and allow up to 24-48 hours for DNS propagation

Method 2: Redirect using .htaccess (Apache)

Use .htaccess when you want full control over redirects on Apache hosting. This method preserves URL paths and lets you enforce HTTPS and www settings easily.

Steps

1. Access your server via FTP or file manager.
2. Open or create a .htaccess file in the root directory.
3. Add this redirect code:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.olddomain\.com$
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]

‍

4. Replace both domains with your own.
5. Save and test using an http status checker.

Method 3: Redirect using NGINX

NGINX handles redirects at server level and offers fast performance with low overhead. Good for large sites or whenever speed matters.

Steps

1. Open your NGINX configuration file, usually in etc/nginx/sites-available/.
2. Add:

server {
    listen 80;
    server_name olddomain.com www.olddomain.com;
    return 301 https://newdomain.com$request_uri;
}

‍

3. Replace the domain values.
4. Test the config with:

sudo nginx -t

‍

5. Reload the server:

sudo systemctl reload nginx

‍

Method 4: Redirect using a CMS (WordPress, Webflow, Wix, Shopify)

CMS redirects are helpful when you want control without touching server files. Keep in mind that most platform redirects only work if the site remains hosted there.

Steps by platform

‍

Method 5: Redirect using Cloudflare Rules

Cloudflare handles redirects at the edge, which means users are routed before the request hits your server. Good for performance and global traffic.

Steps

1. Log in to Cloudflare and open your domain.
2. Go to Rules > Redirect Rules.
3. Create a rule:
   If Hostname equals olddomain.com
   Then Redirect to https://newdomain.com/$1‍
4. Save and deploy.

Method 6: Redirect with a third-party tool (Geo Targetly recommended)

Third-party redirect platforms are ideal when you want personalization, location targeting, or path preservation without editing servers.

Steps with Geo Targetly:

1. Create a Geo Redirect project.
2. Enter the original domain and target destination.
3. Add conditions such as country, region, device or URL path.
4. Copy the one-time JavaScript snippet.
5. Paste it into the old domain header.

SEO checklist for redirecting a domain correctly

As with most SEO practices, there are steps to take before, during, and after. We’ve put together this checklist to help you along the way.

Before the redirect

1. Crawl and document the existing site structure
Use a crawler like Screaming Frog or Sitebulb to generate a full URL list of your current site. This gives you a baseline to map redirects and catch any missed pages. Export the list and include metadata like title tags, canonical URLs, and response codes.

2. Audit backlinks and top-performing pages
Pull backlink data from tools like Ahrefs or Majestic. Identify pages with strong inbound links or high traffic. These should be prioritized in your redirect plan to preserve link equity. As an example, if /blog/seo-tips has 200+ backlinks, make sure it redirects cleanly to the equivalent new URL.

3. Plan a 1:1 redirect map
Avoid redirecting everything to the homepage. Instead, create a spreadsheet mapping each old URL to its most relevant new URL. If the structure is changing, aim for the closest content match. This helps search engines understand the relationship between old and new content.

4. Set up canonical tags on the new domain
If both domains will be live temporarily, use canonical tags on the new site to point to itself. This prevents duplicate content issues during the transition.

During the redirect

1. Use 301 redirects, not 302s
A 301 status code tells search engines the move is permanent and transfers most of the link equity. Avoid 302 (temporary) redirects unless you're testing something short-term. Configure these at the server level or via your CMS, depending on your setup.

2. Keep redirect chains short
One redirect is fine. Two is pushing it. More than that, and you risk crawl issues and ranking loss. For example, avoid /old-page → /intermediate-page → /final-page. Redirect /old-page directly to /final-page.

3. Update internal links and sitemaps
Once redirects are live, update all internal links to point to the new URLs directly. Also, submit an updated XML sitemap to Google Search Console with the new URLs. This helps search engines discover and index the new domain faster.

4. Maintain consistent site structure if possible
If the old domain used /category/product-name, try to keep that structure on the new domain. Consistency helps search engines map old content to new more easily.

After the redirect

1. Monitor traffic and rankings
Use Google Search Console and your analytics platform to track traffic drops, crawl errors, and keyword rankings. Expect some fluctuation, but large drops may signal redirect issues.

2. Check crawl errors and fix broken redirects
Google Search Console will flag any redirect errors or unreachable pages. Fix 404s or incorrect redirects promptly. For example, if /services/seo is returning a 404 instead of redirecting, update your redirect rules.

3. Keep redirects in place long-term
Don’t remove redirects after a few weeks. Keep them active for at least 12 months, especially for high-traffic or high-authority pages. Some links and bookmarks may take time to update.

4. Rebuild lost links where possible
If some backlinks point to pages that no longer exist and weren’t redirected properly, reach out to those sites with the correct new URL. This helps to recover lost authority.

Redirecting a domain is more than flipping a switch. With the right prep, execution, and follow-up, you can preserve your SEO strength and make the transition smooth for both users and search engines..

Advanced domain redirect scenarios

Moving a site from example.com to example.co.uk is easy. Redirecting several domains, subfolders and region-based versions is where things get interesting. 

With the right setup, you can keep traffic flowing to the correct destination, protect rankings, and route visitors without creating duplicate content or redirect loops. The examples below cover the more complex situations.

Wildcard redirects

Wildcard rules let you redirect groups of URLs without manually mapping each one. They’re useful during migrations or when the same page structure exists across different regions or folders.

Example:
olddomain.com/products/* → newdomain.com/products/*
Everything under /products/ follows the same pattern automatically.

Wildcard redirects save time, scale well, and reduce redirect errors when you’re dealing with large batches of similar URLs.

Subdomain redirects

Subdomains often separate content by region or product line. Redirecting them into a single main domain keeps the experience unified and simplifies long-term maintenance.

Example:
uk.example.com → example.com/uk
de.example.com → example.com/de

This keeps your content organized under one structure rather than maintaining multiple standalone sites.

Region or language-based redirects

Not every country speaks the same language or needs the same landing page. Redirects based on state, province, or language preference help send visitors to the most relevant version.

Example:
Visitors in Quebec → example.com/ca/fr
Visitors in Ontario → example.com/ca/en

This prevents users from landing on the wrong version and reduces friction, especially for multilingual audiences.

Redirecting multiple domains into one

If you own several domains for branding, legacy sites, or acquisitions, routing them into one primary domain consolidates authority and avoids splitting SEO value.

Example:
example.co.uk, example.ca, example.com.au → example.com

You get a single analytics view, consistent link equity, and a much cleaner site structure.

Redirecting only specific pages or folders

You may not want to redirect a whole domain, just certain URLs. Page or folder-based redirects work well for campaigns, currency differences, or seasonal variations.

Example:
US visitors → example.com/holiday-sale
Canadian visitors → example.com/holiday-sale-ca

You keep the same navigation across regions but fine-tune what content each visitor sees.

How to test and verify your redirects

Once your redirects are live, run checks to confirm that traffic is routing correctly. The goal is simple: make sure each URL sends users to the right destination, preserves SEO signals, and doesn’t create loops or dead ends.

Tools you can use

• Browser dev tools (Network tab)
• Redirect checkers such as httpstatus.io
• Screaming Frog or Sitebulb for full site scans
• Terminal commands such as curl -I for header checks

What to look for

• Status code returns 301 for permanent moves
• No multi-step redirect chains
• Old URLs keep their full path after redirect
• HTTPS is enforced and certificates are valid
• Canonical tags point to the correct final URL

A quick spot check is fine for small sites, but larger migrations should be scanned in bulk with a crawler so you can catch issues early.

Common problems and how to fix them

Even a well-planned redirect setup can break in ways you don’t expect. The list below highlights the most common failures and what to check if something looks off.

How Geo Targetly's Geo Redirect feature helps

When you're serving a global audience, sending every visitor to the same default version of your site creates friction. Geo Targetly's Geo Redirect feature solves this by automatically directing users to the most relevant version of your website based on their location.

Route users to the right site or page automatically

Geo Redirect uses IP geolocation to detect a visitor’s country, state, or city in real time. Based on that, it can redirect them to a localized URL, subdomain, or folder path. For example:

• A visitor from Germany landing on example.com can be redirected to example.com/de or de.example.com.
• Someone in California can be sent to a state-specific landing page like example.com/us-ca.

You can set up rules for countries, regions, or cities, and even combine them with URL paths or query parameters. This is especially useful for brands running localized campaigns or managing compliance requirements across markets.

Avoid duplicate content and SEO issues

Redirects can hurt SEO if not handled properly. Geo Targetly gives you full control over redirect types: choose between 302 (temporary) and 301 (permanent) redirects depending on your use case. 

You can also exclude search engine bots from redirection, so they always crawl your default version.

This means you can personalize user experience without confusing Google or splitting your SEO equity across multiple versions of the same page.

Control redirects visually or with code

Marketers can use Geo Targetly’s visual dashboard to create redirect rules without writing code. Just select the target location, define the conditions, and choose the destination URL. Everything is handled through a clean interface.

For developers, the platform offers JavaScript variables and API access. You can trigger redirects conditionally based on user behavior, combine location data with custom logic, or integrate redirects into your own routing system.

Handle exceptions and edge cases

Not every visitor should be redirected. Geo Redirect lets you define exceptions by IP, URL, referrer, or device type. You can also add a redirect delay or display a message before redirecting, giving users a chance to opt out.

This feature is great for international travelers or users on VPNs. You can offer them a choice to stay on the current version or switch to their local one.

Measure and optimize redirect performance

Built-in analytics show how many users are being redirected, from where, and to which destinations. You can track conversion impact, bounce rates, and engagement on redirected pages.

If you're testing different redirect strategies, Geo Targetly supports A/B testing. Run experiments to compare performance between automatic redirection and manual language selectors, or test different landing pages by region.

Geo Redirect removes the guesswork from location-based routing. Instead of maintaining multiple country sites or relying on users to find the right version, you can send them there automatically without compromising SEO or control.

Are you ready to handle your redirects with ease and gain access to a full suite of geo-targeting tools?

Conclusion

Redirecting a domain isn’t difficult, but the details matter. The right method depends on how your site is hosted, whether paths need to be preserved, and how permanent the move is.

A clear SEO migration plan helps protect rankings, maintain traffic, and keep users moving through your site without interruption. 

Tools like Geo Targetly can streamline complex routing, especially when multiple domains or regional experiences are involved. The end goal is simple: a smooth transition for both visitors and search engines.

FAQ

Does redirecting a domain hurt SEO?‍

Not when done correctly. A 301 redirect passes most ranking signals from the old URL to the new one. Issues usually happen when paths aren’t preserved or when pages redirect to irrelevant destinations.

How long does Google take to process a redirect?‍

Indexing changes vary, but most shifts start appearing within a few days to a few weeks. Full consolidation of signals can take several months, especially for large sites.

Can I undo a redirect?‍

Yes, but undoing a redirect may cause search engines to reprocess both URLs. If the old domain needs to be restored, remove the redirect and resubmit sitemaps to Search Console.

How long should I keep the old domain?‍

Keep redirects active for at least 12 months. High-value URLs or sites with strong backlink profiles may need even longer.

Do I need a separate SSL certificate?‍

Yes. Both domains require valid certificates if you expect users or crawlers to access them over HTTPS. Missing or mismatched certificates can trigger warnings and break redirects.

Should I redirect everything or only specific pages?‍

Full-domain redirects work for rebrands and migrations. For campaigns, location targeting, or regional experiences, page-level or folder-level redirects are often more appropriate.