Site migration SEO
Site migration SEO protects search visibility when URLs, domains, platforms or templates change. It covers benchmarking before launch, complete redirect mapping, staging tests, launch-day validation and monitoring until search engines have processed the change.
By ROI SynthUpdated 11 min read
The problem this solves
Google's documentation on site moves describes a process that is simple in principle: map old URLs to new ones, redirect permanently, update internal links and sitemaps, and monitor. In practice, migrations fail on detail: forgotten URL patterns, staging noindex tags carried to production, or redirects pointing to the homepage.
Traffic losses after migrations are common and often avoidable. They usually trace back to incomplete redirect maps, changed content or structure on the new site, or technical regressions introduced by the new templates.
What the work includes
- Pre-migration benchmark of rankings, traffic and indexed pages
- Full URL inventory and one-to-one redirect map
- Staging review of templates, metadata, directives and rendering
- Launch-day checklist and validation crawl
- Post-launch monitoring and issue triage
How the work is done
Benchmark
Record performance by page and template before anything changes.
Map every URL
Build the redirect map from crawls, sitemaps, analytics, logs and backlink data.
Test on staging
Validate templates and redirects before launch, with staging protected from indexing.
Launch and validate
Crawl the old URL list on launch day and fix gaps immediately.
Monitor
Track indexing, traffic and errors for weeks after launch.
Any change that moves URLs, domains or templates

A site migration is any change that alters how search engines find and understand your pages: a new domain, a move from HTTP to HTTPS, a new platform or framework, a restructure of URLs, a merger of two sites, or a switch to a new rendering approach. Migrations are where search visibility is most often lost, not because migrations are inherently dangerous, but because the SEO work is left until the final week, when there is no time to do it properly.
Coded sites migrate often. Teams move from a page builder to Next.js, from the Pages Router to the App Router, from a monolith to a headless CMS, from one hosting provider to another. Each can change URLs, status codes, rendering or metadata without anyone intending to. Migration SEO makes sure the new site keeps what the old one earned.
- Changing domain or consolidating several domains into one.
- Moving to a new CMS, framework or hosting platform.
- Restructuring URLs, categories or the navigation hierarchy.
- Merging content from an acquired business or a separate microsite.
- Changing how pages render, for example from client-side to server-side.
Before, during and after: the three phases of a safe migration
Migration SEO is a sequence of checks spread across the project, not a single task. The most valuable work happens before launch, when changes are still cheap.
| Phase | What happens | Why it matters |
|---|---|---|
| Benchmark | Crawl the old site; export Search Console and analytics data; record top pages, links and rankings | You cannot tell what was lost without knowing what you had |
| Map | Every old URL mapped to its best new equivalent, one to one where possible | Redirects are how links, visits and signals carry over |
| Test on staging | Templates, metadata, canonicals, robots, structured data and redirects checked before launch | Problems found here cost minutes; after launch, weeks |
| Launch day | Redirects tested live; robots and noindex checked; sitemaps submitted; Search Console updated | The first hours catch the mistakes that matter most |
| Monitor | Indexing, errors, traffic and rankings watched against the benchmark for weeks | Search engines process a migration gradually |
The redirect map is the heart of the migration

