Traffic that finally converts
Technical audit with crawl and speed fixes, buyer-intent on-page work, internal links rebuilt.
Visits 2,140 → 4,432 · orders 116 → 149
A new website is a happy day for everyone except Google. Every address that changes without a redirect, every page that quietly disappears, every title the new theme resets costs rankings that took years to earn. I plan the move, map every old address to a new one, check the staging site and watch the numbers afterward.
Illustration. A real map for a store often runs to thousands of lines.
An SEO website migration is any change to a website big enough to alter how Google finds, reads or ranks its pages, handled so that rankings and traffic survive the change. That covers a new domain, a new platform, a redesign that changes addresses or content, merging sites, or moving between a .co.uk and a .com. The work is a plan, a redirect map, checks before launch and monitoring afterward. Your developer builds the new site. I make sure Google follows you to it.
Tick everything that applies. The score tells you how much planning the move needs.
A rough guide, not a quote.
| Type of move | Main risk | What I do about it |
|---|---|---|
| New domain (rebrand, .co.uk to .com) | Google treats it as a new site | Full redirect map, Change of Address, old domain kept redirecting |
| New platform (WordPress to Shopify) | URL patterns change for every product | Redirect rules per pattern, exceptions mapped by hand |
| Redesign with new URLs | Pages merged or dropped unnoticed | Traffic and link data on every URL before anything is cut |
| Merging several sites | Duplicate pages fighting each other | One winning page per topic, the rest redirected to it |
A 301 redirect tells Google and every visitor that a page has moved for good, and where. Done one-to-one, it carries most of the old page's rankings and links. Done lazily, with everything sent to the home page, it carries almost nothing.
The map is a spreadsheet with two columns: old address, new address. The skill is in the matching. A product that no longer exists goes to its closest category. A guide split into three goes to the one that answers the old title best.
Domain changes add two steps. Search Console has a Change of Address tool, and the old domain must stay registered and redirecting for years, because links on other sites keep pointing at it.

Every old address with its traffic, rankings, links and conversions, so nothing valuable is dropped.
Each old URL mapped to its closest new page, as a file your developer can load and I can test.
Titles, internal links, canonicals, schema, speed and robots rules checked before launch.
Rankings, traffic and indexed pages recorded, so afterward we know what moved.
Redirects tested at scale, noindex removed, sitemaps and Search Console updated.
Crawl errors, lost rankings and traffic by page watched weekly.
Rankings, traffic, indexed pages and backlinks recorded for every URL.
Every old URL listed, every new URL matched. Patterns by rule, exceptions by hand.
The new site crawled as Google would see it, including the noindex tag that must come off.
Redirects tested across the whole map, sitemaps swapped, the first crawl watched live.
Weekly checks for eight weeks. Lost rankings traced to their cause while recovery is quick.
You know which pages earn your traffic, and each one has a named new home.
Visitors and Google land on the new pages, not on errors.
Google re-crawls the site. Some rankings wobble while the new addresses take over.
Traffic settles close to where it was. A faster, better-structured site often ends up ahead.
A migration protects what you have. It does not create rankings you never had.
The old addresses return errors, the links pointing at them are wasted.
Google treats this much like an error page. The old rankings do not transfer.
The most common cause of a site vanishing after launch.
If traffic drops, nobody can tell which change caused it.
Someone else registers it, and years of links point at a stranger's site.
| Task | Can the developer do it? | Why an SEO does it instead |
|---|---|---|
| Set up the redirects | Yes, once they have the map | Writing the map needs traffic, ranking and link data |
| Keep the same URLs where possible | Yes, if asked early | Nobody asks early unless an SEO is in the project |
| Check staging for SEO problems | Partly | Canonicals, schema and rendering need specialist crawls |
| Update Search Console and sitemaps | Yes | Change of Address is easy to get wrong once |
| Spot and fix lost rankings afterward | Rarely | It takes benchmarks from before and weekly comparison |
Migration work usually happens under the developer's or agency's agreement with their client, and often under the client's own confidentiality terms, so I do not publish those projects. The results below come from clients who agreed to be shown, where technical work on crawling, speed and structure was the main lever.
Technical audit with crawl and speed fixes, buyer-intent on-page work, internal links rebuilt.
Visits 2,140 → 4,432 · orders 116 → 149
Crawl and speed fixes, keyword targeting, more content and better internal links.
Clicks 706 → 1.99K · position 20.7 → 13.3
A UK online store and a US paint protection film business.
Small sites: the inventory, the redirect map and a launch checklist for your developer to carry out.
The move handled end to end inside a monthly plan, with the staging review and eight weeks of monitoring.
Large stores and multi-country sites, staged launches, or several sites merging into one.
I do the work myselfI'm Muhammad Zohaib Ameer. I have worked in SEO since 2022 for businesses in the US, UK, Canada and the UAE. I write the redirect map myself and I test it myself, line by line, before anyone presses launch.




“If your developer says the redirects will be handled later, that is the moment to call someone. Later is after launch, and after launch is when the traffic has already gone.”
Muhammad Zohaib Ameer · OvaVerseSend your current website and, if you have one, the staging link. Within 48 hours you get a short recorded video audit of the risks I can see, the pages you cannot afford to lose, and what your developer must get right first.
The photo on this page is a custom AI-generated illustration, not a real client or event. Diagrams and sample numbers are labelled illustrations; case study screenshots are real.