Website Migration SEO: When to Hire a Consultant

Website migration SEO is the work that protects organic visibility when a business changes platform, structure, domain, templates, tracking, or key URLs. Hire before design sign-off, not after launch, because the expensive mistakes usually happen when search requirements are added too late.

Josh Willett Consultancy Ltd handles this UK-wide for businesses that need senior technical input without a bloated agency team. I bring 8+ years of search experience, a former front-end development background in HTML, CSS and JavaScript, and enough migration scar tissue to know that a good launch plan is built before anyone presses publish.

If you're comparing support options, the useful question isn't whether someone offers seo website migration services. The useful question is whether they can influence the migration process early enough to protect the pages, links, rankings and conversion data that already make money.

Why Should Migration Work Start Before Design Sign-Off?

The safest migration starts before wireframes, CMS settings, templates and URL decisions are locked, because the redesign stage is where most future ranking problems are created. A consultant should shape the brief early enough to protect crawl paths, content depth, internal links, redirects, tracking and commercial pages before developers build around the wrong assumptions.

Google's own hiring guidance says a good time to hire search help is when you're considering a redesign or planning a new launch, with the work designed to make the site search-friendly from the bottom up. That advice matters because migration risk is rarely one isolated technical fault.

Planning Before Repair

A redesign can change the way content is grouped, the way service pages are linked, the way JavaScript renders, and the way users reach conversion points. If those decisions are made before search risk is understood, the seo migration checklist becomes a repair list instead of a planning tool.

A migration can involve a new CMS, new templates, rewritten content, different navigation, a changed domain name, a new JavaScript framework, or a changed URL structure. Each one can alter how search engines crawl, interpret, index and rank the site.

The Early Decisions That Set The Risk

Before the build starts, I want a clean decision log covering the pages, templates and tracking points that must be protected. That log gives designers, developers and decision-makers a shared reference before build work begins.

• The team should identify the pages that generate leads, sales, backlinks, revenue or assisted conversions.
• The team should mark the URLs that must keep their search engine rankings after launch.
• The team should define which templates need indexable body content, metadata, schema and internal links.
• The team should confirm which analytics properties, Search Console properties and event tracking must survive launch.
• The team should document staging site rules that prevent test pages being indexed before release.

That decision log stops the migration process becoming a sequence of assumptions. It also makes trade-offs visible when a cleaner design choice would quietly remove a search signal.

A Consultant Sees A Different Brief

A web design team is often judged on the look, speed, CMS usability and launch date. My job is to ask what happens to the pages that already work.

These aren't glamorous checks, but they matter: whether old URLs are mapped one-to-one, whether high-authority pages are merged without a content plan, and whether old blog posts are deleted despite earning links. I also check whether location pages lose unique copy, and whether forms or thank-you pages change without preserving reporting continuity.

Why Timing Changes The Cost

Where I see this go wrong, the migration is treated as a delivery task instead of a commercial risk event. The launch still happens, but the pipeline gets quieter three weeks later.

Early involvement is cheaper because the recommendations can still shape structure. Late involvement is slower because the consultant is asking a team to unpick templates, rewrite redirects, restore content and reopen decisions that were already approved.

This is why seo website migration services shouldn't be bought as a last-minute technical audit. The best work happens when search is part of the planning, not a ticket added when the site is almost ready.

Which Migration Risks Usually Damage Organic Performance?

Most failed migrations come from normal development decisions that make sense in isolation but damage search performance in combination. A cleaner menu, a new CMS, a rewritten service page and a redirect spreadsheet can all look fine separately, while the combined effect removes the signals Google used to trust.

A good seo migration checklist looks beyond whether pages exist. It checks whether the new site preserves the relevance, authority, internal prominence and measurement setup of the old one.

The Common Failure Modes

Google's site move documentation, updated on 17 June 2026, advises mapping old URLs to new URLs, preparing the new site, setting redirects, and monitoring both old and new URLs. It also says a medium-sized site can take a few weeks for most pages to move in Google's index, while larger sites can take longer, according to Google's site move guidance (developers.google.com).

These failures are rarely dramatic on launch day. They often show up after Google has recrawled enough pages, users have followed enough broken paths, and reporting has lost enough continuity to make diagnosis harder.

