SEO migrations
Planning, checking and monitoring a website move so that you keep the traffic and enquiries you have worked hard to earn.
Why migrations go wrong
A website redesign, move to a new platform or change of URLs is one of the riskiest moments for organic traffic. Pages disappear, redirects are missed, content is cut and tracking breaks. The damage is often noticed only weeks later, when enquiries have already dropped.
Most of this is preventable with a plan made before the build begins.
Experience with multi-site migrations
I have led SEO through the migration of several sites within a multi-brand group, working alongside developers, designers and content teams. That experience covers the unglamorous details that decide whether a launch goes smoothly: redirect mapping, staging checks, launch-day monitoring and fast fixes afterwards.
What the service covers
- Before. A benchmark of current traffic, rankings and top pages, a list of what must be kept and a clear SEO brief for the design and development team.
- Redirect mapping. Every important old URL matched to the right new one, tested before launch.
- Staging review. Checking the new site for indexing blocks, missing metadata, broken links, speed and mobile issues before anyone sees it.
- Launch support. A checklist for go-live and monitoring in the first days.
- After. Tracking recovery, fixing problems fast and comparing performance with the benchmark.
Types of migration
Redesigns, new platforms (for example moving to Shopify or WordPress), domain changes, merging several sites into one, moving from http to https, and restructuring URLs and categories. Each carries different risks, and the plan reflects that.
When to involve me
As early as you can. The best time is before the design is signed off, when changes are cheap. The second best is before launch. Please do not wait until the traffic drops, though I can help with recovery if that is where you are.
What I need from your developer
Collaboration is the first thing I ask for in a successful migration. I need three things from the development team:
- Communication: what they have implemented, when, and when any further fixes are planned.
- Implementation on the day of launch, or access to the site so that I can fix any SEO issues myself if needed.
- A willingness to hear about things that a developer who has not worked with SEO for years may not think are important.
Working with developers, not around them
I am not trying to tell developers how to do their jobs. I spot things they may not have seen before, and a migration goes best when we work on it together.
Why migrations go wrong, in my experience
In my experience, migrations that go wrong tend to go wrong for three reasons. SEO was not involved early enough. A decision was made without checking what it would do to search, however well meant. Or simple things were not checked.
None of this is complicated. But the impact when one of them is missed can be big, which is why I ask the same simple questions every time.
What good and bad look like
A good migration is collaboration between the client, the web developer and the SEO team, with great communication and a lot of planning. A bad one is rushed, with no collaboration.
Tiffany Fowler
The simple checks I make
- Does the new site have a sitemap, and has it been submitted?
- Is the site set to be indexed, rather than blocked by a setting left over from development?
- Has the core, best-performing content been carried over, together with the pages that support it?
- Has the expertise shown on the old site been maintained on the new one, including depth, authorship and proof?
- Are redirects in place and tested, and is tracking working from day one?
A typical migration timeline
- Planning. Decide what is changing, benchmark performance and agree the SEO requirements.
- Design and build. I advise on structure, content and technical needs while the site is made.
- Staging. Review the test site, fix issues and test redirects.
- Launch. Go-live checks, sitemap submission and close monitoring.
- Aftercare. Weeks of monitoring and fixes, followed by a review against the benchmark.
Content, design and SEO need to agree
Many migrations suffer because design, development and marketing work separately. A designer may remove text that was bringing in traffic. A developer may change URLs for tidiness. A copywriter may rewrite pages without knowing which ones rank. I act as the link between these teams, so that everyone understands what must be kept and why.
Frequently asked questions
Will I lose traffic during a migration?
Short, small dips are common and can be managed. Large lasting losses are usually caused by missing redirects, blocked pages or lost content, which good planning prevents.
Can you help after a migration has already gone wrong?
Yes. I audit what changed, find the cause and put together a recovery plan.
How long does a migration project take?
It depends on the site. I usually become involved a few weeks before launch for smaller sites, and from the start of the project for larger ones.
Should I change my URLs during a redesign?
Only if there is a good reason. Every URL change adds risk. If you do change them, every important old URL needs a redirect.
Can I migrate and rebrand at the same time?
You can, but it increases the risk. I usually suggest planning them together and, where possible, separating the steps.
What does it cost if a migration goes wrong?
It can mean weeks or months of lost enquiries and a lot of repair work. A small amount of planning up front is much cheaper.
Related
Want to talk about your search results?
Email me a few lines about your business and website. I will tell you honestly whether SEO is likely to be worth it for you right now.