Traffic Disappeared After Moving to a New Domain

You moved your website to a new domain.

Maybe you rebranded. Maybe you finally got the shorter, cleaner domain name you wanted. Maybe you moved from a .net to a .com. Whatever the reason, the move made sense at the time.

Now the traffic is gone.

A domain migration is one of the riskiest SEO operations you can perform. Not because Google penalizes domain changes. It does not. But because the process requires a long list of technical steps to be executed correctly. If even a few of them are missed or done wrong, you can lose months or years of accumulated authority almost overnight.

The comforting truth: domain migration traffic loss is almost always recoverable. The entire ranking history, the backlink equity, the Search Console data. None of it has to be permanently lost. Google has a specific process for recognizing and processing domain moves. The challenge is executing that process correctly, or, if the move was done incorrectly, systematically repairing what broke.

This article covers everything you need to know to recover traffic after a domain move gone wrong.

1. How Google Processes Domain Migrations

When you move a website from one domain to another, you are asking Google to do something significant: transfer all the trust, rankings, and historical signals it has built up for the old domain to a completely new domain it has not yet evaluated independently.

Google does this through a process called domain move recognition. When it encounters 301 redirects from every page of the old domain to the corresponding page on the new domain, it interprets this as a permanent move. It then begins transferring the historical signals from the old domain while simultaneously evaluating the new one.

This process is not instantaneous. It takes time, sometimes weeks, sometimes two to three months, for Google to fully process a domain move and stabilize rankings on the new domain. During this window, rankings fluctuate. Some pages rise and fall unpredictably. Traffic may drop, then partially recover, then drop again before settling.

This is normal and expected even when the migration is executed perfectly.

The catastrophic losses happen when the migration is not executed correctly. When Google cannot follow the signal clearly from old domain to new, or when the new domain introduces problems that the old one did not have.

Understanding this distinction is critical. A clean migration with some temporary fluctuation is very different from a broken migration with a signal loss that compounds over time.

2. The Most Common Migration Mistakes That Kill Traffic

Most post-migration traffic disasters trace back to one or more of these specific errors:

No 301 redirects, or only redirecting the homepage:

The most damaging mistake. Without 301 redirects on every page, every URL on the old domain becomes a dead link. All the backlink equity that pointed to specific pages on the old domain evaporates. Google finds a new domain with content but no clear authority signal.

302 redirects instead of 301:

A 302 redirect means “temporary move.” A 301 means “permanent move.” Google treats them very differently. With 302s, Google does not transfer ranking signals to the new domain. It continues treating the old domain as the canonical location. If you used 302 redirects, your new domain has almost no chance of inheriting the old domain’s rankings.

Keeping both domains live simultaneously:

If the old domain is still active and returning content rather than redirecting, Google sees two domains with the same content and treats it as duplicate content. Neither domain ranks optimally, and the authority is split rather than transferred.

Changing URLs at the same time as changing domains:

A domain migration is already a major signal change for Google. Simultaneously changing URL structures multiplies the complexity and the risk. Google has to process both a domain change and a URL structure change at the same time, making it much harder to correctly transfer signals to the right new pages.

Not verifying the new domain in Search Console:

Without verifying the new domain property in Google Search Console, you cannot use the Change of Address tool, cannot monitor crawl data, and cannot submit a new sitemap. Google has no formal notification that a migration occurred.

Not submitting a new sitemap after migration:

Without a sitemap on the new domain, Google discovers new pages through crawl alone. This is slower, less complete, and delays the indexation of all your content on the new domain.

3. Step 1: Verify Your 301 Redirects Are Correct

If your traffic has disappeared, the first thing to check, before anything else, is whether your 301 redirects are in place, complete, and functioning correctly.

What correct 301 redirects look like:

Every page on the old domain redirects to the corresponding page on the new domain
The redirect returns a 301 status code (not 302, not meta refresh, not JavaScript redirect)
The redirect goes directly to the target page without creating chains (old URL to new URL in one step)
The homepage redirects: olddomain.com redirects to newdomain.com
Both the www and non-www versions of the old domain redirect to the new domain

