A poorly managed SEO migration can cost a website dearly: a botched redesign can wipe out, in a few days, organic traffic built up over years. These losses are usually avoidable with a rigorous method and proper monitoring. This guide walks you through the procedure, from preparation to monitoring after go-live.
Types of SEO migrations
Not all migrations carry the same level of risk:
| Migration type | Risk | Examples |
|---|---|---|
| Design/template change | Low | Visual redesign with no URL changes |
| CMS change | Medium to high | WordPress → Shopify, Drupal → Next.js |
| URL restructuring | High | Changing the category structure |
| Domain change | Very high | old-brand.com → new-brand.com |
| HTTP → HTTPS | Low (if done right) | SSL migration |
| Site merger | Very high | Consolidating several domains |
Phase 1: Pre-migration (4 to 8 weeks before)
A complete inventory of the current site
Before making any change, you need a complete inventory of your current site. Zerkado's SEO audit crawls your site, up to your plan's page limit, and matches it with the project's other data:
- The crawled URLs, compared with the sitemap; also export the list of indexed pages from Search Console
- For each page, Search Console clicks and impressions and the rankings of tracked keywords, along with the site's backlinks collected by the Backlinks module
- The internal linking structure (internal link graph, orphan pages)
- The title, meta description, canonical and hreflang tags of each page
- Baseline speed measurements (LCP, CLS and TBT, measured in the lab on mobile)
The 301 redirect plan
The redirect plan is the most critical document in any migration. Every URL on the old site must be mapped to its equivalent on the new site. The golden rules:
- 1:1 redirects: Each old URL points to the most relevant page on the new site
- No mass redirects to the homepage: if a page has no equivalent, redirect it to the closest parent page when it meets the same need; otherwise, let it return a 404 or 410. Google often treats a redirect to the homepage as a soft 404
- Avoid chains: A → B → C slows down crawling, and Googlebot follows no more than 10 redirects in a row. Redirect straight from A → C
- Test before going live: Check every redirect in a staging environment
Phase 2: Migration day
On switchover day, check first the points that cause the fastest losses:
- Robots.txt and noindex tags: the rules that blocked the staging environment must not reach production
- Redirects: test a sample of old URLs (high-traffic pages, pages that receive backlinks) and check that they return a 301 to the right page, in a single hop
- Canonical and hreflang tags: they must point to the new URLs, not to the old ones or to staging
- XML sitemap: publish the sitemap of the new URLs and submit it in Search Console
- Domain change: declare it with the Change of Address tool in Search Console
Then set up close monitoring in your rank tracking tool. Zerkado lets you refresh keywords on demand, within your plan's daily limit: refresh your strategic keywords first so you have a baseline at the moment of the switchover. Automatic checks then take over, daily for keywords in the top 10.
Phase 3: Post-migration (intensive monitoring)
The first 4 weeks after a migration are critical. Monitor daily:
- Indexing: the Page indexing report in Search Console (new URLs indexed, old URLs dropping out of the index)
- Rankings for your strategic keywords with Zerkado rank tracking
- Crawl errors: 404s, 500s, broken redirects
- Overall organic traffic: week-by-week comparison with the pre-migration period
- Backlinks: check that inbound links point to the right pages with backlink analysis
A temporary dip is common after a migration, while Google processes the redirects. A sharp drop that lasts, or that is concentrated on certain groups of pages, usually points to a redirect or indexing problem. Run a new technical audit: Zerkado flags 4xx and 5xx errors, redirect chains and loops, and pages blocked by robots.txt or set to noindex.
Try Zerkado for free for 14 days, with no credit card, before your next migration: you'll take an inventory of your site, within the trial's limits, and track your rankings after the switchover.