Definitions That Matter

A 301 redirect is a permanent server instruction that sends an old URL to its new equivalent. A canonical tag is an HTML signal that tells Google which version of a page should be treated as the preferred version when similar URLs exist.

Those two terms sound technical. In a migration, they decide whether historic search value is consolidated or scattered.

A domain migration is a move from one domain to another, such as changing brand name, consolidating sites or moving from an old web address to a new one. Domain migration work carries extra risk because Google has to process both the URL changes and the site identity change.

Why Combined Changes Are Harder To Diagnose

A simple template refresh is easier to monitor than a full platform change. A rebuild that changes URLs, content, navigation, design system, tracking, page speed and domain at the same time is much harder to read.

If organic traffic drops after a complex launch, the cause might be redirects, lost content, slow rendering, poor internal linking, blocked pages, missing schema or weaker commercial intent. That's why the migration process needs a baseline before launch.

The baseline should show which URLs earned clicks, links, conversions and impressions before anything changed. Without that baseline, recovery becomes guesswork.

Should You Hire A Consultant Or A Larger Agency?

Hire an independent consultant when the migration needs senior judgement, direct technical scrutiny and tight accountability across a small number of business-critical pages. Hire a larger agency when the work needs a full delivery team, multilingual production, analytics engineering, development resource and account coordination at scale.

The point isn't that one model is always better. The point is fit.

For many small and mid-sized UK businesses, the missing role isn't another project manager. The missing role is an experienced search person who can challenge decisions before they become expensive.

Where A Consultant Fits

If you're a founder, marketing director or head of growth, you probably don't need five people in status calls to tell you the 50 URLs that matter most. You need someone who can read the migration brief, challenge the build assumptions, crawl the old site, inspect the staging site and give developers decisions they can act on.

A consultant model works well when the business has an existing web developer or web design agency already managing the build. It also works when the migration risk sits mainly in URLs, content, redirects, templates and tracking.

The model is strongest when the site has a clear set of revenue pages that need protection. It suits decision-makers who want direct access to the person doing the work and no long-term contract after the migration risk has passed.

Direct Senior Input

This is also where my SEO consultant work usually fits. The job is to add senior search judgement into an existing project, not to replace the designers, developers or internal marketing team.

That direct involvement matters during a pressured migration process because decisions often need to be made quickly. A senior consultant can explain the trade-off, approve the practical route and keep the seo migration checklist tied to commercial risk rather than abstract best practice.

Where An Agency Fits

A larger agency can be a better fit when the migration involves multiple regions, heavy content rewriting, paid media coordination, data warehouse work, complex ecommerce feeds, or several development squads. That model can make sense if delivery capacity is the blocker.

My concern is the common middle ground. Some businesses pay agency rates but still get migration work passed to a junior team member using a standard checklist.

Polaris Agency, Marcel Digital and Extra Mile Digital all point towards migration support as a managed service, which is useful for buyers comparing providers. The gap I care about is the decision before purchase: who'll inspect the staging build, who'll challenge URL decisions, and who's accountable if the migration plan is wrong.

Accountability Should Feel Direct

Good seo website migration services should feel direct. You should know who's reviewing the staging site, who's approving redirect logic, who's checking tracking and who's monitoring the first week after launch.

If the answer is hidden behind account management, ask more questions. Migration work rewards experience because small technical choices can have large commercial consequences.

What Should A Pre-Launch SEO Migration Checklist Cover?

The pre-launch work should produce a clear risk register, not a vague promise that the site has been checked. A proper seo migration checklist covers current performance, URL mapping, content parity, template changes, internal links, crawl controls, redirect rules, analytics and fallback plans before launch day.

The checklist isn't the strategy by itself. It's the control system that makes sure the strategy survives design, development, QA and release pressure.

The migration process is like an office move while customers are still calling the old number. If the forwarding, signage and handover notes aren't right, people don't care that you've got a better-looking reception desk.

My Pre-Launch Review

I start by separating pages into risk tiers. A homepage with strong brand demand, a service page generating enquiries, and an old blog post with 40 referring domains don't deserve the same treatment as a thin announcement page from 2019.