How to check:

For a quick check without command-line tools, install the free Redirect Path browser extension for Chrome or Firefox. Enter any old URL in your browser’s address bar. The extension shows the exact redirect chain and final status code at each hop.

If you are comfortable with the command line, you can also verify using: curl -I http://olddomain.com/specific-page

Look for “HTTP/1.1 301 Moved Permanently” in the response. Anything else (302, 200, or 404) indicates the redirect is wrong or missing.

Use Screaming Frog to crawl your old domain. It will show the response code for every URL. Every page should return 301.

If redirects are missing or wrong:

Implement correct 301 redirects immediately. In Apache, this is done via .htaccess. In Nginx, via the server configuration file. In most CMS platforms, redirect plugins handle this. Your hosting provider or developer can implement server-level redirects, which are the most reliable option.

Once redirects are in place, Google will begin processing the domain move as it recrawls the old domain and follows the redirects to the new one. Rankings typically begin recovering within four to eight weeks of implementing correct redirects.

4. Step 2: Update Google Search Console

Google Search Console has a built-in tool specifically designed for domain migrations: the Change of Address tool.

If you did not use this during your migration, doing it now, even after the fact, formally notifies Google of the domain move and helps accelerate the ranking transfer.

How to use the Change of Address tool:

Verify ownership of both the old domain and the new domain in Google Search Console.
In the old domain’s property, go to Settings, then Change of Address.
Select your new domain from the dropdown and follow the prompts.

This formally tells Google that the site at olddomain.com has permanently moved to newdomain.com.

Google recommends keeping this Change of Address active for at least six to twelve months after migration, as it continues to help signal the domain relationship while Google processes the full transition.

Also verify the new domain as a Domain property (not just a URL prefix property) in Search Console. This captures all variations of the URL, including www and non-www, both HTTP and HTTPS, in a single property. This gives you the most complete view of how Google sees your new domain.

5. Step 3: Submit Your Sitemap on the New Domain

A sitemap tells Google about every page that exists on your site and helps it discover content more efficiently.

After a domain migration, submitting a fresh, complete sitemap to the new domain’s Search Console property accelerates indexation.

What a post-migration sitemap should include:

Every page you want indexed on the new domain
Only canonical URLs (not redirect URLs or parameter URLs)
Current, accurate last-modified dates
The new domain’s URLs, not the old domain’s

How to submit:

In Search Console for your new domain property, go to Sitemaps. Enter the URL of your sitemap (typically newdomain.com/sitemap.xml) and click Submit.

Monitor the sitemap report over the following weeks. The “Discovered URLs” count should be growing, and the ratio of indexed to discovered pages should be high. If many pages are being discovered but not indexed, there is a separate crawl or quality issue to investigate.

6. Step 4: Update All Backlinks You Can Control

Backlinks are the most critical authority signal in Google’s ranking algorithm. After a domain migration, the backlinks pointing to your old domain pass their equity through your 301 redirects to the new domain.

However, this transfer is not always 100% efficient. Some link equity may be lost through redirect hops. More importantly, as you build future authority, you want backlinks pointing directly to your new domain, not through a redirect chain.

Links you can update directly:

Social media profiles: update all profile links to the new domain
Directory listings: any business directories, industry listings, or citation sources where you have control
Guest posts where you have author access: update your author bio links
Your own other websites or properties: update any cross-links between your own sites
Newsletter archives and email templates: update any links in email footers or welcome sequences
YouTube channel descriptions and video links
Any platforms where you have posted links to your site

Links you can request be updated:

For important backlinks from high-authority sites, reach out to the site owners and request they update the link to point directly to your new domain URL. Most webmasters will accommodate this request if you provide the exact new URL they should update to.

