The riskiest thing you will do to your site this year.
Redesigns, replatforms, domain changes and consolidations, planned and verified so the traffic survives the launch. From $2,900. Engage us [six] weeks before go-live.
Nobody notices a migration went wrong until the quarter is already gone.
The failure is never dramatic. A few hundred URLs redirect to the homepage instead of their equivalent. The schema does not come across. Hreflang stops reciprocating. Nothing looks broken to a person, so nobody checks, and eight weeks later somebody asks why organic is down forty percent and the answer is buried in a launch that everybody signed off on.
Mapped, not guessedEvery URL matched one to one, single hops, no chains, with a confidence score on each.
Verified before launchRender-versus-source checks on every template, on staging, before anyone goes live.
Watched after[Eight] weeks of daily monitoring with same-day response on regressions.Six things arrive. All of them are named.
Artifacts, not activities. Each one is a thing you can open, keep and hand to someone.
A pre-migration baseline
Full crawl, [16] months of Search Console data, backlink profile, rank snapshot and a schema inventory, captured before anything changes. This is the only chance to take it.
A URL mapping spreadsheet
Old URL, new URL, redirect type, confidence score. Single hops only, no chains, with the awkward cases handled explicitly: pagination, facets, parameterised search, and pages you are choosing to drop.
A schema and hreflang preservation spec
What structured data exists today, what must survive, and hreflang reciprocity checked URL by URL.
A staging audit
Render-versus-source checks on every template, so content that exists for a person but not for a crawler is caught before launch rather than after.
A launch-day checklist, run by us
Robots, canonicals, sitemaps, the change-of-address, analytics continuity, and [200+] redirect smoke tests executed on the day.
[Eight] weeks of post-launch monitoring
Daily crawl and index monitoring, weekly reporting, and same-day response on any regression.
What happens, and when
The clock starts when we have what we need from you, and the first phase says exactly what that is.
Baseline
Everything measured and captured while the old site still exists. The clock starts when we have crawl access and Search Console.
You get · a baseline that cannot be recreated laterMapping and spec
URL map built and reviewed with your developers, schema and hreflang spec written, edge cases resolved.
You get · a map your developers can implementStaging
Template-level verification on staging, and the launch checklist agreed with whoever is pressing the button.
You get · a go or no-goMonitoring
Checklist run on the day, then daily monitoring and weekly reporting.
You get · confirmation it worked, or a fixWhat it is, and what it is not
What actually arrives
The URL mapping spreadsheet is the main artifact and it is the one your developers will live in. Alongside it: the baseline data, the preservation spec, the launch checklist as a runnable list, and weekly monitoring reports for [eight] weeks after go-live.
Pricing
Published. Nothing here is quoted after the fact.
Questions
If your question is not here, one of us will answer it directly.
Still have questions? →A free migration review is a sales document for a rebuild. A paid engagement can tell you your plan is sound and step away after the checklist, which a free one structurally cannot. And the baseline it captures cannot be recreated once the old site is gone.
NextA launch on
the calendar?
Tell us the platform, the URL count and the go-live date. We will reply with the price, the timeline, and the one thing to protect first, which costs nothing to know.