A site migration is one of the highest-risk events in a website’s life. Done right, it is invisible to Google. Done wrong, it costs you months of organic traffic and takes the better part of a year to recover. Understanding what SEO migration services include, what they should cost, and what separates a credible vendor from someone just along for the invoice is the point of this piece.
SEO migration services cover the technical work required to move a website — to a new domain, platform, or URL structure — without losing organic search rankings. A professionally managed migration involves a pre-migration audit, redirect mapping of every URL, staging validation, Search Console configuration, and post-launch monitoring over 4-8 weeks. Pricing ranges from $1,500 for small sites to $15,000 or more for large ecommerce catalogs. According to a Search Engine Journal study of 892 domain migrations, the average site takes 523 days to fully recover organic traffic after a domain change, and 17% never return to pre-migration levels.
What “SEO Migration Services” Actually Covers
The phrase gets used loosely. Some agencies mean they will set up your 301 redirects and hand you a checklist. Others mean a fully managed process from pre-launch audit to 90-day post-launch monitoring. Before you compare prices, you need to know which one you are buying.
A complete SEO migration engagement covers six distinct workstreams. If a vendor’s scope of work does not address all six, ask why.
1. Pre-migration audit.
This is a baseline crawl of your existing site using tools like Screaming Frog or Ahrefs. The output is a URL inventory: every indexable page, its current traffic, its backlinks, and its ranking keywords. This document is the reference against which everything after launch is measured. Skipping it is the most common reason migrations fail quietly — there is no baseline to compare to, so traffic drops are only noticed months later.
2. Redirect mapping.
Every old URL gets mapped to a destination on the new site. One row per URL. 301 redirects are the standard for permanent moves. According to Google Search Central’s official site migration documentation, chaining redirects should be kept to three hops or fewer — each additional hop adds user latency and dilutes crawl efficiency. On a site with 200 pages, this is a spreadsheet. On an ecommerce store with 5,000 SKUs, it is a project in itself.
3. Staging environment testing.
Before the new site goes live, an SEO specialist needs to review it on staging for: canonical tag accuracy, robots.txt configuration (new sites are often accidentally left in noindex from the development phase), internal link integrity, page title and meta description carry-over, Core Web Vitals baselines (LCP, INP, CLS), and mobile rendering. Google completed mobile-first indexing in 2023, which means the mobile version of your new site is the one Google’s index will be built from. Testing only on desktop is not adequate.
4. Launch-day execution.
Redirects go live. The Change of Address tool in Google Search Console is submitted (required for domain-to-domain migrations). A new sitemap is submitted. GA4 and any tracking tags are verified against the live site. This is the one-week window with the highest density of irreversible decisions.
5. Post-launch monitoring.
The first 30 days after launch are when problems surface. Google will crawl the new site more heavily than usual post-migration, which means server load spikes can cause crawl errors. Coverage reports in Search Console need daily review for the first two weeks, then weekly through day 60. Soft 404s, redirect loops, and missing canonical tags are the most common emergencies.
6. Backlink and content audit integration.
Your existing backlinks point to your old URLs. If you have significant link equity concentrated on a handful of pages, those redirect paths need to be verified individually, not just mass-mapped. Content that was deleted or consolidated during migration needs to be tracked because removing pages that carry backlinks without redirecting them properly will cost you authority you can never get back.
The Four Migration Types, and Why Each Has a Different Risk Profile:
Not every migration is equal. The scope of SEO work required and the risk of traffic loss varies depending on what is actually changing.
| Migration Type | What Changes | SEO Risk Level | Typical Recovery Window |
| HTTPS migration (HTTP to HTTPS) | Protocol only | Low | 1-4 weeks |
| Domain change (rebrand) | Domain name, all URLs change | High | 6-18 months |
| Platform/CMS replatform | URL structure, templates, CMS | High to Very High | 3-12 months |
| Redesign (same domain, same CMS) | Templates, internal links, content | Medium | 4-12 weeks |
| Server/hosting migration | Server only, no URL changes | Low | 1-2 weeks |
| Combined (new domain + new platform) | Everything | Very High | 12-24 months |
The riskiest migration is also the most common one founders request: a new domain, a new platform, and a new visual design, all at once. This is the “we’re rebranding everything” scenario. Bruce Clay’s migration timetable guidance allocates 8-15 weeks for a mid-sized SMB migration across planning, preparation, staging, execution, and post-launch monitoring — and that is when things go smoothly.
A combined migration of this type is also the one most likely to see permanent traffic loss. A Search Engine Journal study analyzing 892 domain migrations found that on average it took 523 days for a new domain to reach the organic traffic volume of the old domain. 17% of migrations in that dataset had not recovered even after 1,000 days. Those are not worst-case numbers for migrations that ignored SEO — those are averages across the full sample.
What This Means Practically:
If your current site generates meaningful organic traffic and you are considering a full replatform plus domain change, the business case for doing both simultaneously needs to account for the fact that you may be significantly diminished in organic search for 12-18 months. Sometimes the business reasons for a combined migration outweigh that risk. But that decision should be made consciously, with the numbers on the table.
What SEO Migration Services Cost (Honest Market Ranges):
Pricing for this work varies widely and, unlike most SEO retainers, is project-scoped rather than ongoing. What drives the spread is almost entirely URL count, migration complexity, and how much of the SEO work is already done in-house.
| Scope | Typical Price Range | What Is Included |
| Small site (under 100 URLs, same domain) | $1,500 – $3,500 | Pre-migration audit, redirect map, staging review, post-launch check |
| Mid-size site (100-1,000 URLs) | $3,500 – $8,000 | Full workstreams 1-6 listed above, 30-60 day monitoring |
| Large site (1,000-10,000 URLs) | $8,000 – $18,000 | Full workstreams, content audit, backlink mapping, 90-day monitoring |
| Enterprise / ecommerce (10,000+ URLs) | $18,000 – $50,000+ | Full workstreams, schema migration, structured data, international SEO, dedicated monitoring |
These are market ranges for US mid-market agencies. Rates at offshore or distributed agencies are typically 30-50% lower for equivalent technical depth. What should never get cheaper is the audit and redirect mapping phase — those are the deliverables where cutting corners creates the 6-12 month recovery problem.
One honest caveat: there is no standard pricing model for SEO migration services. Some agencies quote hourly ($100-$250/hour for senior technical SEOs), some quote per-URL (useful for large catalogs), and some quote flat project fees. The right model depends on your site’s structure. What you want to avoid is an agency that quotes a fixed low number without ever asking about your URL inventory — that is a sign the estimate is a guess.
A data point worth knowing: an Optimum7 analysis of 4,000 AI responses and 1,000+ completed ecommerce platform migrations found that poorly executed migrations cost merchants 20-40% of organic traffic with recovery windows of 6-12 months. For a site generating $15,000/month in organic revenue, a 30% drop over 9 months is a $40,500 problem. The cost of a professional migration looks very different against that number.
The Specific Technical Deliverables You Should Request:
Before hiring any agency for SEO migration work, ask for these specific deliverables in writing. If a vendor cannot tell you what format these will be delivered in, their quote is not credible.
The pre-migration deliverables you need: a full URL crawl export showing current indexation status, rankings, and backlink count per URL; a redirect mapping document (spreadsheet with source URL, destination URL, redirect type, and mapping logic); a staging site crawl report confirming canonical accuracy, robots.txt correctness, and no accidental noindex directives; and a Core Web Vitals baseline for the new site’s key templates.
The post-launch deliverables you need: a Search Console coverage report comparison at 30 days and 60 days; a rankings comparison against pre-migration baseline for the top 50 organic landing pages; a server log check or crawl report confirming redirect chains are resolving correctly; and a backlink spot-check confirming high-authority inbound links are resolving to the correct new URLs.
Advanced Web Ranking’s SEO migration best practices analysis is worth reviewing as a technical reference for what a thorough migration process looks like from the SEO specialist’s side. Even in the best-managed migrations, their research notes a typical 10% traffic decline in the first 30 days. That is the realistic floor, not a failure.
Who Handles This Work and Who Should Not:
A web developer who is not an SEO specialist should not be solely responsible for migration SEO. This is not a criticism of developers — it is a scope problem. Migration SEO is a specific technical discipline. A developer who has never run a post-migration crawl diff, never filed a Change of Address in Search Console, and never worked through a redirect chain audit is not the right person to own this work, even if they are a skilled engineer.
The clearest sign that SEO was not integrated into a migration: the site goes live, looks great, and traffic drops 40% over the following six weeks. By that point the development team has moved on to the next project. Undoing the damage is significantly more expensive and slower than preventing it.
The right ownership model is: your web developer builds and launches the new site; an SEO specialist reviews every technically relevant decision from URL structure to canonical implementation, runs the staging audit before go-live, and owns the post-launch monitoring. Those two roles need to be in conversation throughout the project, not handed off sequentially.
At BetaTech, our team spans Bangladesh and the US, which means staging reviews and pre-launch SEO checks run during hours when a purely US-based agency is offline. Feedback given at the end of a US business day is often actioned before the next morning. For time-sensitive migrations where a bad launch window costs real rankings, that time compression matters.
FAQ:
Will my site definitely lose traffic after a migration?
Some short-term fluctuation is normal and expected. Google needs time to recrawl your new URLs and update its index. According to Google’s own site migration documentation, a medium-sized website can take a few weeks for most pages to move in the index. A well-managed migration with complete redirect coverage, clean canonicals, and a submitted sitemap will typically see traffic return to pre-migration levels within 4-12 weeks for a same-domain redesign. Domain changes take significantly longer.
Do 301 redirects pass full SEO value?
Yes. Google’s Search Central documentation confirms that 301 and 308 permanent redirects do not cause a loss in PageRank. The confusion comes from an old finding (since corrected) that suggested redirect chains diluted link equity. A direct 301 from the old URL to the correct new URL transfers full link authority. What does cost you is a broken redirect, a redirect to the wrong page, or a chain of three or more hops.
How long should redirects stay in place?
Google recommends keeping redirects live for at least one year after migration. This gives sufficient time for Googlebot to process the full index transfer, and for backlinks on external sites to be recrawled and resolved to the new URL. From a user experience standpoint, keeping redirects indefinitely is better practice, since external links pointing to your old URLs will continue to resolve correctly.
What is the Change of Address tool in Google Search Console, and do I need it?
The Change of Address tool in Google Search Console is a signal you submit to tell Google you have permanently moved from one domain to another. It accelerates the index transfer process and is required for domain-to-domain migrations. It does not apply to migrations where the domain stays the same (such as a platform replatform or redesign). To use it, both the old and new domains need to be verified in Search Console.
Can I do a site migration in phases, or does it have to go live all at once?
Both approaches are valid, and the right one depends on site size. Google recommends moving large sites in sections, which reduces risk because problems in one section do not bring down the entire migration. For small to mid-sized sites, a simultaneous launch is generally faster to recover from because Google can detect and process the full site move at once rather than encountering a partial state that can confuse its index.
What is the most common mistake in site migrations?
Forgetting to remove the noindex directive from the staging environment before launch. New sites built in staging are almost always set to noindex during development to prevent Google from indexing incomplete pages. If that directive is not removed before go-live — or if the robots.txt still disallows all crawlers — Google cannot index the new site at all. This mistake can go unnoticed for days or weeks and requires emergency remediation. It is the first thing any migration SEO specialist checks.
If you are planning a website migration, a scoped pre-migration audit is the lowest-risk way to understand your actual exposure before any files move. Request a migration scoping conversation and we will walk through your URL inventory, your current organic footprint, and what a properly managed migration would look like for your site.
