---
title: "Website Migration Costs: SEO for a New Website From €10,000, and Where the Work Goes | Baba SEO"
description: "SEO for a new website (a website migration) starts at €10,000 over 3–4 months. About three quarters of the work happens before launch: the share per phase, what drives the price, and what a failed launch costs."
canonical_url: https://www.baba-seo.com/website-migration-cost
last_updated: 2026-11-17
---

new website

# Website migration cost: the question most companies ask is the wrong one.

Across 892 domain moves, the new domain took 523 days on average to get its organic traffic back. Most budgets cover what you spend. Almost none account for what you lose.

**B2B companies only** – I take on new websites for SaaS, tech, and B2B services businesses.

[Book a free call](https://cal.com/baba-seo/website-migration)

## **The decision that determines everything comes before the new website is built.**

Not the platform choice. Not the redirect strategy (a redirect sends visitors and Google from an old page address to the new one). Not which agency you hire.

The decision that determines whether your new website protects revenue is whether anyone has sat down, before a single page is moved, and answered two questions: which pages are actually driving pipeline right now, and which keywords cannot afford to lose their rankings?

Most website migrations, SEO's word for a new website (a new platform, design, structure or domain), skip this entirely. Not because teams are careless. Because it requires commercial judgment, not technical execution, and most of the people building new websites are technical. They're excellent at moving things. They're not paid to decide what matters.

So they treat everything equally. Every URL gets a redirect. Every page gets checked. Every group of keywords gets documented. It looks thorough. It isn't. Because thoroughness without prioritization means the three URLs quietly generating 60% of your MQLs get the same attention as blog posts from 2021 that nobody reads.

That's where revenue gets lost. Not in the redirect map. Not in the canonical tags, the setting that tells Google which version of a page counts. In the decision that was never made about what to protect in the first place.

## WHAT'S ACTUALLY AT STAKE

**IF IT GOES WRONG:&#x20;**&#x35;23 days on average to recover, across 892 domain moves

HIDDEN COST: Commercial pages drive most conversions, and get the least protection

**THE FIX:&#x20;**&#x31;5–25 priority URLs identified before the build starts

## **What the triage looks like in practice.**

Every new website I protect starts with the same document: the New Website Risk Assessment. Not a technical audit. Not a redirect map. A commercial assessment that answers, before any build work begins, what this site's organic presence is actually worth, and which parts of it cannot be disrupted.

It covers 3 things, in this order.

### **First: define what success means in commercial terms.**

Most new website briefs define success as 'no traffic drop.' That's the wrong metric, because not all traffic is equal, and a 10% drop in total sessions that doesn't touch your pricing or solutions pages is a completely different outcome from a 10% drop concentrated there.

Before any technical work starts, I define the KPIs that will determine whether the launch succeeded: organic sessions to priority pages, conversions from organic (absolute, not just rate), rankings of the focus keywords, and how many pages show up in Google as a technical check. These are agreed with the client before launch, so there's a shared definition of what we're protecting, and what a post-launch drop actually means.

This matters because it changes how the team responds to data. A short-term dip in total organic traffic post-launch is normal and expected. A drop in conversions from organic to the pricing page is not. Without pre-agreed KPIs, teams either panic at the wrong signals or miss the right ones.

### **Second: name the pages that cannot fail.**

This is the output most new website projects skip entirely, and it's the one that prevents the most damage.

I build an explicit priority page list before the launch planning starts. Not 'all pages,' not 'high-traffic pages.' A short, named list of URLs that are tied to pipeline: commercial pages, pricing, solution pages, the specific blog posts that are generating trial signups or demo requests from organic traffic.

In practice, this list is shorter than most teams expect. On a typical B2B SaaS site with 200+ pages, the priority list is usually 5 to 15 URLs. That's the set that drives the migration strategy. Every redirect decision, every review of internal links (the links between your own pages), every post-launch monitoring alert is built around those pages first.

The rest of the site gets moved correctly, but it doesn't drive the decisions. That distinction is what makes the engagement commercially focused rather than technically thorough-but-directionless.

### **Third: build the keyword set around the words buyers use, not coverage.**

Alongside the priority page list, I define a monitored keyword set, typically 15 to 50 keywords depending on the site, all tied to what a buyer is looking for or to strategic visibility goals. These are the terms I track through and after the launch.

The set is deliberately split: keywords already ranking that need to be protected, and keywords with no current visibility that I track after launch as a growth signal. The migration strategy for each is different. Protecting a position-8 ranking on a keyword where the searcher wants pricing is an active task: it requires verifying that the page, its internal links, and its technical settings survive the transition intact. Tracking a position-100 keyword is a monitoring task. Conflating the two wastes effort on the wrong things.

What this produces is a monitoring dashboard that's commercially meaningful from Day 1 after launch, not a ranking report that shows 200 keywords moving up and down with no indication of which ones matter.

> *The assessment about a day. It's the most commercially valuable work in the entire engagement, because once it's done, every technical decision that follows has a clear answer to the question: does this protect what matters?***\
> Baba, on every new website I protect**

## **What happens when nobody does this first.**

Here's a pattern that shows up consistently across new website projects where the commercial assessment was skipped.

The site has significant organic traffic — often 6 figures of sessions per year. But when you look at where that traffic actually lands, 60–70% is hitting the homepage or regional equivalents. The commercial pages — pricing, solutions, specific use case pages — are getting a fraction of a percent each. They look like they barely matter in the traffic report.

But when you cross-reference against conversion data, those same commercial pages are driving the majority of organic signups and demo requests; not surprising. The homepage traffic bounces. The pricing page traffic converts. The traffic report and the commercial reality are pointing in completely opposite directions.

A new website that treats all pages equally, based on traffic share, will spend the most effort protecting the homepage and the blog. It will treat the pricing page as one of 200 URLs to redirect correctly. Nobody flags it as a priority. Nobody verifies that its internal linking survived. Nobody checks whether the platform's canonical handling affected its ranking signals.

4 weeks post-launch, total traffic looks fine. Conversions from organic are down 40%. The diagnostic work takes 6 weeks. The recovery takes 6 months.

This is not a hypothetical. It's the failure mode that a pre-launch commercial assessment is specifically designed to prevent, by making the gap between traffic share and commercial value visible before any build decisions are made, not after.

> *Your dev agency will build your new site correctly. They will not tell you which pages you cannot afford to deprioritise, because they don't have access to your conversion data and they don't know your close rates. That gap is where revenue disappears.*

## **What the work returned on three new websites, and what still broke**

By [Baba Hausmann](https://www.baba-seo.com/about) · Last updated November 2026

A budget line is only cheap if it protects your leads. Here is what this work did on three launches I ran, including the parts that went wrong.

### **Bedrijfsfitness Nederland: leads went up during launch week**

A Dutch corporate fitness provider moved to HubSpot in May 2025, and its weekly lead flow could not stop. I measured the new website on leads and checked it on a fixed schedule. Weekly leads rose 12% in launch week and finished the week after launch up 21%. Visits to missing pages still jumped from 26 to 130 in week one. The checks caught it, and a bulk redirect import closed it within days. I also deleted content that no longer fit the business, so "wat is bedrijfsfitness" slipped from position 1 to 3. Explainer rankings that never produced a lead were not worth defending. The week-by-week numbers are in [how Bedrijfsfitness Nederland grew leads through its launch week](https://www.baba-seo.com/client-stories/bfnl-migration-leads-up-launch-week).

### **Backbase: 19 pages decided before 1,300 moved**

Backbase moved more than 1,300 pages in three languages from Craft CMS to Webflow in November 2025, and 10 of its 19 most important pages changed address. I agreed those 19 pages and the success measure before launch. All 19 showed up in Google after launch, and organic sessions to them doubled within a month. I wrote up [how Backbase doubled organic sessions to its 19 priority pages](https://www.baba-seo.com/client-stories/backbase-enterprise-webflow-migration).

### **Mollie: 290 tickets, and most of them could wait**

I led SEO in-house when mollie.com, 2,011 pages, moved to a new platform in October 2022, so no fee applies to this one. I went through 290 SEO tickets daily and sorted them by what would block the launch. The month after launch, organic sessions were up 9%, sessions on the pages closest to a purchase up 73%, and conversions from those pages up 21%. I had no access to server logs, the keyword research planned for the product pages never happened, and content was frozen for six weeks. What went wrong is in [the Mollie relaunch of 2,011 pages without a dip](https://www.baba-seo.com/client-stories/mollie-no-dip-relaunch). Deciding which tickets could not wait is the triage you are paying for.

### **What I got wrong**

At Backbase I could prove the traffic doubled, but not what it did to pipeline, because lead reporting through Salesforce was not connected for the launch. I accepted sessions as the measure and put that limit in writing. I would not accept it again without a fight. On every new website since, connecting lead reporting is a condition before launch, because you cannot reconstruct it afterwards.

## **What the SEO side of a new website costs, and what drives the difference.**

Engagements start at €10,000, and the price grows with scope: larger or multi-language sites go beyond that. Here's what you're actually paying for, and what the alternative looks like. You can also see [all my prices, sorted by budget](https://www.baba-seo.com/pricing).

| Without triage                         | With Baba's triage                              |                                                      |
| -------------------------------------- | ----------------------------------------------- | ---------------------------------------------------- |
| Pre-launch revenue triage              | Not done                                        | Always done first                                    |
| Priority pages identified before build | No — all pages treated equally                  | Yes — short list, non-negotiable                     |
| Commercial keyword mapping             | Traffic-based, not based on what searchers want | Matched to the words buyers use, and to pipeline     |
| Platform-specific risk assessment      | Generic checklist                               | Platform-specific, from experience                   |
| Redirect mapping approach              | All URLs, equal weight                          | Priority URLs first, tested individually             |
| Post-launch monitoring (60 days)       | Rarely included                                 | Standard — risk window stays open                    |
| Traffic loss risk (priority pages)     | Unknown until after launch                      | Forecast before launch, priority pages checked daily |
| Specialist fee                         | Varied range                                    | From €10,000, rising with scope                      |
| Revenue at risk (unmitigated)          | €50K–€400K+/year                                | Mitigated before launch                              |

*Engagements start at €10,000, and the price grows with site complexity, URL count, and platform. The intro call (30 minutes, no cost) is where I assess the specifics and give you a fixed price.*

## **Where the work goes: the share of time per phase**

People ask how many hours SEO for a new website takes. The total depends on the site, so here is how the work splits instead, from the method I use on every launch. The total grows with the number of pages and languages. The split stays about the same.

| Phase                               | What happens                                                                                                                                            | Share of the work |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| 1. Baseline                         | From about a month before launch: daily scans of the site, plus Search Console, analytics and backlink data saved, so there is a before to compare with | **10%**           |
| 2. Content audit and priority pages | Keep, cut or review every page, name the pages that cannot fail, and show what each decision costs in leads before anyone approves it                   | **20%**           |
| 3. Redirect map                     | The new URL structure, every old page matched to a new one, checked for chains, loops and broken targets, exported for the developers                   | **25%**           |
| 4. Before launch                    | SEO guidelines for the build, each template checked as it is finished, a full audit of the test site, and a go or no-go                                 | **20%**           |
| 5. Launch day                       | A scan of the live site the same day: redirects, technical settings, no new errors                                                                      | **5%**            |
| 6. After launch                     | Daily scans for the first month, checks at week one and month one, and a final report on traffic, rankings, leads and revenue                           | **20%**           |

**About three quarters of the work happens before launch day.** If a quote for SEO on your new website covers launch week and the month after, it covers about a quarter of the job, and the part that decides whether you lose leads has already passed.

## **Not ready to commit? Start with the New Website Risk Assessment.**

If you suspect your new website puts revenue at risk but you're not ready to buy a full engagement, there is a smaller first step: the [**New Website Risk Assessment, €2,500**](https://www.baba-seo.com/migration-risk-assessment), delivered in 5 business days. Here is [an example New Website Risk Assessment](https://www.baba-seo.com/migration-risk-assessment-example).

You get one document, written so you can forward it to your CEO without rewriting a word:

- The revenue at risk, quantified: which pages produce your leads and what share of pipeline runs through them
- Your top risks, ranked by likelihood and impact, each with the specific prevention step
- A verdict: go, fix these first, or restructure the plan
- The list of non-negotiables to hand your developer or agency

If we work together on the new website within 60 days, **the €2,500 is credited in full** against the engagement. You are not paying extra for starting careful.

Why does this work? Because this is how my new website launches run: priority pages at **2 to 4x their organic sessions within a month** of launch, and **leads holding or growing through launch week** where they are tracked. The basis: the three website migrations I delivered in 2025. All three are written up: [weekly leads up 21% at Bedrijfsfitness Nederland](https://www.baba-seo.com/client-stories/bfnl-migration-leads-up-launch-week), [priority-page sessions doubled at Backbase](https://www.baba-seo.com/client-stories/backbase-enterprise-webflow-migration) and [organic trial signups up 5x at Rentman](https://www.baba-seo.com/client-stories/rentman-webflow-migration-5x-trials). That outcome starts with exactly this assessment: it is the first phase of every engagement, offered standalone. Read more about [what dip is normal after a new website, and how long recovery takes](https://www.baba-seo.com/website-migration-risks), or [how the full engagement runs](https://www.baba-seo.com/website-migration).

## **Who this engagement is built for.**

I work with B2B SaaS companies at Seed to Series C that are planning a new website or a move to a new platform, and whose organic traffic brings leads they cannot afford to lose. Specifically:

- **You're moving to Webflow, HubSpot, or a headless CMS&#xA0;**
- **You're [merging two websites into one](https://www.baba-seo.com/website-merger-seo) after an acquisition or rebrand&#xA0;**
- **Organic is already generating MQLs — not just traffic — and you know roughly what those leads are worth&#xA0;**
- **Your dev agency is handling the build, but nobody owns commercial SEO continuity through the transition&#xA0;**
- **You've raised a round, you have budget for the move, and losing 3 months of pipeline to a recoverable SEO error is not acceptable&#xA0;**

I don't work with companies that want the cheapest path through a new website. I work with companies that **have done the maths on what a traffic drop costs them**, and decided that paying for it to not happen is the obvious move.

## Common Questions.

### How much does a website migration cost for a B2B SaaS company?

New Website SEO starts at €10,000 for a 3–4 month project, and the price grows with scope: larger or multi-language sites go beyond that. That covers pre-launch triage, redirect mapping, platform-specific SEO review, launch support, and 60 days of post-launch monitoring. What that fee buys is not technical execution: your dev team handles the build. It's the commercial judgment that comes before the build: identifying which pages and keywords cannot be disrupted, and making sure every technical decision is made against that list.

### Is there a smaller way to start than the full engagement?

Yes: the New Website Risk Assessment. €2,500, delivered in 5 business days. You get the revenue at risk quantified in money terms, the risks ranked with a prevention step for each, a clear go or fix-first verdict, and the list of non-negotiables to hand your developer. If we work together on the new website within 60 days, the €2,500 is credited in full against the engagement. It exists for one buyer: the team that suspects something is at risk and wants proof before committing to the full project.

### What's the single biggest mistake companies make with a new website?

Not doing the commercial triage before the project starts. Most teams treat all pages equally, which means the 3 pages generating 60% of their organic pipeline get the same level of protection as blog posts with no commercial value. When those priority pages get disrupted, the traffic drop shows up 4–8 weeks post-launch. By then, the old site is gone and the recovery work is expensive. The triage costs 1 to 2 days. The recovery costs months.

### My dev agency says the new website is straightforward. Should I still bring in an SEO specialist?

Yes, and your dev agency is probably right that the technical build is straightforward. That's not where the risk is. The risk is in the decisions made before the build starts: which URLs are revenue-generating and cannot change, which keywords need to maintain their ranking signals through the transition, and which platform-specific SEO limitations need to be accounted for in the architecture. Dev agencies are not paid to know your close rates or your Google Search Console data (Google’s free report on your search traffic). That gap is where your rankings, and the leads they bring, get lost.

### How long does New Website SEO take?

The triage and planning phase runs in weeks 1–2, in parallel with your dev agency's discovery work. The technical review and checks run alongside the build in weeks 3–6. Launch support and monitoring covers the 60 days post-launch. The engagement ends when the traffic is stable, not when the site goes live. Going live is roughly the halfway point in terms of risk.

### What platforms do you work with?

Primarily Webflow, HubSpot CMS, and headless setups: Next.js, Astro, Contentful, Sanity. Each platform carries a different risk profile. Moves to Webflow are usually the most contained; I wrote up [the six SEO risks of moving to Webflow](https://www.baba-seo.com/webflow-migration-seo). HubSpot has specific limitations around canonical handling and URL flexibility that need explicit workarounds.

### Can I do the commercial triage myself before hiring a specialist?

You can start it. Pull your Google Search Console data and filter for pages that get clicks from search, not just pages that show up. Cross-reference against your CRM to see which landing pages are generating form fills or demo requests from organic traffic. That short list is your priority set. Where it gets harder without experience is matching each keyword to what the searcher wants, and the platform-specific risk assessment: those require knowing what to look for on your specific platform, which comes from having done this move before on that platform.

![corner right](https://www.baba-seo.com/assets/talk-top-image.svg)![corner left](https://www.baba-seo.com/assets/talk-btm-image.svg)

## WHAT THIS MEANS FOR YOUR BUDGET

**The specialist fee** starts at €10,000 and grows with the size of the site. The revenue at risk is multiples of that.

**The triage** takes 1–2 days. Recovery from skipping it takes 6–12 months.

**The calculator above** shows your specific number — not a generic estimate.

## **WANT TO KNOW YOUR NUMBER?**

Use the calculator to see what your new website puts at risk. Then book a 30-minute call: I'll tell you where the risk is concentrated and what to protect first.

**B2B companies only** – I take on new websites for SaaS, tech, and B2B services businesses.

[book a free call](https://cal.com/baba-seo/website-migration)

[see how i work](https://www.baba-seo.com/website-migration)

Read next.

[April 3, 2026](https://www.baba-seo.com/website-migration)

### [SEO for a New B2B Website](https://www.baba-seo.com/website-migration)

[How the engagement runs from triage to handover, and what you get at each stage.](https://www.baba-seo.com/website-migration)

[April 3, 2026](https://www.baba-seo.com/seo-migration-checklist)

### [The SEO Checklist for a New B2B Website](https://www.baba-seo.com/seo-migration-checklist)

[The ungated, priority-ordered checklist I use on every new website, as an interactive tool.](https://www.baba-seo.com/seo-migration-checklist)

[April 3, 2026](https://www.baba-seo.com/website-migration-risks)

### [What Dip Is Normal After a New Website](https://www.baba-seo.com/website-migration-risks)

[What dip is normal, what is not, and how long recovery takes when it goes wrong.](https://www.baba-seo.com/website-migration-risks)

[Baba SEO](https://www.baba-seo.com/)[SEO for a New Website](https://www.baba-seo.com/website-migration)
