Use one-to-one 301 redirects, verify both domains in Google Search Console, and test everything before launch. That's the fastest way to redirect a domain to another domain without losing SEO. Skip any of these and rankings can vanish for weeks.
Three actions matter more than the rest:
- Set up a 301 permanent redirect for every old URL, not just the homepage.
- Build a one-to-one URL map so each old page points to its true new equivalent.
- Verify both domains in Google Search Console and run the Change of Address tool.
Key Takeaways
A domain move preserves SEO when every old URL gets a 301 redirect to its true equivalent, both domains are verified in Search Console, and redirects stay live for a full year.
| Point | Details |
|---|---|
| Use 301s, never 302s | A 301 tells Google the move is permanent and transfers ranking signals; a 302 does not. |
| Map every URL individually | Build a spreadsheet mapping old URLs to new ones instead of one blanket homepage redirect. |
| Verify both domains in Search Console | Run Change of Address only after both properties are confirmed and verified. |
| Test before and after launch | Check status codes with curl, crawl for chains, and monitor coverage for months, not days. |
| Get managed help if needed | inSave Hosting offers free migration, staging, and support to implement redirects and SSL correctly. |
Where to Read More on Domain Redirects
- Cloudflare's redirect documentation for proxied A/CNAME setup and Redirect Rules.
- Namecheap's URL forwarding guide for registrar-level limitations.
- inSave Hosting's website migration checklist and the partner website handoff checklist for launch-day steps.
Table of Contents
- Quick Checklist for Launching a Domain Redirect
- What's the Difference Between Redirecting a Domain and Forwarding It?
- How Do You Build a URL Map for a Domain Redirect?
- How Do You Test and Monitor a Domain Redirect?
- How Long Does It Take for SEO to Recover After a Domain Change?
- How inSave Hosting Handles Domain Redirects for You
- Sources
- FAQ
Quick Checklist for Launching a Domain Redirect
- Back up the site and export your sitemap and analytics data.
- Build a URL map spreadsheet using crawl data, the sitemap, and top-traffic pages from analytics.
- Pick your redirect method (server, Cloudflare, or registrar) based on how much control you need.
- Implement 301s in staging, test thoroughly, then deploy and submit Change of Address in Search Console.
- Keep redirects live for at least 12 months and update backlinks where you can.
Pro Tip: Don't skip the staging test. A redirect that works on your local machine can still break in production because of caching rules or a missed rewrite condition.
What's the Difference Between Redirecting a Domain and Forwarding It?
Redirecting a domain means the server sends back an HTTP 301 status code that tells browsers and search engines the content has permanently moved. Forwarding often refers to the same outcome, but it's frequently handled at the registrar level rather than the server. DNS itself never touches the browser's address bar. It only resolves a domain name to an IP address, and the actual redirect happens one layer up, at HTTP.
That distinction decides which tool you reach for.
Apache (.htaccess): Add this to the old domain's root .htaccess file:
RewriteEngine On
RewriteCond %{HTTP_HOST} ^olddomain\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.olddomain\.com$
RewriteRule ^(.*)$ https://newdomain.com/$1 [R=301,L]
The $1 preserves the original path so /blog/post-1 lands on the matching page, not the new homepage.
nginx: A server block handles it more cleanly:
server {
listen 80;
server_name olddomain.com www.olddomain.com;
return 301 https://newdomain.com$request_uri;
}
One rule, no chains, and $request_uri carries over the full path and query string.
Cloudflare: Point the old domain's A record at the non-routable address 192.0.2.1 with the proxy enabled, then use Redirect Rules to forward one domain to another while preserving path and query string. Workers can handle more complex logic, like redirecting by geography or URL pattern, but most migrations don't need that.
Registrar forwarding: Many registrars offer a forwarding toggle that runs 301, 302, or masked redirects from their own servers. It works fast for a parked domain, but it rarely gives you per-page mapping or SSL flexibility, which makes it a poor fit for a real SEO migration.
| Method | Control level | Best for |
|---|---|---|
| Apache .htaccess | High | Self-hosted sites with full server access |
| nginx rewrite | High | VPS or dedicated server environments |
| Cloudflare Redirect Rules | High | Sites already proxied through Cloudflare |
| Registrar forwarding | Low | Parked or low-traffic domains only |
How Do You Build a URL Map for a Domain Redirect?
Start by crawling the current site, exporting the XML sitemap, and pulling your top pages from analytics by traffic and backlinks. That combination catches URLs a sitemap alone might miss, including old blog posts that still pull in search traffic.
- Open a spreadsheet with three columns: old URL, new URL, and redirect type plus notes.
- Map your highest-traffic and highest-linked pages by hand first. These carry the most SEO weight, so guessing here costs the most.
- Use pattern-based or regex rules for bulk sections like product categories, but test a sample from every pattern before trusting it site-wide.
- For pages with no real equivalent, redirect to the closest parent category instead of the homepage, or return a 410 status if the content is genuinely gone.
Avoid a blanket homepage redirect except as a last resort for a handful of orphaned pages. It flattens your URL structure and tells Google every old page became one new page, which tanks rankings across the board. Many hosting control panels and CMS plugins support bulk CSV import for these maps once you've built them, which saves a lot of manual entry.
Pro Tip: Reach out to sites linking to your old URLs and ask them to update to the new domain. Updated backlinks pass authority faster than redirects alone, and the outreach list doubles as a record of who to notify about the move.
WordPress-Specific Redirect Options
If you run WordPress, a plugin like Redirection or the redirect manager built into Rank Math or Yoast handles cross-domain 301s without touching server files. Confirm the plugin supports absolute target URLs (full https://newdomain.com/... paths), since some tools default to relative paths that only work within the same site.
- Test bulk imports in staging before pushing to production.
- After redirects go live, update the WordPress Site Address and Site URL settings.
- Regenerate permalinks and manually fix internal links that still point to the old domain.
- Don't rely on the plugin alone for server-level performance. Editing .htaccess directly is still faster for high-traffic sites.
How Do You Test and Monitor a Domain Redirect?
Run curl -I https://olddomain.com/some-page and confirm you get a 301 status with a Location header pointing to the correct new URL. Do this for a representative sample, not just the homepage.
- Crawl the old domain with a tool like Screaming Frog to surface redirect chains, loops, and any pages that quietly fell through the cracks.
- Use an online redirect checker to confirm status codes and headers match what you expect.
- Watch Google Search Console coverage reports on both properties after submitting Change of Address.
- Track rankings and traffic weekly for the first month, then monthly after that.
Recovery windows for a correctly executed migration typically run from a few weeks to as long as 12 months, according to migration case studies, which is exactly why redirects need to stay live well past launch day, not get pulled once traffic looks stable.
How Long Does It Take for SEO to Recover After a Domain Change?
Redirect behavior itself is instant. Google typically starts recrawling redirected URLs within days, but full re-indexing across a large site takes weeks to months, and complete authority transfer can run 6 to 12 months depending on site size and link profile.
Watch for these common mistakes:
- Using a 302 (temporary) redirect by accident, which tells Google not to transfer ranking signals.
- Catch-all redirects sending every old URL to the new homepage.
- Redirect chains, where domain A redirects to B, which redirects to C.
- Forgetting to verify both the old and new domain in Google Search Console.
- Missing redirects for pages that earned backlinks or ranked well, even if they look low-traffic in a quick scan.
Fix these fast: correct any 302s to 301s, collapse chains to a single hop, confirm both domains are verified, and resubmit your sitemap once the new URL map is live.
What I'd Tell You If You Only Had an Hour
Spend most of that hour on the URL map, not the redirect code. A perfect nginx rule pointed at the wrong mapping still loses rankings. Test in staging first. Pattern rules written under deadline pressure without a test pass are where most migrations quietly go wrong.
— Ihor
How inSave Hosting Handles Domain Redirects for You
inSave Hosting gives you a faster path than piecing together .htaccess rules and registrar dashboards on your own. Free migration and staging tools let you build and test your full redirect map before anything touches your live domain, and managed support can implement the server-level 301 rules directly if you'd rather not edit config files yourself.
Pair that with free SSL provisioning so your new domain launches on HTTPS from day one, avoiding an extra canonicalization step later. If you're moving to a new domain as part of a rebrand, start with domain transfer support to get the new domain registered and pointed correctly, then use staging to test every redirect before you flip the switch on the live site.
Sources
FAQ
What's the Difference Between a 301 and a 302 Redirect?
A 301 tells search engines a page moved permanently and passes ranking signals to the new URL. A 302 signals a temporary move and typically doesn't transfer that authority the same way.
Is Redirecting a Domain the Same as Forwarding It?
Not exactly. "Redirecting" usually means a server-level 301 with full control over headers and paths, while "forwarding" often runs through a registrar's own servers with fewer options for SSL and per-page mapping.
Is a CNAME Record a Redirect?
No. A CNAME record is a DNS entry that points one domain name to another for resolution purposes; it doesn't change the URL a visitor sees or send an HTTP status code. The actual redirect happens at the HTTP layer, not in DNS.
What Does It Mean to Redirect a Domain?
It means every URL on the old domain sends visitors and search engines to its corresponding URL on the new domain, using an HTTP 301 response so the move counts as permanent for SEO purposes.
Can inSave Hosting Help Set Up Domain Redirects?
Yes. inSave Hosting's managed support can implement server-level 301 rules, and its free migration and staging tools let you test the full redirect map before your new domain goes live.