website migration seo consultant
Working with an SEO migration consultant
One person, accountable for the specification and the technical gates, working directly with your engineers. No account layer, no handover between the person who scoped it and the person doing it.
- Definition
- A website migration SEO consultant — A website migration SEO consultant is an individual specialist retained to protect organic search performance across a site move. They produce the specification — redirect map, parity requirements, launch runbook — and verify the result, while the client's engineering team implements. The engagement trades resourcing depth for direct access and single-point accountability.
The case for one person
Migration work is unusually judgment-dependent. The hard parts are not laborious — they are decisions about which URLs matter, what to do when two taxonomies do not reconcile, and whether an incomplete redirect map justifies moving a launch date.
Those decisions get worse when they pass through layers. A website migration SEO consultant removes the layers: the person who scoped the engagement is the person doing the analysis, holding the gate and on the call at cutover. When your engineer asks why a particular URL maps where it does, the answer comes from whoever made the decision, in the same thread, that day.
The trade is real and worth stating plainly. One person is one person. There is a capacity ceiling, and there is a single point of failure. The mitigations are written availability commitments and a runbook someone else can execute — not a claim that the risk does not exist.
What your team does, and what we do
The division is fixed and it works because it puts each task with whoever has the context for it.
Your engineers implement. They know the codebase, the deploy pipeline and the edge configuration. Handing that to an outsider mid-migration adds a handover cost precisely when you cannot afford one.
Your marketing or content lead owns the decisions that require business knowledge: which discontinued product pages deserve a redirect to a category and which should go to a genuine replacement, which of two overlapping pages wins a topic after a consolidation.
We own the specification, the verification and the gates. That means producing artifacts your team acts on, testing the result independently, and being the person who says the redirect map is not ready when it is not ready.
The part of this engagement people underestimate
Not the redirect map. The content decisions.
Every migration surfaces a set of URLs with no clean equivalent on the new site — discontinued products, retired campaign pages, blog posts from a strategy nobody remembers. Each one needs a decision: redirect to the closest relevant page, redirect to a category, or return 410 Gone deliberately.
There is no technical answer to those questions. They need someone who knows the business. The consultant’s job is to surface them early, with the traffic and link data attached so the decision is informed, and to put a deadline on each one so they do not all get resolved by a catch-all rule the week before launch.
Sites that come through migrations well are usually the ones where those decisions were made in week four rather than week nine.
How this compares to hiring an agency
Both work. The agency comparison page sets out the trade-offs in a table, including the six questions worth asking any provider — us included.
The short version: if you need implementation capacity or parallel workstreams, hire an agency. If you have engineers who can ship and what is missing is specification, QA and accountability, a consultant is the more direct route and usually the cheaper one.
Starting
Send the launch date and what is changing. The scoping call is thirty minutes and its only purpose is to establish whether this engagement helps you — which sometimes it does not, in which case that is what you will hear.
If you would rather assess your own risk first, the pre-launch audit is fixed-scope, and the full checklist is published so you can work through it without hiring anyone at all.
| Stage | Working mode | Your time | What lands |
|---|---|---|---|
| Weeks 1–2 | Independent analysis, one working session | 2–3 hours total | Benchmark, crawl export, priority tiers, risk register |
| Weeks 3–6 | Collaborative — mapping decisions need your content knowledge | 2–4 hours a week | Redirect map, structure findings, content decisions with deadlines |
| Weeks 7–9 | Iterative QA against staging as builds land | Engineering time, not marketing time | Parity diff, exception list, go/no-go recommendation |
| Launch window | Live availability across the cutover | Whatever the cutover needs | Verified redirects, production directive checks, runbook sign-off |
| Days 30/60/90 | Independent analysis, one readout each | 1 hour each | Cohort performance against benchmark, ranked remaining issues |
When a consultant is the right fit
- You have engineers who can implement a specification without hand-holding.
- You want one named person accountable rather than a rotating team.
- Decisions need to be made quickly, in one conversation, without escalation.
- The scope is judgment-heavy rather than volume-heavy.
When it is not
- You need someone to write and deploy the redirect rules themselves.
- Several workstreams have to run in parallel on a compressed timeline.
- Your procurement process requires a vendor with contractual cover for absence.
- You want a team that can absorb ongoing content and link work at the same time.
How the engagement starts
The first two weeks are deliberately front-loaded, because everything after them depends on knowing what you currently have.
- 01
Scoping call
Launch date, what is changing, who owns what. Thirty minutes, no deck. The output is a yes or no on whether this engagement helps, and a rough shape if it does.
- 02
Access and benchmark
Read-only Search Console and analytics, plus permission to crawl. The 12-month URL-level export gets frozen as the baseline before anything changes.
Output Frozen benchmark
- 03
Current-state crawl
Complete crawl of the existing site with per-URL signals recorded, so the parity diff later has something real to compare against.
Output Production crawl export
- 04
Working session on structure
The one meeting that matters early: the proposed new structure walked through against the current inventory, with mismatches turned into owned decisions.
Output Structure findings and decision list
- 05
Risk register and honest timeline read
What can realistically be done before the launch date, and what cannot. If the date does not allow the work, that gets said in week one rather than week eight.
Output Risk register
Deliverables
What this engagement hands over
-
Pre-launch
Redirect map
One row per old URL with destination, status code, priority tier and reasoning where the mapping is not one-to-one. Yours to keep and reuse.
-
Discovery
Structure findings
Where the proposed URL structure creates avoidable risk, ranked by traffic exposed, with a clear note on which items are worth reopening a locked decision for.
-
Staging QA
Parity diff and exception list
Staging against production, field by field, with each unexplained difference either fixed or formally accepted before the go/no-go call.
-
Launch day
Launch runbook
Cutover sequence with owners and timings, including the rollback trigger and who is authorized to pull it.
-
Recovery
30/60/90 readouts
Cohort performance against the frozen benchmark, with remaining issues ranked by traffic at risk rather than by severity label.
Questions people ask before starting
What does an SEO migration consultant actually do?
Produces the specification and verifies the result. That means benchmarking current performance, mapping redirects, reviewing the new structure, diffing staging against production, holding the launch gate and tracking recovery. Implementation stays with your engineering team throughout.
Is a consultant enough for a large migration?
For specification and QA, usually yes — that work is judgment-heavy rather than volume-heavy. Where a consultant stops being enough is when you need parallel implementation capacity as well. At that point an agency is the right structure and we will say so.
What happens if you are unavailable during our launch?
Launch-window availability is agreed in writing before the engagement starts, and the runbook is written so someone else can execute it. That is the honest mitigation for a single point of failure: documentation that does not depend on the person who wrote it.
Do you offer an ongoing retainer?
For migrations with long build cycles, yes. An advisory retainer covers structure reviews, decision support and QA at each milestone rather than a fixed monthly deliverable. Outside a migration, ongoing SEO growth work is not what this practice does.
Can you work with our existing agency?
Yes, with a clean split. They keep content, links and ongoing strategy; migration mechanics sit here until 90 days post-launch. What does not work is two parties giving technical direction to the same engineers in the same sprint.
What if we already migrated and traffic dropped?
That is a recovery engagement and it starts with diagnosis, not a plan. The first step is separating redirect failures from indexation changes from genuine content loss, because those three look similar in a traffic graph and need completely different fixes.
Start with the launch date
Tell us what is changing and when. We will tell you what is realistic in the time available before anyone discusses scope.
- Reply
- Typically within one business day.
- Hours
- Monday to Friday, 9am–6pm US Eastern.
- First call
- Scoping, not a pitch. No deck.