Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



Are you in the process of migrating your content to a new website? If so, you’ll already know that this is one of the most taxing and demanding experiences a webmaster or business owner can undergo. Unfortunately, the process known as content migration is a necessary part of a website redesign. This is where content elements such as text, images, and videos, are migrated from your old website to the new domain.
While the website migration process can often be painful, it can also provide the perfect opportunity to re-evaluate your website content, to benchmark performance, and to identify potential areas of improvement. For this reason, a website migration checklist is imperative to carry out the operation successfully. The checklist will help you to plan your migration strategically, to maintain (as far as possible) the SEO strength of your domain, and to avoid some of the many risks attendant upon website migrations.
When migrating content to a new website many businesses simply copy over all of their existing content en masse to the new website. While this is a perfectly legitimate means of website migration, it does not capitalise on this unique opportunity to analyse and optimise the performance of your existing content.
Before migrating, analyse your Google Analytics account and look for the following pages:
Your analytics data will provide you with deep insights into your most important pages, and the poorest performing webpages. Armed with this data you will be able to optimise the content migration process, and to streamline your new website. In identifying the power pages on your old site, you will then be able to focus your efforts on ensuring these pages retain their quality on the new site. On the other hand, the pages with high bounce rate or low session count provide an opportunity either to optimise the pages on the new website, to consider leaving them out altogether, or to move them to new URLs to be optimised for a different search intent.
The XML sitemap is the backbone of your website, the information which search engines such as Google refers to understand the navigational structure of your site. Creating a new sitemap will also help to guide you in terms of which content you want to migrate, and which content you want to leave behind based on the analysis of your Google Analytics data.
You should also keep your old sitemap in Google Search console, and then submit the new XML sitemap for your new site as well. This way, if you request Google to request the old sitemap, it will pick up on the redirects to the new site quickly, helping to accelerate the migration process considerably.
It goes without saying that a website migration is not something that should be rushed. A successful migration requires coordination and planning, as well as careful testing. Before you even consider carrying out the migration, everything should be tested first on a test server. This way, you will be able to catch any errors in advance of the final migration, and will be able to verify that crucial elements such as redirects are functioning correctly. Failure to carry out testing in advance can have serious repressions for your website and your business, particularly if your organic traffic drops off a cliff in the days following the migration!
Here are some of the elements to check before going live:
Generally speaking, any form of website migration is going to have a short and long term impact on your traffic. For this reason, it is crucial that you take steps to minimise this impact as much as possible. An easy and obvious way to minimise the short term loss of traffic is to plan your website migration in a period of downtime. Peak and downtimes will vary by industry, but as a general rule of thumb, you will probably want to avoid planning a migration leading up to the Christmas period, or in its immediate aftermath. In terms of days of the week to migrate, Tuesdays and Wednesdays are generally preferable, as this allows you to iron out any issues and get up and running by the weekend. Of course, if you run a B2B business then the opposite is true, and you may want to take advantage of the relative quiet of the weekend to migrate to your new website.
A successful website migration does not end with the migration itself. In the days and weeks following your migration it is crucial that you closely monitor activity on your website using Google Analytics. It is normal to see a downturn in traffic following the migration, but you will still want to measure performance on your new site against the benchmarks set on your old website. Each of your top-performing pre-migration pages should be analysed to see to what extent, if at all, traffic has declined. Major short term drop-offs in traffic will be easily noticeable, but you should also be watchful of smaller drop-offs over a longer period of time which may represent a genuine error that you should be able to rectify.
Share this
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
Find out everything you need to know in our new uptime monitoring whitepaper 2021