3rd February 2026
A website migration is one of the fastest ways to lose organic revenue if it is handled badly. However, in most cases, this is not because SEO is unpredictable. It is because planning was poor, ownership was unclear or critical checks were skipped.
An SEO migration is the process of protecting organic search visibility when a website undergoes significant structural change. This typically includes changes to domains, URL structures, site architecture, templates, content or platform. The goal is to ensure search engines can still crawl, understand and trust the site after launch, and that existing rankings and authority transfer cleanly to the new version.
This guide sets out a practical SEO migration plan and checklist, based on real migration work carried out by an SEO agency . It focuses on the steps that actually protect performance during a site or domain change.
This phase exists to remove uncertainty before any website development or content work starts.
Most SEO migration problems are not technical in nature. They come from unclear scope, blurred ownership or timelines that prioritise launch dates over validation. To remedy this, this phase defines what is changing, who is responsible and how much risk the business is willing to accept. If those decisions are made late, they get made badly.
Before any development work starts, you need to be clear on what is changing and what is not. At a minimum, you need clear answers to three questions:
Each of these introduces a different level of SEO risk. Combined, they multiply it.
If this scope is not locked early, SEO decisions get pushed to the end of the project. That is when teams are under time pressure and trade-offs get made quickly. Those trade-offs usually cost traffic.
This step exists to prevent reactive decisions later. It forms the foundation of a workable website migration project plan, not a theoretical one.
Migrations fail when responsibility is shared instead of owned. You need named owners for the parts of the migration that directly affect organic performance. This includes content decisions (around what changes and what stays the same) and technical decisions (who is responsible for running SEO checks before and after launch).
Without clear ownership, problems fall between teams. Specifically, this can result in redirects only getting partially implemented, content being removed without review or tracking issues being assumed to be “someone else’s problem”. When ownership is explicit, issues surface earlier and get resolved faster.
The timeline affects how well the migration actually gets done. When time is tight, technical checks can get rushed or even dropped completely.
If organic traffic matters to your business, you need enough time to do the basics properly before launch and to monitor things closely afterwards. If that time isn’t available, it’s worth being clear about the level of risk the business is comfortable with.
Most migration failures are decided before development even starts. Unclear scope, shared ownership and unrealistic timelines create avoidable risk long before anything goes live.
Content is where migrations quietly lose money. This isn’t because “Google doesn’t like change”. More often, it’s because teams remove or rewrite the parts of pages that were doing real work.
For example, during a migration, category pages can lose supporting copy, internal links sometimes disappear, FAQs get dropped, or templates change and the content ends up in a different place.
These kinds are content changes can wipe out rankings that were driving profitable traffic long before the migration. Phase 2 is how you stop that happening.
Before you change anything, you need a clear record of what you are migrating; specifically, the content and page elements that make those pages rank and convert.
Start by reviewing the main page types. Each one carries different SEO and commercial risk during a migration. For example, on ecommerce websites:
Category and listing pages: These pages usually drive the majority of organic traffic and revenue. The top-of-page copy, supporting content blocks and internal links often explain relevance to search engines and guide users deeper into the site. When this content is shortened, moved or removed for design reasons, rankings tend to move quickly. Any changes here should be deliberate and documented, rather than accidental.
Product pages: Product pages often contribute a meaningful share of organic traffic, even when they are not the primary landing pages. They also support category performance through internal linking and relevance signals.
Static pages and blog content: These pages are easy to overlook during migrations and are a common source of lost value. Many continue to attract steady traffic long after publication and contain internal links that distribute authority across the site.
FAQ content: FAQs usually exist because they answer real search intent. On many sites, they are also marked up with FAQ schema. If FAQs are present on the legacy site, they should be treated as part of the migration scope unless there is a clear and justified reason to remove them.
The output of this content audit is your website content migration checklist. It gives you something you can check off and validate, rather than guessing after launch.
At launch, the goal is stability.
That is why content parity matters. “Parity” simply means the new site carries across the content that already performs, in the places search engines and users expect to find it.
When you mix a migration with big content rewrites, you create noise. If rankings drop, you cannot quickly tell whether the cause is redirect coverage, crawlability, template changes or content removal.
If the legacy content is too long, too messy or needs improvement, that is fine. Keep it close for launch, then plan a proper post-launch review once the new site is stable and tracking is reliable.
Migrations don’t lose rankings, content changes do. Removing, rewriting or relocating what already performs is the fastest way to erase organic value during a redesign.
This phase is where most migrations either hold steady or unravel.
Technical SEO is what determines whether search engines can crawl, understand and trust the new site. It also dictates whether the equity built up in the old site transfers cleanly or gets lost.
The aim here is control; you want to know exactly what search engines will see before and after launch.
Start by crawling the current website in full. This gives you a complete view of what exists today, including all indexable URLs, their status codes, canonical tags and metadata.
That crawl becomes your reference point for the rest of the migration. When performance changes after launch, this is what you compare against to understand why.
Every existing URL needs a defined destination on the new website. That applies to category pages, product URLs, static pages, blog posts and image URLs where they contribute traffic or visibility. If a URL exists today and performs any useful function, it needs to be accounted for.
This mapping is the backbone of any SEO site migration checklist. If a URL is not mapped, it will not be redirected correctly. In practical terms, that means it has been removed from search.
Redirects should be planned, reviewed and ready before the site goes live.
Each old URL should resolve cleanly to its most relevant new equivalent. Redirect chains dilute signals and slow crawling. Redirecting large numbers of URLs to irrelevant destinations usually results in lost rankings rather than preserved ones.
Once URLs and redirects are defined, you need to be clear about how search engines are allowed to crawl the new site. Review the following areas carefully:
robots.txt rules: Use robots.txt to control which sections of the site should and should not be crawled, especially where filters or faceted navigation create large numbers of URLs. Google no longer supports crawl control through Search Console parameters, so robots.txt now carries more responsibility.
Indexation logic: Check how noindex directives are applied across page types. Make sure pages intended to rank are indexable, and that low value or duplicate URLs are consistently excluded.
Canonical tag behaviour: Confirm that canonical tags point to the correct preferred URL on every page type.
Template changes are a common source of unexpected ranking drops.
Compare new templates directly against the legacy site, with particular focus on heading tag structure , internal linking and where content appears on the page. Even small shifts can change how search engines interpret page purpose.
Where paginated pages are intended to be indexable, they should use self-referencing canonical tags rather than consolidating signals back to page one. Incorrect canonical logic often suppresses valuable pages without throwing obvious errors. This is the kind of issue that can quietly cap performance for months if it is missed.
The mobile version of the site must reflect the same content and structure as desktop.
Differences between mobile and desktop still cause real SEO and conversion problems. Content omissions, broken internal links or altered templates on mobile are common failure points during migrations.
Technical SEO determines whether your migration preserves value or deletes it. If crawling, redirects and indexation aren’t controlled before launch, rankings can plummet.
This phase only applies if the domain itself is changing.
When a domain changes, risk increases across the entire migration. Even if URLs, content and templates remain the same, search engines treat the new domain as a new entity. Trust, history and ranking signals need to transfer cleanly.
All analytics and tracking properties need to reflect the new domain from day one.
If properties are not updated, performance issues become harder to diagnose. Specifically, any traffic drops may not be visible immediately.
Before launch, confirm that reporting is aligned to the new domain and that historical data will remain usable for comparison.
Every URL on the old domain should resolve cleanly to its equivalent on the new domain.
This includes high traffic pages, as well as URLs and pages that may no longer be linked internally but still receive visits or links. Incomplete redirect coverage is one of the most common causes of sustained ranking loss after a domain migration.
This step is central to any domain migration project plan because it determines whether authority moves with the site or gets left behind.
Changing domain means resetting trust, unless you transfer it properly. Without full redirect mapping and effectively implemented redirects, authority doesn’t move with you.
For most websites, using analytics platforms (such as GA4) is how migration impact is understood in the days immediately after launch.
If tracking breaks or data becomes inconsistent, it becomes difficult to tell whether changes in performance are real or measurement-related. That uncertainty slows decisions at the point where issues are easiest to fix.
This phase exists to make sure performance data remains reliable through the migration and that any paid activity continues to work as expected.
Before launch, confirm that analytics tracking is present and firing correctly across the site.
This needs to be checked on the page types that actually matter to the business; on ecommerce websites, this would be category pages, product pages and checkout steps. Tracking issues are common during migrations because templates change, scripts are moved or consent logic behaves differently on the new site.
These problems are rarely obvious straight away. More often, they surface after reports stop making sense or revenue drops without a clear explanation. Catching them before launch removes a major source of uncertainty post-migration.
If the domain or site structure is changing, analytics properties need to reflect that change.
Keeping your analytics setup aligned ensures you can assess impact quickly and make informed decisions in the days following launch, when small issues can still be corrected with minimal disruption.
If paid campaigns are running, destination URLs need to be reviewed and updated before launch.
Domain or URL changes can cause ads to break immediately. When that happens, spend continues but traffic and conversions do not. This is one of the fastest ways for a migration to create unnecessary revenue loss.
If tracking breaks, you lose visibility at the exact moment you need it most. Without reliable data and updated paid links, you can’t separate real performance issues from measurement errors, and that delays fixes.
Once the site is live, the priority shifts to validation.
Even well-planned migrations surface issues after launch. The goal at this stage is to find and fix them quickly, before they affect performance more widely.
Run a full crawl as soon as the site goes live. This shows how search engines can actually access and interpret the site. It is also the fastest way to identify problems introduced at launch.
When reviewing the results of the website crawl, prioritise issues that tend to surface at scale after migrations:
Broken internal links: These usually appear when URLs change and links are not updated.
Redirect behaviour: Check that redirects resolve cleanly and consistently, without redirect chains.
Incorrect status codes: Pages returning the wrong status can drop out of the index or block crawling entirely.
Missing or inconsistent metadata: Gaps or duplication here can affect how pages are indexed and displayed.
Automated crawls do not catch everything.
Use targeted checks on areas that are high risk or business-critical. This includes key templates, filtered pages, pagination behaviour, mobile rendering and any areas where logic differs from the legacy site.
Spot checks are most valuable where a small issue could have a large impact, such as on high traffic category pages or checkout journeys.
In the first days after launch, monitoring needs to be frequent and focused.
Review rankings, organic traffic, landing page performance and crawl errors daily. Look for consistent patterns rather than one-off movements.
Early changes are easier to diagnose because fewer variables are involved. Addressed quickly, most issues can be resolved without lasting impact. Left unresolved, they tend to compound.
Launch is not the finish line, it’s where problems become visible. The faster you validate, diagnose and fix issues, the less chance they have to impact performance.
A website migration is easier to manage when the process is clear. A structured SEO migration checklist helps teams prioritise the right work, reduce avoidable risk and keep organic performance stable while the site changes.
If you need support planning or delivering a migration, our website migration services focus on the practical SEO checks that protect performance before, during and after launch.
Klaudia Majewska is an SEO Account Manager responsible for planning, executing and reporting on SEO campaigns across a range of clients. Her work focuses on turning strategy into consistent, measurable performance through clear priorities and ongoing optimisation. Klaudia has a strong technical SEO background and works closely with emerging AI-led search formats. She specialises in making sure products and services are structured and presented in ways that perform across both traditional search results and newer AI-driven search experiences.
Now we’d like to hear yours:
Do you have a big idea that you want to bring to the market quickly via a beautiful and user-friendly website? Whether you have the details of a project ready to go or need help finishing an existing project or even starting one from scratch, our team will help you achieve the results you need to make your business profitable.
Get In Touch Today