
How much should you budget for SEO during a website migration?
Understand the work behind a migration quote, compare equivalent scopes and build a budget that includes testing and implementation.
Written by Rob KnottYour migration SEO budget should come from the work the project requires. A small site with complicated international rules can demand more attention than a much larger site with consistent templates and a simple URL mapping.
This guide explains how to build and compare estimates. The figures in the worked example are deliberately hypothetical: they are not Rob's rates, a quote or a claimed market average. Use the method with the rates and scope supplied for your own project.
Separate the rebuild from the search work
A developer's price for moving content or replacing a platform may not include search discovery, destination decisions, baseline analysis or independent verification. Equally, an SEO consultant's estimate may exclude implementing the recommendations. Clarify both before comparing totals.
Think in workstreams: discovery and planning; specification; implementation; pre-launch testing; launch support; post-launch verification. Some can be delivered by the same supplier, but they should remain visible in the scope.
Avoid double counting. If your agency already owns crawl analysis and redirect testing, an independent consultant might review that evidence rather than repeat the entire exercise. If the proposal only says “SEO-friendly development”, ask which actual deliverables that covers.
Use the migration checklist to identify the stages your budget needs to cover.
The inputs that change the effort
Page count is a starting point, not a pricing formula. The number of distinct behaviours often matters more: templates, URL rules, languages, domains, filters, documents and integrations. A clean export with obvious replacements is easier to map than several incomplete inventories and ambiguous merged pages.
Commercial exposure also affects the level of assurance you need. A business dependent on a few landing pages may require careful journey testing and a clear escalation plan even when the site is small. A fixed launch date or weekend release changes availability requirements; it does not make the underlying work disappear.
Provide an honest description of uncertainty. Unknown content ownership, unavailable staging access and an undecided URL structure create estimation risk. A paid discovery stage can be more useful than a confident fixed price built on guesses.
| Input | Why it affects scope |
|---|---|
| Current and proposed URL structure | Determines mapping and redirect complexity |
| Templates, domains and markets | Defines the behaviours that need testing |
| Content changes and removals | Creates editorial decisions and destination review |
| Platform and rendering changes | Affects access, output and verification requirements |
| Available crawl, analytics and inventories | Changes how much reconstruction is needed |
| Launch date, hours and support window | Sets staffing and incident-response expectations |
| Implementation ownership | Separates advice from development work |
Worked budget: a fictional service-site migration
Imagine a service business keeping one domain and one language while replacing its CMS. Its content is mostly stable, but some URLs change. The developer handles implementation. The consultant provides planning and independent checks, with an agreed number of review rounds.
The following allocation is an illustration of the arithmetic, not a recommended number of days. A real estimate needs the inventory, dependencies and acceptance requirements. The fictional rate is £700 per day solely to show how the calculation works.
| Workstream | Illustrative days | At fictional £700/day |
|---|---|---|
| Discovery and baseline | 1.5 | £1,050 |
| Mapping review and requirements | 2 | £1,400 |
| Staging checks and one retest | 2 | £1,400 |
| Launch verification | 1 | £700 |
| Post-launch review and handover | 1.5 | £1,050 |
| Base consultancy scope | 8 | £5,600 |
| Optional reserve: one extra agreed day | 1 | £700 |
| Budget including that reserve | 9 | £6,300 |
Read the assumptions behind the number
In the example, £6,300 covers eight planned consultancy days plus one explicitly budgeted optional day. It does not mean nine continuous days on site, nor that the calendar project finishes in nine days. Waiting for content, development or approvals can stretch elapsed time.
Development, content rewriting, translation, tool licences and out-of-hours support are excluded unless separately agreed. Taxes and payment terms need to be stated in the actual proposal. The optional reserve is not permission for a supplier to invoice extra work without agreement.
Now change the scenario: two markets are added, the navigation is rewritten and hundreds of resources are merged. The original eight-day scope no longer describes the job. Request a revised estimate explaining which workstreams change. This is more informative than applying an arbitrary percentage uplift.
Compare two proposals on equivalent terms
A cheaper quote may be suitable if your team already owns much of the work. It may also omit precisely the testing you assumed was included. Put the deliverables side by side before deciding.
For each proposal, ask whether the supplier creates the mapping, reviews a mapping supplied by others or only checks a sample. Ask whether post-launch support means responding to defects, analysing search performance or implementing further changes. Each is a legitimate service, but they are different services.
Compare the people doing the work, availability at important stages and how findings are communicated to developers. A large report is not automatically more valuable than concise, evidenced actions with good acceptance tests. Choose the arrangement that closes your actual capability gaps.
- Are baseline, mapping, staging and public launch checks included?
- Who implements recommendations and who pays for that time?
- How many retests are allowed, and what happens if launch moves?
- Which URLs, templates, markets and documents are in scope?
- What evidence and handover files will you receive?
- Which support hours and post-launch review dates are agreed?
Reduce cost by improving readiness
You can often make specialist time more effective by supplying a current inventory, clear owners, staging access, a realistic release plan and decisions about content. Resolve basic disagreements about what the new site should contain before asking someone to verify it.
Preserving stable URLs where appropriate may simplify the migration, but do not retain a poor structure merely to avoid planning. The right choice depends on the business need and the consequences of change.
If funds are constrained, discuss phased delivery openly: requirements first, a representative template review next, then a defined launch check. Document what will remain untested. Quietly removing verification from the estimate does not remove the risk it was meant to address.
What about a recovery budget?
Recovery after a failed launch is a separate scope because the starting evidence and faults are uncertain. An initial diagnostic engagement can establish what changed and what further work is justified. It is sensible to agree a bounded first stage rather than promise a complete recovery at a guessed price.
Do not treat an optimistic estimate of lost revenue as a guaranteed return from hiring someone. A consultant can investigate faults, specify changes and verify implementation. Future search demand and rankings are not fully controllable. A credible proposal states the intended outcomes and the limits of attribution.
The traffic-drop diagnostic framework explains why the investigation should precede a recovery promise.
Ask for a scope, not just a day rate
To request a useful estimate, share the current site, planned platform and URL changes, markets, target launch date and who is building it. Note what evidence is available and where decisions are unresolved.
You can then agree whether you need end-to-end migration support, a second opinion on an agency plan or a few defined technical review points. The right budget buys the missing expertise at the stages where it can influence the outcome.
Key takeaways
- Build the budget around deliverables and ownership, not page count alone.
- Separate consultancy, implementation and post-launch support.
- Compare assumptions and exclusions before comparing totals.
- Treat illustrative figures as arithmetic, not a quote or promise.
Sources and further reading
Continue planning your website change
The right control plan depends on what is changing. Explore the full website change and SEO guide collection, or go straight to another relevant scenario:
- Briefing your web agency: the SEO requirements to agree before a rebuild
- How to test a redirect map before a site migration
- Website migration SEO checklist: before, during and after launch
- CMS migration SEO requirements: what to specify before the build
- Navigation redesign SEO: protect discovery while improving the journey
- Multi-site consolidation SEO: how to decide what moves where
- How to redesign a website without losing SEO