The pre-launch checks usually include:

• I crawl the current site and export all indexable URLs, titles, canonicals, status codes and internal links.
• I pull Search Console data for landing pages, queries, clicks, impressions and average position.
• I identify URLs with backlinks, assisted conversions, leads, sales or strong local visibility.
• I map every valuable old URL to the closest new URL, not just the nearest category.
• I crawl the staging site and compare metadata, headings, content blocks, schema and canonical tags.
• I check that XML sitemap files contain the new indexable URLs only.
• I confirm that GA4, form tracking, call tracking and conversion events are present before launch.

Domain Checks Before Launch

For a domain migration, I also want both old and new properties available in Google Search Console where possible. That makes it easier to monitor the handover between old and new URLs.

The checks should also cover brand queries, old domain redirects, sitemap ownership and any third-party systems that still reference the previous domain. Domain migration work fails when the technical move is treated as just another URL change.

The Staging Site Problem

A staging site is a private version of the new build used for testing before release. It should be blocked from public indexing, but the live version must not inherit those blocks.

This sounds basic. It's still one of the easiest ways to break a launch.

Ahrefs' Patrick Stox updated his migration guidance on 17 January 2025 and flags staging access, backups, Search Console access and analytics access as practical requirements before launch. He also notes that a checklist alone isn't enough, because migrations involve many people and moving parts, in Ahrefs' migration guide (ahrefs.com).

Content Parity Needs Human Review

Content parity means checking that the useful content from the old page still exists on the new page where it needs to. It doesn't mean blindly copying every paragraph.

A commercial service page might need the same search intent coverage, proof points, locations, FAQs, comparison language and internal links. It can look cleaner, but it shouldn't become weaker.

This is where many rebuilds lose ground. The new page reads nicely, but the old page answered more buyer questions and matched more search demand.

Redirect Mapping Should Follow Intent

A redirect map shouldn't be a spreadsheet filled by matching similar-looking URLs. It should map old intent to new intent.

If an old page about emergency IT support generated leads, the replacement should answer the same need. Sending it to a generic IT services page weakens relevance, even if the redirect technically works.

For domain migration projects, redirect mapping is even more important because external links, branded searches and old bookmarks all need a clean route into the new site. The migration process shouldn't treat that historic value as disposable.

How Should Launch Day Work?

Launch day isn't the time to discover that the redirect rules only covered the top-level pages. The first 24 hours should be treated as a controlled verification window, with a short command list, named owners, rollback criteria and live checks across crawlability, redirects, indexability, analytics and core templates.

A launch plan should be boring in the best possible way. Everyone should know what's being checked, who owns each fix, and what level of fault would pause the release.

The Launch Sequence

For smaller UK business sites, I usually want the launch window planned for a quieter period. Google gives similar advice for site moves where seasonal dips exist, because fewer users are affected.

The launch checks run in a tight order:

• The team should confirm that the live site returns `200` status codes on the expected indexable URLs.
• The team should confirm that priority old URLs return `301` or `308` redirects to the mapped new URLs.
• The team should confirm that no production page carries staging `noindex` or blocked robots.txt rules.
• The team should confirm that canonicals, hreflang where relevant, schema and page titles render as expected.
• The team should submit the new XML sitemap in Google Search Console.
• The team should test GA4 events, forms, phone clicks and key conversion paths.
• The team should crawl priority URL samples across mobile and desktop user agents.

Evidence During Release

Those checks don't need to take weeks. They need to happen in the right order, with evidence captured while the development team is still available.

For practical seo website migration services, that evidence might be a redirect test export, crawl sample, Search Console note, analytics event test and list of unresolved launch issues. The point is to leave the release window with facts, not just confidence.

What I Do Not Accept As A Pass

A developer saying "the redirects are in" isn't enough. I want a crawl export or test output showing that the URLs resolve correctly.

A designer saying "the pages are there" isn't enough either. I want to know whether the important copy, headings, internal links, metadata and structured data survived the template change.

Google says 301 and other permanent redirects don't cause PageRank loss, but that statement assumes the implementation is sensible. Redirecting 200 service pages to the homepage isn't sensible, even if the status code is technically permanent.

