Website Migration SEO Checklist: Move a Website Without Losing the Signals That Already Work
Changing domains, CMS platforms, hosting, URL structures or rebuilding a website can improve the business—but it can also disconnect the URLs, links, content and search signals that already earn traffic. This checklist helps teams plan, test, launch and monitor a migration with SEO continuity built in from the start.
What counts as a website migration?
From an SEO perspective, a migration is any substantial website change that can alter how users or search engines reach, crawl, interpret or index existing content.
Moving from one domain to another, including rebrands and domain consolidations.
Moving from Wix, Shopify, WordPress, WooCommerce or another system to a different platform or build.
Changing folders, slugs, category structures, language paths or page locations.
A project where templates, navigation, content and often URLs change together.
Protocol and hostname changes such as www to non-www can affect URL identity.
A hosting move can be lower risk when URLs stay unchanged, but DNS, downtime, server responses, performance and crawling still need attention.
Google Search Central’s current site-move guidance covers domain, protocol and URL-path changes and recommends planning URL mappings, permanent redirects, testing and post-move monitoring.
Not every migration carries the same SEO risk
Hosting move with the same domain, URLs, content and internal links, assuming downtime and server configuration are controlled.
Redesign or CMS migration where most URLs remain stable but templates, navigation, content rendering or performance change.
Domain change, major URL restructure, large content consolidation, replatforming and redesign happening at the same time.
Google explicitly advises changing one major thing at a time where practical—for example, moving the domain first and changing layout later—because simultaneous changes make problems harder to isolate. Temporary ranking fluctuations can occur while Google recrawls and reindexes the move. See Google Search Central’s site-move guidance.
Phase 1: Pre-migration SEO checklist
Write down whether the project changes domain, protocol, CMS, URL structure, hosting, design, content or all of them. This determines the risk and testing scope.
Create an inventory of indexable URLs, status codes, titles, descriptions, canonicals, headings, internal links and important media or file URLs.
Identify URLs and queries already earning impressions and clicks so they do not disappear unnoticed during the move.
Pages with valuable external links deserve special attention because broken or irrelevant redirects can waste earned authority.
Capture organic traffic, leads, purchases, calls, form submissions and key landing-page performance before launch.
Include files, database, media and critical configuration. Migration planning should include a rollback path, not only a launch plan.
Do not discover on launch day that a former vendor controls the account needed to complete the move.
Migration is a good opportunity to remove genuine duplication and outdated content—but decisions should be based on evidence rather than appearance alone.
Use Vylino’s Website Audit Checklist to build the baseline before the migration starts.
Phase 2: Build the old-to-new URL map
The URL map is the central migration document. Every important existing URL should have a deliberate outcome.
| Old URL outcome | What to do |
|---|---|
| Same purpose, same URL | Keep the URL unchanged where practical. |
| Same purpose, new URL | Map old URL → closest equivalent new URL using a permanent redirect. |
| Several old pages merged | Redirect each relevant old URL to the consolidated page if it genuinely covers their purpose. |
| Content intentionally removed | Return an appropriate 404 or 410 when there is no relevant replacement. |
| Page moved only for cosmetic slug reasons | Reconsider whether changing the URL creates enough value to justify the migration work. |
Phase 3: Staging-site migration checklist
Use appropriate access controls or temporary noindex rules during development, then explicitly remove those controls before the live launch.
Review service pages, articles, locations, products, categories, search, forms, checkout and any custom post types used by the business.
A visually cleaner redesign should not accidentally remove the information that helped an important page rank or convert.
New pages should point to the intended live destination, not staging URLs, old-domain URLs or obsolete paths.
Do not leave navigation and body links pointing to old addresses and rely on redirects to fix them.
Update URLs, organization details, breadcrumbs, products, articles and other schema to match the visible content on the new site.
Forms, calls, WhatsApp, ecommerce, booking and other goals should be testable before the migration is considered ready.
A migration should not replace an old site with a heavier experience that reduces usability on real devices.
Phase 4: Redirect strategy
When URLs change, use server-side permanent redirects where technically possible. Google currently recommends permanent HTTP redirects such as 301 or 308 for permanent URL moves and recommends sending old URLs directly to the final destination rather than through long redirect chains. See Google Search Central.
The redirect file or rules should be ready and tested—not built reactively after users discover broken pages.
Old URL → final URL is cleaner than old → intermediate → new.
Destination relevance matters. A discontinued service page should not automatically go to the homepage if a closer useful destination exists.
PDFs, images and downloads may have direct traffic or external links too.
Phase 5: Launch-day SEO migration checklist
Test a representative sample of high-traffic, high-link and structurally varied URLs, not only the homepage.
A beautifully migrated site cannot perform if production inherits development restrictions.
Canonical tags should reference the final production URLs.
The sitemap should list canonical live URLs that return successful responses.
For domain moves, verify old and new properties and their relevant variants before completing the migration steps.
SEO continuity is not enough if the new site loses the leads or sales it receives.
Confirm priority URLs return 200, retired URLs behave as intended and accidental blocks are absent.
Compare the live crawl against the pre-migration inventory to identify missing pages, broken links, redirect chains and metadata changes.
Extra steps for a domain migration
A domain move adds another layer because Google must associate the existing site with a different host.
Include relevant www/non-www and subdomain variants rather than assuming one property covers every migration signal.
Google’s June 2026 documentation update specifically clarified that Change of Address requests should cover all relevant subdomain variants, including www and non-www variants, during domain migrations.
Important profiles, directories, social accounts and owned properties should link directly to the new domain rather than depending forever on redirects.
Review Search Console and domain history for legacy issues before moving a healthy site onto it.
Google’s June 17, 2026 documentation update explicitly added guidance about domain variants and the Change of Address tool during domain migrations. See Google Search documentation updates.
If you are only changing hosting and URLs stay the same
A hosting-only migration is usually simpler because the public URLs and page identities remain unchanged, but it still needs operational discipline.
This can make DNS changes propagate more predictably, depending on your infrastructure and provider.
A short overlap can reduce risk if the new server shows unexpected errors.
HTTPS, redirects, caching, headers, image paths, email delivery, scheduled jobs and application dependencies may differ between hosts.
Google notes that after a migration, crawling may temporarily increase as old and new URLs are processed. See Google Search Central.
If hosting choice is part of the project, Vylino also maintains a comparison resource on hosting providers that offer website migration.
Phase 6: Post-migration monitoring checklist
Watch important queries, pages, coverage changes and unexpected crawl/indexing issues rather than judging success from one day of rankings.
New errors often reveal missed redirects, old internal links or external links pointing to retired content.
Look for specific page losses so problems can be diagnosed rather than treating “traffic down” as one website-wide issue.
A migration can preserve search traffic but still reduce leads if forms, CTAs or page journeys changed.
Do not remove migration redirects as soon as the launch appears successful; old URLs may continue to be visited and crawled.
Direct links to final URLs reduce unnecessary reliance on redirects, especially on profiles and properties you control.
Record what changed, what failed and what required remediation so future updates do not repeat the same risks.
Will a website migration cause a ranking drop?
No responsible migration plan can guarantee completely unchanged rankings. Google states that temporary ranking fluctuations can happen while a move is recrawled and reindexed, and that processing can take time depending on site size and server speed. See Google Search Central’s migration guidance.
The objective is therefore not to promise “zero movement.” It is to remove preventable causes of loss: missing redirects, irrelevant destination mapping, blocked crawling, wrong canonicals, deleted content, broken internal links, missing analytics and unmonitored launch errors.
Migration, redesign and rebuild are related—but not the same decision
If the current website is merely dated, a full technical migration may be unnecessary. If the underlying platform, architecture or maintainability is the real problem, rebuilding may be justified.
Use the Website Redesign vs Rebuild guide first if you have not yet decided whether the existing foundation should be retained.
Planning a website move and want the SEO handled before launch—not repaired afterwards?
Vylino can audit the existing site, inventory important URLs, plan redirects and internal linking, support a platform or website rebuild, verify launch settings and monitor the migration after go-live. The scope can be limited to migration SEO or combined with development and ongoing support where needed.
Frequently asked questions
What is a website migration SEO checklist?
It is a structured set of tasks used to preserve crawlability, URL signals, content, internal links, analytics and search visibility when a website changes domain, CMS, hosting, URL structure, protocol or underlying platform.
Should every old URL redirect to the new homepage?
No. Changed URLs should normally redirect to the closest relevant replacement. Irrelevant mass redirects can create a poor user experience and may be treated as soft 404s.
Should I use 301 or 302 redirects during a permanent migration?
For permanent URL moves, Google recommends server-side permanent redirects such as HTTP 301 or 308 where possible. Temporary redirects are for genuinely temporary situations.
Can I change domain, CMS and design at the same time?
It is technically possible, but it increases complexity. Google recommends changing one major thing at a time where practical because it makes issues easier to isolate.
Do I need the Change of Address tool when moving from HTTP to HTTPS?
No. Google’s current guidance says the Change of Address tool is for domain migrations, not HTTP-to-HTTPS moves.
How long does SEO migration recovery take?
There is no fixed timeline. Google notes that rankings can fluctuate temporarily and that recrawling and reindexing time depends partly on site size, URL volume and server speed.
Is changing hosting considered a website migration?
Yes operationally, although SEO risk is generally lower when URLs and content remain unchanged. DNS, downtime, performance, server responses, HTTPS and crawlability still need testing.
Related Vylino resources and services: Website Audit Checklist · Redesign vs Rebuild · WordPress Maintenance Checklist · Website Development · Website Maintenance