
How Many Hours Should I Estimate for Site Migration SEO
The SEO hours a site migration needs depend on five variables: the number of URLs, the templates that change, languages or regions, platforms and integrations, and how much content changes. Estimate each task separately with a worksheet, then add the post-launch monitoring most estimates forget.
Sahar
Content Writer
How many hours should I estimate for site migration SEO? It is a question SEO leads, agencies and marketing managers ask whenever a redesign, replatform or domain change is on the table, and the honest answer is that it depends. Not vaguely: it depends on five things you can count. This guide gives you those variables, a task-by-task worksheet, a worked example with clearly made-up numbers, and the timeline the hours fit into.
Need this done right?
Hoop builds the strategy, design and development behind sites like this one, talk to us about yours.
The Short Answer: It Depends on Five Variables
The SEO hours a migration needs depend on five variables:
- URL count: how many URLs have traffic, links or rankings, and need a decision.
- Templates: how many page types change and need testing.
- Languages and regions: each one multiplies URLs, redirects and checks.
- Platforms and integrations: how different the new system is, and how much connects to it.
- Content change: how much content is rewritten, merged or removed.
Fixed numbers you find online (“a migration takes X hours”) mislead because they hide these variables. A site with 50 URLs and one template and a store with tens of thousands of product URLs in three languages are different projects. Count your variables first, then estimate.
What Drives SEO Migration Hours
Site size and URL patterns
The URL inventory and redirect map scale with the number of URLs, but not linearly. Thousands of URLs that follow predictable patterns (products, categories, blog posts) can often be mapped with rules, while a few hundred one-off pages may each need a manual decision. Count both: patterned URLs and unique ones.
Templates that change
Every template that changes needs checking on staging: titles, headings, content, canonicals, structured data, internal links and speed. Ten templates take far longer to test than two, even if the URL count is the same.
Languages and hreflang
Each language or regional version adds its own URLs, redirects and checks, plus hreflang annotations that must be correct on both old and new sites. Multilingual migrations are where small mistakes multiply.
Platform and integrations
Moving between very different systems, such as a custom build to a hosted ecommerce platform or a traditional CMS to a headless setup, means new URL rules, new ways of setting metadata and new rendering behaviour to test. Integrations such as search, filters, reviews and feeds add checks.
Content that is rewritten or removed
Keeping content as it is takes little SEO time. Rewriting, merging or removing content means comparing old and new pages, deciding what must be kept for rankings, and mapping removed pages to the right destinations.
A Task-by-Task Website Migration Estimate Worksheet
Use this website migration estimate worksheet to build your own number. For each task, record the driver, your count, the hours per unit based on your team's experience, and the total. The tasks follow the phases in our website migration checklist.
| Task | Driver | Your count | Hours per unit | Total |
|---|---|---|---|---|
| Benchmark (traffic, rankings, Search Console, links) | Sections or page groups to report on | |||
| URL inventory (crawl, sitemap, analytics, backlinks combined) | URLs with value | |||
| Redirect map: pattern rules | URL patterns | |||
| Redirect map: one-off decisions | Unique URLs | |||
| Content comparison for top pages | Pages by organic traffic | |||
| Staging crawl and fixes | Templates | |||
| Hreflang and regional checks | Languages or regions | |||
| Tracking checks | Conversion types | |||
| Launch-day checks | Top URLs to spot-check | |||
| 90-day monitoring and fixes | Weeks of monitoring | |||
| Reporting to stakeholders | Reports | |||
| Contingency | Share of the total you add for unknowns |
The hours-per-unit column is deliberately blank: fill it in from your own past projects, or ask your team how long each task took last time. If the move is a particular type, such as a platform change or HTTPS switch, check the extra tasks in our site migration checklist and add rows for them.
A Worked Example
This is a fictional example to show the arithmetic, not a benchmark. The inputs are round numbers chosen for illustration; your hours per unit will be different.
Imagine a mid-size services company moving to a new CMS on the same domain. It has 400 URLs with value (300 blog posts following one pattern and 100 unique pages), 8 templates, one language, 3 conversion types, and a plan to merge 40 thin blog posts.
| Task | Example count | Example hours per unit | Example total |
|---|---|---|---|
| Benchmark | 5 page groups | 1 | 5 |
| URL inventory | 1 combined list | 6 | 6 |
| Redirect rules for blog pattern | 1 pattern | 2 | 2 |
| One-off redirect decisions | 100 pages | 0.1 | 10 |
| Merged posts mapped | 40 posts | 0.25 | 10 |
| Staging crawl and fixes | 8 templates | 2 | 16 |
| Tracking checks | 3 conversions | 1 | 3 |
| Launch-day checks | 1 launch | 6 | 6 |
| Monitoring and fixes | 12 weeks | 2 | 24 |
| Reporting | 4 reports | 1 | 4 |
| Contingency | example 20% | - | about 17 |
| Total | about 103 |
The point is the method: each line is small and checkable, and the total is something you can defend. Notice that post-launch monitoring is one of the largest lines; it is also the one most often left out.
Replace the example figures with your own as soon as you have them; even rough numbers from one past project beat any figure borrowed from someone else's site.
Who Does Each Task
SEO hours are not the whole migration. Split the estimate by role, because each role is usually budgeted separately:
- SEO: benchmark, inventory, redirect map, staging crawl, launch checks, monitoring, reporting.
- Developer: implementing redirects, fixing template issues found in testing, deploying, server configuration.
- Content owner: deciding what to keep, merge or rewrite, and doing the rewriting.
- Analyst: tracking setup and checks, dashboards, before-and-after comparisons.
Many SEO findings turn into developer hours, so agree with the development team how many fix hours to reserve for launch week and the weeks after. Our migration website checklist covers the content, data and tracking work beyond SEO.
How Long Does a Website Migration Take? The Timeline
How long does a website migration take on the calendar? Always longer than the hours suggest, because SEO work waits on other work. A typical website migration timeline spreads the SEO hours across four stages:
- Plan: benchmark, inventory and redirect map, while the new site is being designed and built.
- Build and test: staging crawls and fixes, in rounds as templates are finished.
- Launch: an intense day or two of checks.
- After launch: monitoring and fixes for around three months while search engines process the move.
So how long does a site migration take end to end? For most sites, the SEO involvement spans the whole build plus about three months after launch, even though the hours themselves are concentrated before and just after launch. Google's documentation on site moves notes that a medium-sized site can take a few weeks for most pages to move in its index, and larger sites longer, which is why the monitoring tail exists. Our launch-day and first-30-days checklist covers that period in detail.
One practical tip: build the estimate as a range, with a low and a high figure for each task, and agree with stakeholders which assumptions move a task from low to high. When the project changes, you can show exactly which assumption changed and what it does to the total.
What Pushes the Estimate Up
- Late scope changes: new sections, changed URLs or a new navigation after the redirect map is done.
- No staging site, or one that does not match production, so testing happens after launch.
- Combined moves: a redesign, platform change and domain change at the same time.
- Missing analytics history, so the benchmark and inventory have to be rebuilt from other sources.
- Old redirect chains from previous migrations that have to be untangled.
- Several approvers who each need to review the same decisions.
The business side of these drivers, including what they do to cost, is covered in our guide to what a website migration is.
Reducing the hours without cutting corners
- Keep URLs the same wherever you can; unchanged URLs need no mapping.
- Use pattern rules for large groups of URLs instead of mapping one by one.
- Freeze scope before the redirect map is built.
- Provide a staging site that matches production, so testing happens once.
- Separate big changes: move the domain, then redesign, rather than both at once.
What should not be cut is post-launch monitoring; it is cheap compared with the cost of a problem found months late.
How to Brief an Agency for an Accurate Quote
To get an accurate quote rather than a guess, send:
- The approximate number of URLs, and a sitemap or crawl if you have one.
- The list of templates or page types.
- Current and new platforms, and any domain or URL structure changes.
- Languages and regions.
- Integrations that affect pages, such as search, filters, reviews and feeds.
- The planned launch date and any fixed deadlines.
- Read access to analytics and Search Console.
We price migration work as fixed milestones rather than open-ended hours. A free SEO audit gives us the counts in this guide; the quote then breaks the work into benchmark, mapping, QA, launch and monitoring milestones, each with an agreed price.
Want a fixed quote instead of an estimate? Get a free SEO audit. Our SEO migration team will size your move and show you where the risks are.
“There is no standard number of hours. There is a standard way to work it out.”
Key takeaways
- 01Fixed hour counts quoted online mislead, because sites differ enormously in size and complexity
- 02Break the work into tasks: benchmark, inventory, redirect map, staging QA, launch, monitoring and reporting
- 03Calendar time is longer than hours, because work waits on builds, reviews and Google recrawling
- 04Late scope changes and combined moves, such as a redesign plus a domain change, push estimates up most
Written by
Sahar
Content Writer
Frequently Asked
Questions
Everything you need to know before booking a strategy call. Can't find your answer? Contact us directly.
Ask hoop
Usually replies in minutes
Is there a standard number of hours for migration SEO?
No. A ten-page brochure site with unchanged URLs and a large multi-language store moving platform are different projects. Use the five variables and the worksheet in this guide to build an estimate from your own counts instead of borrowing someone else's number.
PEOPLE ALSO ASK
Swipe for 3 more questions →
Can't find your answer? Contact us directly.