Reach out to partners and collaborators to announce the new domain. Update your profile links on any platforms where you are already active: LinkedIn, industry directories, podcast bios, and YouTube descriptions. Even a handful of direct links to the new domain early in the migration helps Google build independent confidence in the new URL.

How to find your backlinks:

In Google Search Console’s Links report, you can see who links to your site. You can also use Ahrefs or Semrush to export a full backlink list with the linking page URL and the linked URL. This makes it straightforward to work through the list systematically.

7. Step 5: Update All Internal Links

After a domain migration, every internal link in your content, every link from one page to another within your site, should point to the new domain’s URLs directly, not to the old domain through a redirect.

Internal links that point to the old domain go through a redirect to reach the new domain. This is technically functional but creates unnecessary redirect hops, slightly slower page loads, and a signal that your own site has not fully transitioned.

How to fix internal links:

In WordPress and most CMS platforms, you can use a plugin like Better Search Replace to perform a database-wide find and replace. Find all instances of “olddomain.com” in your content and replace them with “newdomain.com.”

Alternatively, use Screaming Frog after migration to crawl the new domain and identify any internal links still pointing to the old domain. Export that list and update them systematically.

This is especially important for links in your navigation menus, footer, and sidebar. These appear on every page and represent a large number of redirect hops if not updated.

8. Step 6: Rebuild Trust Signals on the New Domain

The new domain is unknown to Google in terms of its own direct history. While 301 redirects transfer ranking signals from the old domain, the new domain itself has no independent trust history. It needs to build its own signals as quickly as possible.

Trust signals to focus on immediately after migration:

HTTPS and security: Ensure the new domain has a valid SSL certificate installed and all pages are accessible via HTTPS without mixed content errors. This is a baseline trust requirement.

About page and contact information: Make sure the new domain has clear information about who owns and runs the site. This helps Google’s quality evaluation systems understand the site’s provenance.

Consistent branding: If the domain change involved a rebrand, update all your online presence consistently. Social media, business directories, Google Business Profile, and anywhere your brand appears. Consistency of name, address, and website URL across the web is a trust signal.

Start earning new links directly to the new domain: Write a few guest posts. Reach out to partners and collaborators to announce the new domain. Update your profile links on any platforms where you are already active. Even a handful of direct links to the new domain early in the migration helps Google build independent confidence in the new URL.

9. Step 7: Monitor and Maintain Through the Transition Period

Domain migrations are not single events. They are processes that unfold over months. Active monitoring during this period allows you to catch and fix problems before they compound.

What to monitor in Search Console:

Coverage report: Are new pages being indexed on the new domain? Is the indexed page count growing toward your expected total?
Crawl Stats: Is Google crawling the new domain regularly and with a healthy crawl success rate?
Performance report: Are impressions and clicks on the new domain growing week over week?
Links report: Are backlinks starting to show as pointing to the new domain?

What to monitor externally:

Check your top 20 keywords weekly to track ranking positions
Monitor the old domain in Search Console. Old domain impressions should decline gradually over six to twelve months as Google fully transitions its index.

Timeline expectations:

Weeks 1 to 2: Google begins crawling the new domain and following redirects from the old domain.

Weeks 3 to 6: New domain pages begin appearing in search results. Rankings are unstable and may fluctuate significantly. This is normal.

Months 2 to 3: Rankings begin to stabilize. Traffic on the new domain should be approaching pre-migration levels if the migration was done correctly.

Months 4 to 6: Full stabilization. Rankings on the new domain should be comparable to or better than what the old domain had. The old domain’s impressions in Search Console will be declining toward zero.

Month 3 is your critical checkpoint. If you are past month three and traffic has not substantially recovered, meaning not returned to 100% but clearly trending back toward pre-migration levels, treat it as a confirmed problem. The most common unresolved causes at this stage are incomplete redirects on specific pages, a crawl barrier that was overlooked, or a quality issue on the new domain that did not exist on the old one. Run a full technical audit of the new domain at this point rather than continuing to wait.

10. Why Traffic Drop During Migration Is Normal (To a Degree)

