Last month, Croud ran the first in its new series of webinars.
Hosted by Adam Clemence, Croud’s SEO Account Director, we discussed the different types of website migrations, the top five things that can go wrong with a site migration (and how to avoid them), and why SEO is one of the most important factors to take into consideration when undertaking a site migration.
You can watch the full video here:
Below is a summary of the webinar:
What is a migration?
A site migration is a broad term used to describe any significant move of all, or part, of a website to a new domain, platform or combination thereof. There are many different types of migration, which we roughly broke down into three categories; CMS, domain, and a blend of both.
First we discussed the characteristics of the three categories, starting with CMS migrations which tend to be more internal, with URL structure remaining relatively stable and a lot of development time going to the back end.
We then moved to the other side of the spectrum with domain migrations. These tend to be more external-facing, represent a large change in URL structure, and are focused on site architecture and redirects.
More of a catch-all for types of migrations that aren’t thought of as such, the third category – affectionately dubbed ‘Combo’ for the webinar – is perhaps the most common and contains elements of both CMS and domain migrations. Examples include moving a blog from a subdomain to a subdirectory, or purchasing a competitor site and redirecting it to your established domain.
Whichever type of migration you’re considering, its important to understand the potential impact it could have on your traffic. Likewise, it’s important to properly plan and execute a migration to mitigate negative impact.
Anatomy of a migration
During the webinar, we discussed the merits of planning migrations at least 3-6 months out, allowing plenty of time for scheduling changes, feature requests and generally unplanned events. Croud’s high-level recommendation for timeline includes:
The planning phase, starting 3-6 months before the suggested migration date. This included planning, metric benchmarking, identifying stakeholders in the migration and finalizing a move date.
Final steps, 1-2 months out from the migration date. During this time, teams should be collaborating on a regular basis, meeting to share information an updates, and identifying major pitfalls. Most importantly, this is when all stakeholders should agree on a no-change date, at which the migration will go through no matter what.
Pre-migration, about a month out, seems a little odd to name a step that had already had two before it, but it’s perhaps the most important. During the pre-migration phase, you should crawl your site multiple times, work on URL inventory, and begin redirect mapping.
Post-migration is an ongoing process following your migration and is focused on mitigating the negative impact of migration. It includes broken link checking, traffic monitoring, and any quick fixes that the dev team should be aware of.
Reasons for migration
Whilst there are many reasons for a migration, in the webinar, we focused on the three key reasons the Croud team tends to experiences. They are:
The company name is changing, or dropping a word, or trying to focus (or broaden) their scope.
2. Moving to a better CMS
Perhaps the old CMS is outdated, the site had outgrown it, or the contract is up and a different partner is in the mix.
3. Site absorption
A site has purchased a competitor or is moving their blog from subdomain to subdirectory.
Failure to prepare is preparing to fail – this adage is true for website migrations. Before you start your journey, one of the key questions you should ask yourself is the reason for the migration – is it something you need to do? Consider carefully, as a botched migration can significantly impact your traffic. A fourth category we touched on is migration recovery – in some instances, clients have come to us following 25% loss in organic traffic that hasn’t bounced back.
We discussed five big pitfalls of a migration, and ways to address them:
1. Failing to take a complete site inventory
If you have a large site, this can feel like an odious task, but it’s a must. Most types of migrations will impact every part of your site and can reveal previously-unearthed sections that can have deep, long-lasting consequences for your site.
2. Trying to do everything at once
Developers deal with scope creep constantly, and the same is true for migrations. During the planning phase, you may encounter stakeholders asking for new features to be added, or backlogged upgrades to be implemented during the migration. However, the move should be your central focus. Although you may want to play other fixes and updates, don’t do more than one section at a time, instead focus your energy on the task at hand.
3. (Dis)regarding redirects
Pop quiz – what are the five most important pages on your site for organic traffic? examine your top-performing pages across multiple channels like organic and PPC, and make a priority list that you’ll check frequently before and after the migration.
4. Delaying the migration
Once you set a date, stick to your schedule! Depending on the type of site you own, a delay of a couple of weeks could add hundreds or thousands of new URLs to the project. A final snapshot of a website can take up to 30 hours to compile – you don’t want to have to repeat it.
5. Missing the post-migration
Make a list of priorities for your post-migration. Some problems – like noindex tags or broken ads – should be prioritized over previously acknowledged drops in traffic. The first 48 hours after a migration are crucial to its success. As such, Croud recommends avoiding running your migration on a Friday night.
Finally, it is important to have some takeaways from any meeting, event or webinar, and these are three key points to help you kick your migration off correctly:
1. Ask an SEO or have them run the migration. A good technical SEO will have an extensive knowledge of how your sites work together.
2. Crawl your side (3x at least) – How big is your site? What is your internal structure like? The answers to these questions will help determine your timeline and resource.
3. Set the deadline three months farther – For more sites with decent traffic, the migration is going to take longer than you think. Give yourself plenty of buffer.
If you need help with your migration or want to talk about any of the points mentioned with Adam, contact us.