Evidence Beats Reassurance

Launch-day evidence should be simple enough for a business owner or marketing lead to understand. It should show which priority URLs were tested, what they returned, and whether any issues need immediate action.

That evidence also protects the developer. Instead of vague blame when traffic moves, the team can see what was checked, what passed and what changed later.

For larger seo website migration services, I'd expect the same principle at greater scale. More URLs, more templates and more stakeholders still need clear proof, not verbal reassurance.

What Should Post-Launch Monitoring Include?

Post-launch monitoring should compare what Google and users see before and after the release, not just whether the new site is online. The first 30 days should track indexed URLs, crawl errors, priority queries, landing page clicks, lead events, redirect behaviour, server logs and any pages that lose visibility.

The goal isn't to panic at every ranking wobble. The goal is to separate normal recrawling from fixable damage.

The First 48 Hours

The first checks are technical. I look for crawl errors, analytics gaps, broken templates, missing forms, wrong canonicals and pages blocked from indexing.

Here's what the first 48-hour review should cover:

• Search Console coverage changes and URL Inspection samples should be reviewed.
• Server errors, redirect chains, unexpected 404s and soft 404 patterns should be investigated.
• GA4 event firing for forms, phone clicks, downloads and ecommerce events should be tested where relevant.
• Priority keyword and landing page movement should be watched without overreacting to normal fluctuation.
• Manual checks for branded searches, key service terms and local results should be completed.

Reading The First Signals

If the issue is obvious, fix it quickly. If the data is noisy, keep monitoring until the pattern is clearer.

A sensible migration process separates urgent faults from normal volatility. Broken redirects, missing forms and live `noindex` tags deserve immediate action, while small ranking changes may need a few more days of evidence before the team rewrites the plan.

The First 30 Days

If rankings move in the first few weeks, the question isn't whether movement happened. It's whether the movement is expected recrawling or evidence of a fixable fault.

Google says temporary ranking fluctuation can happen while it recrawls and reindexes moved pages.

When Recovery Work Is Needed

Recovery work starts by finding the pages that lost clicks, impressions, leads or rankings. Then the investigation works backwards through redirects, indexability, content changes, internal links, rendering and tracking.

The fix might be technical, but it's not always technical. Sometimes the new page simply removed the substance that made the old page rank.

That's why post-launch review should include both crawl data and page-level judgement. A tool can show that a page exists, but it can't always tell whether the new copy answers the same commercial intent.

Choosing The Right Migration Support

The right provider should ask about risk, revenue, developers, analytics, redirects and commercial pages before talking about deliverables. If the first conversation is only about a generic checklist, you don't yet know whether they're capable of protecting the parts of the site that make money.

You're not buying a document. You're buying judgement during a change that can affect leads, sales, reporting and trust in the new site.

Questions To Ask Before You Buy

Google's 2026 hiring guidance recommends interviewing potential search providers, checking references, asking about expected results and timeframes, and being wary of anyone guaranteeing first place. It also says an audit should give realistic estimates of improvement and work involved, with read access to Search Console at that stage, according to Google's hiring an SEO guidance (developers.google.com).

Here's what to ask before signing:

• You should ask who will personally review the staging build.
• You should ask how the provider will prioritise URLs before the redirect map is written.
• You should ask what data will be used from Search Console, GA4 and crawl tools.
• You should ask what launch-day evidence you will receive.
• You should ask what happens if organic traffic drops by more than expected.
• You should ask whether you will deal with the senior person doing the analysis.

Site-Specific Answers

The answers should be specific to your site. A provider who can't talk about your commercial pages, tracking setup and development workflow is not ready to protect them.

Good seo website migration services should be able to explain how the seo migration checklist changes for your CMS, domain migration risk, analytics setup and revenue pages. If every answer sounds identical across every site, the review is probably too generic.

My Buying Advice

If a provider can't explain how they'll protect specific URLs, don't buy the service. If they talk only about tool exports, don't buy the service yet.

A list of 300 issues after launch isn't useful if the top 20 revenue pages were already damaged. A shorter plan, built early and owned by someone senior, is worth more than a bulky PDF produced after the decisions have been made.