A redirect map lists every old URL that matters and the new URL it should lead to. "Every URL that matters" includes more than the current sitemap: pages with external links, pages that receive search visits, old URLs that still get traffic from previous migrations, PDFs and images that other sites link to. We build the list from crawls, Search Console, analytics and link data, so nothing valuable is missed.
Each old URL is mapped to the closest equivalent, not to the homepage. Where a page has no equivalent, we decide with you whether it needs a new home, a redirect to a parent topic, or a deliberate removal. On a coded site the map becomes a configuration file or middleware rule set, reviewed in a pull request and tested automatically against the live site after launch.
One hop
Old URLs redirect straight to their final destination, never through a chain of intermediate redirects.
Permanent status
301 or 308 responses for permanent moves, so search engines transfer signals to the new URLs.
Pattern rules with care
Rules that map whole sections are tested against real URLs, because patterns break in edge cases.
Kept for the long term
Redirects stay in place for as long as the old URLs might be requested, which is usually years.
What we test before launch
Staging is where a migration is won or lost. We check the new site as search engines will see it, template by template, and compare it with the old one. Anything that changed without a reason is flagged.
- Every important template renders its main content in the initial HTML response.
- Titles, descriptions and canonicals are generated correctly, including on dynamic routes.
- Structured data from the old site is present and still accurate.
- Internal links point to new URLs directly, not to old URLs that will redirect.
- The staging site itself is blocked from indexing, and the block is not copied to production.
- Redirects from the map resolve correctly in a test run against the staging host.
- Performance on key templates is no worse than on the old site.
The first 48 hours
On launch day we run the redirect map against the live site, check robots and indexing directives, submit the new sitemaps, and verify the new property in Search Console. For a domain change we use Search Console's change of address tool, which tells Google about the move explicitly.
Over the following two days we watch server logs or hosting analytics for spikes in 404 errors, check that key pages are being crawled, and fix anything unexpected immediately. Fast fixes in this window prevent small mistakes from becoming lasting losses.
A hypothetical migration from a page builder to Next.js
A hypothetical architecture practice moves its site from a hosted page builder to a custom Next.js site. The old site has 140 indexed URLs, including project pages with external links from design publications, and a blog whose URLs include dates.
The benchmark records which pages bring visits and which have links. The map sends each project page to its new address under /projects, each blog post to its new undated URL, and a handful of thin tag pages to the relevant project category. Staging checks reveal that project pages load their image galleries client-side with no text description in the initial HTML; the template is changed to render a description and the first image on the server. Launch-day checks confirm every mapped URL redirects in one hop. Over the following weeks, indexing of new URLs and visits to project pages are compared with the benchmark, and two missed URLs found in logs are added to the map.
When to involve us
The earlier the better. Ideally we join when the new site's structure is being planned, so URLs and templates are designed with search in mind rather than corrected afterwards. At minimum, we need a few weeks before launch for benchmarking, mapping and staging checks.
| When | What happens | What you see |
|---|---|---|
| Planning | URL structure and templates reviewed; benchmark taken | Benchmark report and structural recommendations |
| Build | Redirect map compiled and reviewed; metadata rules specified | The redirect map and template requirements |
| Pre-launch | Staging tested against the checklist; issues fixed | A launch-readiness checklist with every item resolved |
| Launch | Live checks, sitemaps, Search Console updates | Launch-day log of checks and fixes |
| Post-launch | Weekly monitoring against the benchmark for at least two months | Comparison reports and follow-up fixes |
How the migration is judged
Success is measured against the benchmark. We compare indexed pages, impressions, clicks and visits to key pages before and after, along with crawl errors and redirect performance. Some fluctuation in the first weeks is normal as search engines process the change; the report distinguishes expected turbulence from real problems that need fixing.
We also report what the migration improved. Many migrations are an opportunity to fix long-standing problems — slow templates, duplicate URLs, weak metadata — and those gains should be visible in the months after launch.
What we need from you
We need access to the old site's Search Console and analytics for the benchmark, access to the staging environment, and a link to the development team so redirect and template issues can be fixed before launch. We also need the launch date as early as possible, and a commitment that the launch will not happen until the pre-launch checklist is complete — or, at least, that any open items are a conscious decision rather than a surprise.
Consolidating domains and changing brands
Domain changes need extra care because every signal tied to the old domain has to be transferred. When businesses merge, rebrand or consolidate several sites into one, the redirect map spans domains, external links point at old addresses for years, and Search Console needs a property for each old and new domain.
We keep old domains registered and redirecting for the long term, use Search Console's change of address tool where it applies, and update the profiles and listings that reference the old domain — business profiles, social profiles, partner sites — so the new domain is consistently described. Where several old sites are merged, the map decides which page on which site becomes the surviving version of each topic, so the new site does not inherit their duplications.
Migration mistakes that cause lasting losses
Most migration losses trace back to a short list of avoidable errors.
Redirecting everything to the homepage
Search engines tend to treat these as removed pages, and visitors land somewhere unhelpful.
Mapping only the sitemap
Forgetting old URLs that still receive links or visits, such as retired campaigns and PDFs.
Redirect chains
Old URLs redirecting through previous migrations' redirects, slowing crawling and losing signals.
Changing everything at once
New domain, new URLs, new design and new content in one launch, which makes problems hard to diagnose.
Stopping monitoring too soon
Declaring success after a week, before search engines have processed most of the change.
Letting the old domain lapse
Allowing an old domain to expire, so every redirect and link it carried disappears.
Planning for what goes wrong
Even careful launches have surprises. A rollback plan, agreed before launch, decides what happens if something serious appears: which issues justify reverting, who decides, and how quickly the old site can be restored. Most issues are fixed forward with a quick change, but knowing the fallback reduces pressure on launch day.
We also schedule launches sensibly: not just before a holiday or a busy sales period, and at a time when developers are available to respond. On coded sites with preview deployments and version control, reverting is usually quick, which is another reason to make sure the old site's configuration is preserved until the new one is stable.
Moving from a page builder to a coded site
Moving from a hosted builder to a custom Next.js or similar site is one of the most common migrations we support, and it has its own pattern of risks. Builders handle many details silently — sitemaps, redirects, image optimisation, metadata defaults — that the new site must handle explicitly. And builders often create URLs nobody remembers, such as old blog paths, gallery pages and form confirmation pages, which still receive links or visits.
- Export every URL the builder ever served, not only the ones in its current sitemap.
- Recreate per-page titles and descriptions; builder defaults are often lost in exports.
- Rebuild forms with tracking intact, so enquiries are not lost on launch day.
- Replace builder image handling with sized, optimised images in the new templates.
- Check that blog and media URLs either keep their paths or redirect one to one.
- Move analytics and Search Console verification to the new site before switching DNS.
A coded site typically ends up faster, cleaner and easier to maintain than the builder it replaces. The migration work makes sure it also keeps the visibility the old site had earned.
The deliverables, listed
Migration SEO produces a short set of working documents and checks, tied to the project's milestones.
- A benchmark of indexed pages, search performance and key pages before the change.
- A complete redirect map, reviewed and tested against the live site after launch.
- A staging checklist completed and signed off before launch.
- A launch-day log of checks and fixes, and weekly comparison reports afterwards.
How migration work connects to other work
A migration is often the right moment for a content audit, so content that should not survive is not carried across, and for new information architecture. When the visual design changes too, website redesign SEO covers the decisions made in wireframes and templates. After launch, indexation management keeps old and new URLs from competing.
For sites in several countries or languages, hreflang implementation must be rebuilt for the new URLs, since every alternate annotation points at addresses that are about to change.
Which offer includes migration SEO
Migration SEO is delivered within the SEO offer, from $200 per month, typically for the months around the launch. The scope depends on the number of URLs, templates and domains involved.
When the migration is to a new Next.js site we build, the Next.js + TypeScript Website Build, from $1,000 one time, includes the redirect map and post-launch checks in its agreed scope, so the build and the migration are handled together.
Questions about migrations
What teams usually ask before moving their site.
"Will we lose rankings?"
Some short-term movement is common. A careful migration aims to keep what you have and recover quickly; nobody can guarantee zero change.
"Our launch date is next week"
Tell us anyway. A rapid benchmark, redirect check and launch-day review are far better than nothing.
"Can we change the URLs to be cleaner?"
Yes, if the benefit is clear and every old URL is redirected. We weigh the gain against the risk with you.
"How long should redirects stay?"
As long as the old URLs might be requested — in practice, years. They cost almost nothing to keep.
Example deliverable
How progress is evaluated
- Share of old URLs redirecting correctly to relevant destinations
- Organic traffic and indexed pages against benchmark
- Crawl errors after launch
Who this is for
- Domain changes and rebrands
- Platform and CMS migrations
- Redesigns that change URLs or templates
Limits and honest caveats
Common questions
questions
What is site migration SEO?
Site migration SEO protects search visibility when URLs, domains, platforms or templates change. It covers benchmarking before launch, complete redirect mapping, staging tests, launch-day validation and monitoring until search engines have processed the change.
What does a site migration SEO engagement include?
The work includes pre-migration benchmark of rankings, traffic and indexed pages, full URL inventory and one-to-one redirect map, staging review of templates, metadata, directives and rendering, launch-day checklist and validation crawl and post-launch monitoring and issue triage.
What problems does site migration SEO solve?
Traffic losses after migrations are common and often avoidable. They usually trace back to incomplete redirect maps, changed content or structure on the new site, or technical regressions introduced by the new templates.
How is site migration SEO carried out?
It runs in 5 stages: benchmark, map every URL, test on staging, launch and validate and monitor. Record performance by page and template before anything changes.
Who is site migration SEO a good fit for?
It suits domain changes and rebrands, platform and CMS migrations and redesigns that change URLs or templates.
How do you measure the results of site migration SEO?
Progress is measured with share of old URLs redirecting correctly to relevant destinations, organic traffic and indexed pages against benchmark and crawl errors after launch.
What are the limits of site migration SEO?
Some short-term fluctuation is normal even in well-run migrations. Combining a migration with major content changes makes outcomes harder to attribute.
Can ROI Synth carry out the site migration SEO work, or only recommend it?
Implementation is included. Within the agreed scope we fix templates, metadata, internal links and redirects, and build the landing pages ourselves, on your existing platform or on a Next.js and TypeScript build when a rebuild is part of the project, starting with steps such as “Pre-migration benchmark of rankings, traffic and indexed pages”. Every completed item is recorded with evidence in a weekly progress sheet.
How long does site migration SEO take?
The 5 stages (benchmark, map every URL, test on staging, launch and validate and monitor) fit the proposal's four weekly phases. When the agreed scope can be delivered in a month, the proposal commits to completing it in the first month, subject to timely access and approvals. Search engines then take weeks or months to re-evaluate the changes.
Is site migration SEO guaranteed to bring more traffic or leads?
No. Rankings, traffic, leads and sales depend on search engines, competition and your market, so they are not guaranteed. What is committed is the agreed work, completed and evidenced, and measurement of share of old URLs redirecting correctly to relevant destinations and organic traffic and indexed pages against benchmark.
Sources and further reading
Contact us about Site migration SEO
Tell us about your website and goals. We will say plainly whether this is the right offer, what it would include, and what it can and cannot achieve.
Discuss site migration SEO for your business
Tell us about your website and goals. We will confirm whether this work is the right priority, what it would include and how it would be delivered.
