Site Migrations
From 500-page domain moves to enterprise platform re-platforms — planned, executed, and monitored for 30 to 60 days post-launch. Every migration is managed against a zero-traffic-loss target, with rollback triggers defined before a single URL changes.
What we cover
A migration is not just a redirect map. It is a coordinated sequence of technical decisions — URL structure, crawl budget, internal linking, canonical strategy, and server behaviour — that must all land correctly on the same day. We plan each one as an engineering project, not a checklist.
Every indexed URL crawled, classified, and mapped to its destination. Redirect chains collapsed to single hops. Orphaned pages flagged for consolidation or deletion before launch day.
Staging environment audit covering canonical tags, robots.txt, noindex directives, hreflang, schema, internal links, and Core Web Vitals. We issue a go / no-go before you push to production.
Live crawl triggered at launch, GSC coverage report reviewed within 24 hours, and a daily traffic delta check for the first two weeks. Anomalies flagged and root-caused within one business day.
Traffic, rankings, and index coverage compared against pre-migration baseline. Remaining redirect gaps closed. Final sign-off issued when organic performance is stable.
Defined thresholds — traffic drop %, crawl error spike, index loss — that automatically trigger a rollback decision call. Agreed with your team before launch so there is no ambiguity on the day.
How a migration project runs
Audit and plan
Full crawl of existing site, URL classification, redirect map draft, and a migration risk register. We flag any issues that need resolving before the new platform is built.
Staging review
We audit the staging environment against the plan. Canonical, robots, hreflang, structured data, page speed, and the full redirect map are verified before go-live sign-off.
Launch and monitor
Launch-day crawl, 24-hour GSC check, daily traffic monitoring for two weeks, and a 30-day and 60-day post-migration report. Project closes when organic is stable.
Who this is for
- E-commerce stores moving from Magento or WooCommerce to Shopify — or vice versa
- SaaS companies consolidating subdomains into a single root domain
- Media sites re-platforming to headless CMS with server-side rendering
- Businesses changing domain name due to rebrand or acquisition
- Any site with 500+ indexed pages where a traffic loss of 20% would materially impact revenue
- Sites with fewer than 50 pages and negligible organic traffic
- Teams that want to launch without a staging review period
- Migrations where the dev team cannot implement server-side 301 redirects
Scoped to site size. Fixed price. No monthly retainer.
What teams ask before launch day.
30 minutes on a call. No pitch deck. We'll tell you if we're a fit.
Come with your domain, top three competitors, and your revenue goal for the year. You leave with a diagnosis and a realistic 12-month outlook.