Get Found · Site Migrations
Most sites migrate to escape something: a slow, insecure, or unmaintainable platform. The upside is real, and so is the risk that the move itself tanks the rankings you have spent years earning. I handle both: a clean move onto a platform built for performance, security, and maintainability, with your search equity carried over intact.
When this makes sense
The reasons to move are real: performance, security, and a stack your team can actually maintain. Whether you are on Wix, Squarespace, Drupal, or an aging WordPress build, migration is the path to a platform built to last.
New URLs, new information architecture, new templates. Even on the same platform, structural change demands a deliberate redirect and preservation plan, or the rankings tied to your old URLs quietly evaporate.
You have been burned before: rankings dropped after a launch and never fully recovered. This time you want it done right, with every URL baselined and mapped before anything moves.
Merging multiple domains or properties into one, where redirect logic and equity consolidation decide whether the combined site is stronger or weaker.
What gets done
How engagements work
Before anything moves: inventory every URL, baseline rankings and traffic, map redirects, and write the rollback plan. The planning is where migrations are won.
I build and migrate on staging where everything can be tested end to end, then coordinate a controlled launch with redirects live and DNS cut over, nothing left to chance.
After launch I monitor redirects, crawl errors, and indexation, and track ranking recovery through the settling period until the new site is stable and equal or better.
Selected work
Details anonymized; specifics available under NDA.
Common questions
Not if it’s done deliberately. Ranking loss comes from broken redirects, lost URLs, dropped metadata, and changed architecture, all of which are preventable with a proper redirect map, preserved metadata and structured data, and baselines taken before launch. The risk is real, which is exactly why the planning matters.
Wix, Squarespace, Drupal, Joomla, Shopify, hand-coded sites, and older or custom WordPress builds, moving to a modern, maintainable WordPress platform. I also handle WordPress-to-WordPress moves: redesigns, restructures, and consolidations.
A full URL inventory and ranking baseline before anything moves, a complete old-to-new 301 redirect map, migration of metadata, canonicals, and structured data, internal-link and image-path fixes, and a staging-first build that’s crawled and validated before go-live. After launch I monitor redirects, crawl errors, and ranking recovery through the settling period.
Yes. Consolidating domains or properties is one of the trickiest migrations: redirect logic and equity consolidation decide whether the merged site ends up stronger or weaker. It’s a deliberate, mapped process, not a bulk redirect.
It depends on size and complexity, but the planning phase, inventory, baselines, and redirect mapping, is where most of the care goes. The migration itself happens on staging where it can be fully tested, then a coordinated launch. Most migrations run a few weeks end to end.
Recent thinking
The decision to leave Wix or Squarespace usually comes from outgrowing them. You want real performance, control over how the site works, custom functionality the...
Read the article
The scenario is common enough to count as a category: a business has five or six domains, each with a WordPress site of various vintages,...
Read the article
Custom WordPress frameworks were a reasonable answer to a real problem. Vanilla WordPress, circa 2015, didn’t have built-in environment management, didn’t compose well with Composer,...
Read the articleA migration engagement is fixed-scope and staging-first: a faster, more secure platform at the end of it, with your rankings baselined and preserved through the move. Let us plan it properly.
Start a conversation