Even a perfectly executed domain migration produces a temporary traffic drop.

This is not a sign something went wrong. It is the inherent cost of asking Google to transfer its evaluation of your entire site to a new domain.

Google’s process of recognizing and confirming a domain move takes time. During that window, your rankings are in transition. Some pages may temporarily drop off page one before they return. The total traffic during this transition period is typically 20 to 40 percent lower than your pre-migration baseline.

This temporary drop should start recovering within four to eight weeks of a clean migration, with full recovery within three to six months.

What is NOT normal:

A complete disappearance of traffic that does not begin recovering within four weeks
New domain pages that are not getting indexed after four weeks
Old domain pages still appearing in search results with no redirect being followed after six weeks

These signals indicate a specific problem in the migration process that needs to be diagnosed and fixed using the steps above.

Frequently Asked Questions

How long should I keep the old domain’s redirects active?

Google recommends maintaining 301 redirects from the old domain for at least one year after migration. The practical reason: many backlinks pointing to the old domain will never be updated. Keeping redirects active ensures those links continue passing value indefinitely. There is no cost to keeping a domain registered and redirecting it. Treat it as a permanent infrastructure cost of the migration.

We moved to a new domain six months ago and traffic never recovered. Is it too late to fix?

No. Implementing correct 301 redirects, using the Search Console Change of Address tool, and re-submitting your sitemap can still produce recovery even months after a problematic migration. The process takes longer the longer problems have been in place, but recovery is still possible in most cases.

I used 302 redirects instead of 301 for my domain migration. How do I fix it?

Change them to 301 redirects immediately. On Apache servers, update the redirect rules in your .htaccess file. On Nginx, update the server configuration. In most CMS platforms, any redirect plugin will let you change the redirect type. Once the 301s are in place, use the URL Inspection tool in Search Console to request recrawling of your homepage and key pages. Also resubmit your sitemap. Google will then begin reprocessing the migration correctly. The timeline resets from the point the 301s are properly implemented, not from when the migration originally occurred.

Does the age of the new domain matter? Will a brand new domain rank as well?

Domain age is a minor signal. A brand new domain can absolutely rank well, particularly with strong backlink equity transferred through redirects from an established domain. The age of the content, the quality of backlinks, and the overall authority signals transferred through correct redirects are far more important than the new domain’s registration date.

Our traffic was already low before migration. Will migration make it worse?

If pre-migration traffic was low and the migration was done correctly, the new domain should eventually perform at least as well as the old one. If pre-migration traffic was low because of content quality or authority issues, those same issues will exist on the new domain. Migration does not fix underlying SEO problems. It just moves them.

We changed our domain name AND restructured our URLs at the same time. Is recovery still possible?

Yes, but it is more complex. You need both a complete domain-level redirect strategy AND a URL-specific redirect map. Every old URL on the old domain must redirect to the correct new URL on the new domain. This requires careful planning and testing. Work through both components systematically using the steps above.

Can I check if Google has officially processed my domain move?

Yes. In Search Console, check the old domain’s Performance report. Over the months following a correctly executed migration, impressions for the old domain should gradually decline toward zero as Google transfers its index to the new domain. If old domain impressions are holding steady or growing, Google has not fully processed the move. This is typically because the redirects are incomplete or not functioning correctly.

Conclusion

Traffic loss after a domain migration is one of the most correctable SEO problems that exists. Provided you know what to fix and do it systematically.

The steps in this guide cover the complete chain: redirects, Search Console notification, sitemap submission, backlink updates, internal link cleanup, trust signal rebuilding, and ongoing monitoring.

Work through each step in sequence. Do not skip steps because they seem minor. The migration process requires every component working together. A single missed step can undermine an otherwise correctly executed recovery.

Your old domain’s authority is not gone. It is waiting to be properly transferred. Give Google the clear signal it needs, and the traffic will follow.

Google’s official documentation on site moves with URL changes is the authoritative technical reference for domain migrations and should be read in full before or during any domain move.