Published
SEO Migration Services: What They Cover and How to Hire
SEO migration services plan, execute and monitor a structural website change so your search rankings and organic traffic survive it. That covers a new domain, a new CMS, a redesign with new URLs, an HTTPS move or a merger of several sites. Hire a specialist when the change alters URLs, templates or hosting at any real scale. Hire one before the design is finalized, because the cheapest fixes happen while the site is still on a staging server.
This guide is for the person who owns the budget and the result. It explains what the work includes, when to bring in outside help, what goes wrong most often, and how to judge a provider.
TL;DR
- An SEO migration service protects the search equity your current site has earned: URLs, redirects, metadata, internal links, structured data and indexing signals.
- Bring in a specialist for domain changes, replatforming, redesigns that change URLs, and site consolidations. Bring them in at the planning stage, not after launch.
- The work runs in three phases: baseline and mapping before launch, a controlled cutover, then weeks of monitoring against the baseline.
- Most failures come from a short list: wrong or missing 301 redirects, leftover noindex or robots.txt blocks, and redirects removed too early.
- Price depends on site size, the number of URLs to map and the complexity of the platform. Ask for a scoped quote based on a crawl of your site.
Table of Contents
- What SEO migration services cover
- When to hire a specialist instead of using your in-house team
- What a migration service includes
- What to expect after launch
- The mistakes that cost the most traffic
- What migration services cost
- How to choose a provider
- Our perspective
- Plan your migration with a senior specialist
- FAQ
- Sources
What SEO migration services cover
A migration is any change that alters how search engines find, crawl or understand your pages. Search Engine Land lists seven common types: replatforming, site redesign, domain change, new site structure, website consolidation, site location migration and HTTP-to-HTTPS migration.
SEO migration providers describe their scope as planning, executing and monitoring these changes. Typical moves include a new domain, a CMS switch, a redesign with new URL structures, restructuring subfolders or subdomains, and changing URL patterns at scale.
Not every move carries the same risk. A hosting change with the same URLs is a lighter job than a domain change with a new structure. Google publishes separate guidance for each: one page for site moves with URL changes and another for hosting changes without URL changes. A good provider starts by telling you which of the two you are really doing, because that decides the scope.
Some moves also have smaller side effects worth planning for. An HTTPS switch, for example, touches every link you have ever published, including tracked links in affiliate programs. This walkthrough on updating HTTP affiliate links shows what that cleanup looks like in practice.
When to hire a specialist instead of using your in-house team
Your developers can usually build the new site. The question is who owns the search consequences. Four situations make outside help worth it.
The URLs change. Every URL that changes needs a redirect to the right destination. On a site with a few dozen pages, that is an afternoon. On a site with thousands of product, category and blog URLs, it is a mapping project with its own quality checks.
The domain changes. A domain move asks Google to transfer its understanding of the whole site to a new address. There is little room for a second attempt.
Several things change at once. Google recommends splitting large site moves into smaller steps where possible and changing one major variable at a time, such as moving the domain first and changing the layout later. If your project plan combines a new domain, new CMS, new design and new content, a specialist can sequence it or, if the business needs one launch date, plan the risk around it.
Organic search pays the bills. If organic traffic drives a meaningful share of leads or revenue, a temporary dip is a budget problem, not a technical curiosity. Someone senior should be accountable for it.
Small brochure sites moving to a new platform with unchanged URLs can often be handled with a solid checklist. This plan for platform migrations on small sites is a good example of the pre-launch checks that apply.