My own fit is narrow by design. I work best with UK businesses that already have a developer, designer or internal marketing person, but need an experienced search consultant to protect organic performance through the migration.

Signs You Need Help Now

You probably need support before launch if the project includes a domain migration, a CMS change, a large URL restructure, a major content rewrite or a new JavaScript framework. You also need help if nobody owns the redirect map, nobody has compared staging content to live content, or nobody can say which pages generate organic leads.

You may still need help after launch if organic landing pages have dropped, Search Console shows unexpected indexing changes, form tracking has broken, or old URLs are returning 404s. At that point, the work becomes diagnosis and recovery rather than prevention.

For prevention, bring in search support while decisions can still change. For recovery, bring enough data to reconstruct what changed and when.

FAQ

This section answers practical questions that often sit underneath the buying decision. Here's the short version: early support protects choices, while late support repairs consequences.

A migration should have a named search owner, even if the build is being handled by a web agency or developer. Without that owner, important details fall between design, development and marketing.

Initial Filter

Use these questions as the quick filter:

• The site should be reviewed if it is changing URLs, templates, CMS, content structure or domain.
• The site should be treated as commercially sensitive if organic search already generates leads, sales, enquiries or local visibility.
• The project should have a named person responsible for redirects, indexability, tracking and Search Console checks.
• The team should be able to explain which old pages must keep their rankings after launch.

If those points are true, the migration carries commercial risk. The next question isn't whether to check the site. It's whether that risk is owned early enough to influence the build.

Quick Decision Rules

The main decision points are simple. Bring support in before structure, content and URL decisions are frozen, use a seo migration checklist as a control tool rather than a substitute for judgement, and treat domain migration work as higher risk because both URLs and site identity are changing.

Those rules help keep the migration process anchored when the project gets busy. They also stop the search review being pushed to the final week, when the important structural decisions have usually already been made.

How Early Should I Bring In A Consultant?

Bring in a consultant before URL structures, templates, navigation and content plans are signed off. Two to six weeks before development freeze is workable for many small and mid-sized sites, but larger migrations need earlier input.

The later the review happens, the more it becomes damage control. If a new site is already built, the work can still help, but some recommendations may be harder for the team to accept or implement.

For a domain migration, earlier is better because brand, analytics, redirect, Search Console and stakeholder communication all need more planning. That work shouldn't be squeezed into the final week.

Is A Generic SEO Migration Checklist Enough?

A generic checklist is useful as a memory aid, but it's not enough by itself. The checklist has to be applied to the specific pages, templates, redirects, analytics setup and commercial risks of the site.

A small brochure site, a local service business, a SaaS site and an ecommerce store can all need different migration priorities. The same line item can mean very different work in each case, so ask what the checklist means for your site.

Use a seo migration checklist to keep control, but don't treat it as a substitute for judgement. The value comes from knowing which items matter most when time is limited.

What If The Migration Has Already Gone Wrong?

Start with evidence, not guesswork. Crawl the old and new URL sets, compare Search Console data, review redirect rules, check indexability, inspect GA4 tracking and isolate the pages that lost clicks.

Most recovery plans begin with redirects, content restoration, internal links and crawl-control fixes. If the migration process wasn't documented, the first job is to rebuild the timeline from launch notes, crawl data, analytics and Search Console.

Recovery can work, but it's usually slower than prevention. The best time to protect organic performance is before the new structure goes live.

Do I Need SEO Website Migration Services For A Small Site?

You may not need a full project if the site is tiny, has little organic traffic and isn't changing URLs, content or domain. In that situation, a lighter pre-launch review may be enough.

You do need proper seo website migration services if the site already generates leads, sales, enquiries or meaningful local visibility from organic search. The risk is tied to business value, not just page count.

A 40-page site with strong local service rankings can deserve more care than a 4,000-page site with little organic value. The right level of support depends on what the site stands to lose.

Next Step

If you're planning a redesign, CMS move, domain change or major rebuild, get the search risk reviewed before launch. Josh Willett Consultancy Ltd provides UK-wide remote migration support for businesses that want senior technical judgement, direct access and clear ownership from the first planning call.