Website migration SEO cost is what you pay to carry search performance across a replatform, redesign or domain change. It is the clearest example in SEO of work whose value is mostly invisible when it succeeds.
A migration done well produces a shallow dip and a recovery. Done badly it produces a decline that takes months to diagnose and longer to reverse, at a cost that usually exceeds the migration support several times over.
What the work involves is set out on SEO migration. This page covers what it costs and why quotes differ.
What drives the cost
- URL count. Mapping scales with the number of indexed URLs, not with page designs.
- How different the structures are. Like-for-like moves map largely by rule; platform changes need more manual work.
- Data availability. Missing analytics history, no old crawl and no Search Console access all add reconstruction time.
- Whether structure changes too. Migrating and restructuring together roughly doubles the analysis.
- Staging quality. A complete staging environment makes validation efficient; a partial one makes it repetitive.
- Timeline. Compressed launches cost more, because parallel work replaces sequential work.
What the phases cost, relatively
- Inventory and mapping is usually the largest share, and the one most often underestimated.
- Staging validation is moderate, and scales with template count rather than URL count.
- Launch monitoring is small but concentrated into a short, intense window.
- Post-launch remediation should be small. Where it is large, the earlier phases were skipped.
The distribution matters when comparing quotes. A quote weighted toward post-launch support is describing a riskier approach than one weighted toward mapping.
Timing changes the price
- Involved during planning: cheapest, because structure is still negotiable and mistakes are prevented.
- Involved during build: moderate, since staging exists and redirects can be tested pre-launch.
- Involved after launch: most expensive. The work becomes recovery, with decayed signals and less certainty.
Comparing quotes
- Ask what the redirect map deliverable actually is, and in what format.
- Ask whether the URL inventory includes Search Console and analytics sources, or only a crawl.
- Ask whether staging validation is included, and how many rounds.
- Ask how long post-launch monitoring runs, since a week is not enough.
- Ask who implements the redirects, and whether that time is included.
Frequently asked questions
Can we skip SEO support if the developers are good?
Capable developers handle the build well. The gap is usually the URL inventory and redirect map, which depend on search and analytics data outside the development process. That is normally the part worth buying.
Is it cheaper to fix problems after launch?
No, and it is the most expensive sequence available. Pre-launch prevention is bounded work; post-launch recovery involves diagnosis under uncertainty, with rankings decaying while you work.
How long should monitoring continue?
Several weeks at minimum, longer for large catalogues, because recrawling is not immediate. A quote that ends support at launch is not covering the period when problems actually surface.
What if we already migrated and lost traffic?
That is recovery rather than migration support, and it is diagnosed differently. The first step is establishing what changed and when, which is often harder retrospectively than it would have been in advance.
Consulting CTA
If you are planning a replatform, redesign or domain change, book an SEO consultation before the URL structure is finalised, when prevention is still cheaper than recovery.