What a migration service includes
The scope below is how we structure the work. The sequence matters more than any single task.
Before launch: baseline and mapping
This phase decides whether the migration succeeds. The core deliverables:
- A full crawl of the current site. Every indexable URL, with its title, headings, canonical tag, status code and internal links.
- A performance baseline. Export organic clicks, impressions, average positions and top landing pages from Search Console, plus analytics data. Practical migration guidance says to measure post-launch traffic and visibility against this baseline, so you cannot skip it.
- A URL map. Each old URL paired with the closest equivalent on the new site. Pages with backlinks or strong traffic get checked by hand.
- A staging review. The new site is crawled before launch to confirm redirects resolve, metadata carried over, structured data is rebuilt, internal links point to final URLs, and noindex or robots.txt rules from the test environment are gone.
- A tracking check. Analytics and conversion events fire correctly on the new templates, so you can see what the move did. Our Google Analytics consulting guide covers what good setup looks like.
During launch: the cutover
On the day, the work is verification, not hope. Redirects are tested against the URL map. The sitemap is updated and submitted. Server capacity is checked, since insufficient server capacity is a known cause of migration trouble. For a hosting change, Google recommends monitoring server logs on both the old and new servers, checking DNS propagation with public tools around the world, and watching the index coverage reports in Search Console.
For a domain change, the Search Console change of address process is part of this step. Follow Google’s current instructions on its site-move page.
After launch: monitoring and repair
Launch day is the start of the observation period, not the end of the project. Expect weeks of monitoring:
- Indexing transitions. Compare old and new sitemaps. Indexed URLs from the old sitemap should decline over time while indexing of the new URLs rises, as Pantheon describes.
- Crawl errors. Google advises checking Search Console reports for not-found errors and other crawl errors and fixing them quickly.
- Traffic by segment. Compare clicks, impressions and positions by page group, device and country against the baseline. A good report separates the sections that recovered from the ones that did not.
- Source and medium checks. Confirm in GA4 that organic traffic is attributed the way it was before. This guide to seeing traffic by source and medium shows the report to use.
What to expect after launch
Set expectations with your team before the switch. For medium-sized sites, Google says it can take a few weeks or more for new URLs to appear gradually during a move, and that temporary ranking fluctuations are normal. Submitting a sitemap can speed discovery.
The useful distinction is between temporary volatility and a sustained, disproportionate loss. The first is expected while Google recrawls. The second points to a technical problem, and the baseline is how you tell them apart.
A second point is often missed. From a search engine’s view, a migration is an extended period of reprocessing: crawlers keep visiting legacy URLs, following redirects and reassessing how signals transfer over weeks or months. If redirects change or break during that time, confidence in the move weakens. That is why redirects should stay in place well past the day traffic stabilizes. Pantheon notes that Google recommends keeping migration redirects for at least one year.
The mistakes that cost the most traffic
The same few problems show up again and again.
| Mistake | What happens | How it is caught |
|---|---|---|
| Missing or wrong 301 redirects | New pages lose the value of the old ones and visitors hit errors. Shopify names this a leading cause of post-migration traffic loss. | Test every URL in the map against the live redirect before and after launch. |
| Noindex or robots.txt left from staging | The new site stays invisible to search engines until the setting is corrected. | Crawl staging and production for index directives and blocked paths. |
| Sitemaps not updated | Google discovers new URLs more slowly. | Submit the new sitemap at launch and compare coverage over time. |
| Server capacity too low | Crawl and user errors during the recrawl surge. | Load check before cutover, log monitoring after. |
| Redirects removed early | Signals stop transferring when traffic looks stable. | Keep them for at least a year. |
Google’s list of common problems matches this table: leftover blocks, incorrect redirects, crawl errors, insufficient server capacity and outdated sitemaps.
If traffic drops after launch, work in this order. First confirm the site is indexable. Then test the redirect map for gaps and chains. Then compare page groups to the baseline to see where the loss sits. For missing redirects, the usual fix is a 301 rule pointing to the correct destination. Once the technical layer is clean, the remaining gap is a content and relevance question, which is where our guide to improving organic traffic picks up.
What migration services cost
No honest provider can quote a migration without seeing the site. Price follows a handful of drivers:
- Number of URLs. More URLs means more mapping, more redirect testing and more manual review of high-value pages.
- Type of move. A domain change with a new structure takes more work than a same-URL hosting move.
- Complexity. Multiple languages, hreflang tags, structured data and large internal link networks each add line items.
- Monitoring length. A longer observation period with reporting costs more than a launch-week check.
- Who builds the site. If the SEO work is separate from development, coordination time is part of the cost.
Cost estimators break SEO preservation into line items such as the pre-migration crawl, URL mapping, redirect implementation, hreflang preservation, structured data re-implementation, internal link rebuild and post-launch monitoring. Ask any provider to scope against those same pieces so you can compare quotes like for like.
The price of a migration should also be weighed against the organic revenue it protects. If search drives a large share of your pipeline, a quote that includes senior oversight and post-launch monitoring is cheaper than a recovery project later.
How to choose a provider
Provider pages for this keyword tend to promise “no traffic loss.” Nobody controls how Google reprocesses a site, so look at process instead of promises.
- Who does the work. Ask who will map the URLs and who will check the redirects. A senior name in the pitch and a junior on the project is the usual gap.
- When they join. The best results come when the specialist reviews the design and sitemap before development starts.
- What the deliverables are. Crawl export, URL map, staging audit, launch checklist, post-launch report. If the proposal lists only “SEO migration,” ask for the pieces.
- How they report. You should see baseline versus actual by page group, not a general traffic chart.
- What happens after launch. Monitoring and redirect maintenance should be in the scope or in a clear follow-on.
- Fit with your sector. If you run a software or IT business, our guides to SEO for IT companies and choosing a SaaS SEO agency show how we think about those sites.
Our perspective
Most migrations fail on ownership, not on technology. The developer assumes SEO is covered by the design team, the design team assumes the agency has it, and the agency joined after the URLs were set. Nobody is accountable for the redirect map.
Our answer is simple. A senior specialist reviews the plan, builds the URL map, checks staging and watches the results after launch, with no handoff to someone junior in the middle. We do not sell generic packages, because a migration for a 40-page services site and one for a catalog with thousands of products are different jobs.
We also treat the migration as a chance to fix what was already weak: thin pages, poor internal linking, broken tracking, weak conversion paths. If the site has to change anyway, the move should leave you with a clearer picture of what drives growth.
Bob Belkin
Plan your migration with a senior specialist
If you are planning a domain change, replatform, redesign or consolidation, we can help you scope the SEO work before development locks the structure. Our team works directly with you, from the baseline and URL map through launch checks and post-launch reporting. Our SEO, GEO and AIO service is where this work sits, and our development and AI service covers the build side when you want both under one accountable lead.

