An SEO-led website migration protects the organic visibility, traffic and search value your website has already earned while the platform, domain, structure or content changes underneath it.
Whether you are moving CMS, changing domain, redesigning the site or bringing several websites together, the work begins before development starts and continues after launch.
A website migration can be an opportunity to improve a site, but it can also create avoidable disruption if search is treated as something to consider after launch.
Search engines need to understand what has changed, where old pages have moved and which pages remain important. Customers need to continue finding the information they expect. The more that changes at once, the more carefully the project needs to be planned.
The common risks are usually straightforward:
A well-planned migration does not mean promising that rankings will never move. Search engines need time to process a new version of a site. It does mean reducing unnecessary risk, identifying issues early and giving the new site the strongest possible foundation.
Moving from one content-management system to another can affect URLs, templates, content and technical settings at the same time.
This includes moves such as WordPress to Shopify, Wix to WordPress, a bespoke site to HubSpot, or a change to another platform that alters how pages are structured and managed.
A new business name or domain moves the signals the existing website has built over time. This is one of the higher-risk migration types because every existing URL needs a considered destination and search engines need to understand the relationship between the old and new domains.
A website can stay on the same domain but still go through a substantial migration. Changes to templates, navigation, content, page structure and URLs can all affect organic visibility.
Search should be part of the planning before the design is finalised, not an extra task added shortly before launch.
Bringing several sites into one, merging businesses or separating part of a business onto its own domain all require careful planning.
The work considers which pages, content and search signals need to move, what should be combined and how people and search engines will reach the right destination afterwards.
Smaller structural changes can still have search implications. This includes moving a blog from a subdomain into a subfolder, changing protocol, or making a focused section of a site more prominent.
The level of work should match the risk. Some moves need a detailed engagement; others need a smaller, focused review.
Every migration is different, but the process has three main phases: planning before the build, checking before launch and monitoring afterwards.
The first stage is to understand the current site properly.
I create an inventory of the pages that exist, using a full crawl alongside the information available in Search Console and analytics. This identifies the pages receiving organic traffic, ranking for important terms, earning links or contributing to enquiries and revenue.
That inventory becomes the basis for the migration plan.
I then work through the old and new site structure, map redirects from existing URLs to their most relevant new destination and identify content that needs to be retained, improved or deliberately retired.
The planning phase usually includes:
This is the point at which important decisions are easiest and least expensive to make.
Once a staging version of the new site is available, I review it against the agreed migration plan.
The aim is to identify issues while they can still be fixed safely. That includes checking the site structure, content, internal links, metadata, canonical tags, structured data and technical SEO requirements.
Redirects are tested in bulk rather than relying on a handful of manual checks. Staging is checked to ensure it is not indexable, while the live environment is prepared to allow search engines to access the new site when it launches.
Before launch, I provide a clear view of what has been checked, what needs resolving and whether the site is ready from an SEO perspective.
The work continues once the new site is live.
Launch-day checks confirm that redirects are working, the live site is available to search engines, analytics is recording activity and the correct sitemap has been submitted.
During the first two weeks, I monitor the migration closely. Search Console, crawl errors, index coverage and important URLs are reviewed regularly so issues can be addressed quickly.
Monitoring then continues weekly for the following six weeks. At the end of the initial recovery period, you receive a written comparison against the original benchmark, including any areas that need further attention.
A migration usually involves the business, a developer or development team, and search input. Clear responsibilities make the project easier to manage.
I lead the SEO side: the existing-site inventory, benchmarks, redirect mapping, technical specification, pre-launch checks and post-launch monitoring.
Your developer or development team leads the build and implements the agreed requirements. Your team makes decisions on content, timing and priorities, with a clear view of any SEO considerations that may affect the launch plan.
The goal is a joined-up process in which everyone understands what is needed and when.
If you do not have a developer, I can also design and build the new website. In that case the search work and the build sit together from the start, which removes the handover between them and the places requirements tend to get missed.
This is the core checklist used during an SEO-led migration. The exact detail will vary by site, but these are the areas that should be considered.
Not every website change needs a full SEO migration engagement.
If you are changing hosting provider and every URL, page, platform and piece of content remains the same, this is usually a technical task for your developer. A smaller SEO check may be enough.
If you are adding a few new pages to an existing website, that is not normally a migration either.
A full migration service is most valuable when important URLs, content, platform, domain or site structure are changing and organic search is already an important way people find the business.
Most SEO migration engagements run over four to ten weeks from the first review to post-launch sign-off.
The timing depends on the size and complexity of the site, the number of URLs changing, whether content is being rewritten and how far the build has already progressed.
The earlier search is involved, the more time there is to make useful changes before launch. If a launch date is already in the diary, it is still worth discussing the project as soon as possible.
If you are planning a platform move, rebrand, redesign or restructure, tell me a little about the project.
I’ll read it personally and let you know whether SEO migration support is the right fit.
