A B2B business had decided to do three difficult things at once. It was moving its site off self-managed hosting on DigitalOcean and onto managed hosting with WP Engine. It was rolling out a new brand and a redesigned site. And it was reworking a good deal of its content in the same window. Each change was sensible on its own. Together, they were a quiet threat to the one thing nobody in the room was watching closely,the organic search visibility the business already depended on for demand.

There was plenty of energy behind the rebrand. What there wasn’t was a senior SEO owner asking the uncomfortable question: what happens to our rankings if we change the platform, the design and the words all at the same time? That was the gap I was brought in to fill.

The change on the table

The move itself was a genuine upgrade. Self-managed hosting on DigitalOcean gave the team full control and, with it, full responsibility, server maintenance, patching and security all sat with people who had better things to do. WP Engine’s managed environment would take that burden away, improve page speed and harden security. The redesign and new brand were overdue. The content rework was a deliberate attempt to tighten a library that had grown loose over time.

None of that was the problem. The problem was doing all of it in one release, where a single drop in rankings could have three possible causes and no obvious owner.

The real risk wasn’t the move

A hosting migration on its own is routine. A rebrand on its own is manageable. The danger of doing them together is attribution: if visibility falls, you cannot tell whether the platform, the design or the content caused it,and what you cannot diagnose, you cannot fix. The risk was never the move. It was moving everything at once.

So my first job was not technical. It was to decide what changed together, what stayed frozen, and what had to be protected no matter what. The plan came down to four questions: what to change together, what to keep frozen, what to protect at all costs, and what we could afford to lose.

Auditing before anything moved

None of those decisions were made on instinct. Before a single change went live, I ran a comprehensive audit to establish exactly where the site stood, its technical SEO, its content, and its search visibility, so we had a baseline to defend rather than a memory to argue about later. You cannot protect what you haven’t measured, and you cannot prove you protected it without a before.

That baseline fed a detailed technical SEO migration plan: what would change, in what order, and how each change would be tested. Alongside it sat pre and post-migration checklists, the practical safeguards that turn a plan into something a team can actually execute under pressure. The pre-migration list confirmed the redirect map, staging environment and page-level parity were right before cutover. The post-migration list verified indexability, redirects, speed and rankings held once the site was live, so anything that slipped was caught in hours, not weeks.

It’s unglamorous work, and it’s exactly the work that gets skipped when nobody senior owns the move. The audit and the checklists were what made the trade-offs deliberate instead of hopeful.

Protecting the channel that earns

With the sequence agreed, the technical work had a clear order of priority.

Every URL that was changing got a mapped, one-to-one 301 redirect,no chains, no guesses, no pages quietly dropped into a 404. The core commercial landing pages, the ones that bring in qualified demand, were treated as fixed points: their URLs, titles, metadata, headings and internal links were preserved through the redesign rather than left to the new template to reinvent. Structured data and internal linking were rebuilt to match, not left behind. The new site was staged and crawled on WP Engine before cutover, so the redirect map, indexability and speed were verified against a baseline instead of hoped for. After go-live, the same crawl ran again to catch anything that had slipped.

The point of all of it was simple: keep the search engine’s understanding of the important pages intact, even while everything around them changed.

What we chose to protect, and what we let go

The content rework meant some pages were consolidated, rewritten or retired. That was a deliberate decision, not an accident, and it was always going to cost some traffic on the pages we changed. What we would not trade was the brand’s own search visibility and the core keywords that bring in enquiries. Those were ring-fenced.

I’ll be straight about the outcome, because honesty is the point. The migration went through cleanly. Brand search visibility held. Core keyword traffic stayed consistent through the cutover and after it. There was some traffic loss, and it came from the content we chose to change, not from the platform move or the redesign. The things we set out to protect were still standing. The things we accepted we might lose were the only things that moved.

What the migration unlocked

Defending the channel was the immediate job. The lasting value is what the move set up. Managed hosting removed the maintenance and patching burden that had quietly been a reason content shipped slowly, so the business can now publish at a consistent cadence instead of in fits and starts, which is where the next phase of organic growth actually comes from. Page speed improved. Security posture improved, with managed patching and backups replacing a server the team had to babysit.

The site is no longer something to nurse through each change. It’s a platform to grow from.

The difference this made

Not a freelancer running a redirect map. Not an agency reporting the dip after the fact. The fractional lead job on this project was to see the commercial risk before the release, decide what to protect and what could give, and make every trade-off deliberate,so that when the numbers moved, we already knew why.

If your business is planning a re-platform, a rebrand or a redesign and wants the organic channel protected through it, that’s exactly the kind of decision I own. Start with a Leadership Review and we’ll map what to protect before anything moves.