If conversion matters as much as traffic during the redesign, our conversion rate optimization service and our website conversion audit guide help you keep the new site working harder than the old one. To start a conversation, visit Page One Brand.
FAQ
What is SEO migration?
SEO migration is the process of changing a website’s domain, platform, structure or hosting while preserving its search visibility. It includes planning, redirect mapping, launch checks and monitoring afterward. The goal is for search engines to transfer what they know about your old URLs to the new ones.
How long until rankings stabilize after a migration?
Google says that for medium-sized sites, new URLs can take a few weeks or more to appear gradually, and temporary fluctuations are normal. Larger or more complex moves can take longer. Judge progress against your pre-launch baseline, not against day-one numbers.
Should I change my design and domain at the same time?
Google recommends changing one major variable at a time where possible, such as the domain first and the layout later. If a single launch is a business requirement, the plan needs more testing and tighter monitoring. A specialist can help you decide which path fits.
How long should I keep redirects in place?
At least a year. Pantheon, summarizing Google’s recommendation, advises against removing migration redirects as soon as traffic looks stable. Keep them longer if old URLs still have backlinks or bookmarked traffic.
Sources
- Site Migration SEO Guide: Preserve Rankings & Traffic, Search Engine Land
- SEO Website Migration Services: A Complete Guide, CapraSEO
- Site Moves and Migrations, Google Search Central
- Changing Your Web Hosting and SEO, Google Search Central
- A Phase-by-Phase SEO Website Migration Checklist, Pantheon
- SEO migration guide: avoid ranking declines, URLlo
- How To Recover Your Traffic After a Web Migration, Shopify
- HTTP to HTTPS Affiliate Links: How to Update Them Safely
- How do I see traffic by source and medium in GA4?
Recommended
Want a specialist to look at your own situation?
Send an inquiry
