Example of a poor site migration — recovery took 6 months!

[kexej28769@nongnue]

As is typical with site migration projects, the launch date had to be pushed back a few times due to the risks of launching the new site prematurely and before major technical hurdles could be fully resolved. But as you can see in the visibility graph below, the wait was worth it. Organic visibility not only didn’t decline (as most would normally expect), but actually started to increase from the first week.

Visibility growth reached 60% one month after argentina number data , while organic traffic growth exceeded 80% two months after launch.


Example of a very successful site migration — immediate growth after the new site launched!

It was a complex transition as the new website was redesigned from scratch on a new platform and built with an improved site ranking that included new landing pages, an updated URL structure, lots of redirects to preserve link equity, as well as a switchover from HTTP to HTTPS.

In general, it can be difficult to introduce too many changes at once because if something goes wrong, you will struggle to figure out what exactly went wrong. But at the same time, leaving big changes for later is also not ideal because it will require more resources. If you know what you are doing, it can be much cheaper to make multiple positive changes at once.

Before you can learn how to turn a complex site migration project into a success, it's important to explain the main types of site migrations, as well as the main reasons why site migrations fail.