Website migration SEO is the work that protects your rankings when your URLs, platform or domain change. It comes down to five steps: record benchmarks, list every old URL, map each one to its closest new page with a 301 redirect, test on staging, then monitor Search Console for 8 to 12 weeks after launch.
Google says rankings may fluctuate while it recrawls a moved site, and that a medium-sized site can take a few weeks or more to settle. A careful migration keeps that dip short and shallow. This checklist covers every common type of move, including the small-business switches most guides skip: Wix or Squarespace to WordPress, and WordPress to Shopify.
Key takeaways
- A redesign only affects SEO when URLs, content, internal links or crawlability change, so keep URLs wherever you can.
- Map every old URL to its closest new equivalent with a server-side 301 redirect, and keep redirects for at least a year.
- Use Search Console’s Change of Address tool only for domain or subdomain moves, never for HTTP to HTTPS.
- Before launch, carry over titles, content, canonicals and internal links, and plan the removal of every staging noindex rule.
- Monitor Search Console, 404 logs and GA4 key events for 8 to 12 weeks against your pre-launch benchmarks.
Does a website redesign affect SEO?
A redesign affects SEO when it changes something search engines rely on: the URLs, the content on each page, internal links, titles and headings, or whether pages can be crawled. Change the look and keep those intact, and rankings rarely move. Change URLs without redirects, and the affected pages can drop out of results.
So a migration isn’t only a platform or domain change. Any project that changes URL paths counts, including a redesign that renames service pages or merges old blog posts. If you’re still deciding whether to redesign at all, start with our website redesign checklist; this guide assumes the decision is made.
Which type of website migration are you doing?
Name the migration type first, because it sets the risk and the steps. Google treats HTTP to HTTPS, domain changes, merged domains and changed URL paths as site moves with URL changes; a hosting move that keeps every URL is simpler.
| Migration type | What changes | SEO risk | Key extra step | Change of Address tool? |
|---|---|---|---|---|
| Hosting move | The server only; every URL stays the same | Low | Lower DNS TTL a week ahead and keep the old host running until its traffic reaches zero | No |
| HTTP to HTTPS | The protocol on every URL | Low to medium | 301 every HTTP URL to its HTTPS version and update canonicals and sitemaps | No |
| Redesign with new URLs | Page paths, content and internal links | Medium to high | A full redirect map plus content carry-over checks | No |
| Platform change | The CMS or store platform, and usually its URL patterns | Medium to high | Match old URL patterns where the new platform allows, redirect the rest | No, unless the domain also changes |
| Domain change | The hostname on every URL | High | Verify both properties and submit Change of Address | Yes |
| Merging sites | Several domains or subdomains become one | High | Move one site at a time and let traffic settle in between | Yes, for each retired domain, one move at a time |
Google’s Change of Address guidance warns against moving several sites to one new location at once, because it can cause confusion and traffic loss. If you’re merging, finish one move, wait for traffic to stabilize, then start the next.
Phase 1: What should you benchmark and inventory before migrating?
Record how the current site performs and list every URL it has, before anything changes. Without the list you can’t build redirects, and without benchmarks you can’t tell a normal dip from a real problem.
Benchmarks to save
- Search Console Performance: clicks and impressions by page and by query for the last 16 months, exported to a spreadsheet.
- GA4: sessions and key events by landing page, so you know which URLs bring in inquiries or sales.
- Top linked pages: from the Links report in Search Console; these URLs must redirect perfectly.
- Indexed pages: the count in the Page indexing report, as a baseline.
- Rankings: positions for the 20 to 50 queries that matter most commercially, tracked in the same tool before and after.
Build the complete URL list
Combine several sources, because no single one catches everything: your XML sitemaps, a full crawl, the pages listed in the Search Console Performance report, GA4 landing pages and the pages your backlinks point to. Google’s site-move guide also asks you to include embedded resources such as images, videos, JavaScript and CSS files.
Remove duplicates and add columns for traffic, key events and links. That spreadsheet becomes your redirect map.
Phase 2: How do you build a 301 redirect map?
Give every old URL a destination: the page on the new site that best answers the same need, reached through a server-side 301 redirect. The redirect map is a spreadsheet with one row per old URL, and it’s the most important document in any migration.
| Old URL | New URL | Status | Note |
|---|---|---|---|
| /services-page/ac-repair.html | /services/ac-repair/ | 301 | One-to-one match |
| /blog/2019/05/ac-tips/ | /blog/ac-maintenance-tips/ | 301 | Post kept, path shortened |
| /ac-repair-offer-2021/ | /services/ac-repair/ | 301 | Expired offer, sent to the closest relevant page |
| /old-team-gallery/ | None | 410 | Removed, with no relevant replacement |
Redirect rules that protect rankings
- Use server-side permanent redirects (301 or 308). Google treats them as a signal that the new URL should be canonical; temporary redirects such as 302 and 307 don’t send that signal.
- Send each URL to its closest equivalent. Google’s site-move guide advises against redirecting many old URLs to one irrelevant destination, such as the homepage.
- Point every old URL straight at its final destination. Googlebot can follow up to 10 hops in a redirect chain, but Google advises redirecting directly.
- Let content with no replacement return 404 or 410 rather than forcing a redirect.
- Keep redirects for as long as possible: Google’s guide says generally at least one year, so signals can transfer to the new URLs.
- Update internal links to the new URLs instead of relying on redirects.
On an Apache server, simple rules can live in the .htaccess file; Nginx servers and hosted platforms use their own methods, which our web development team or your host can set up. These lines are an example only, so test any rule on staging first.
# Example only: Apache .htaccess redirects (mod_alias)
Redirect 301 /services-page/ac-repair.html https://www.example.com/services/ac-repair/
Redirect 301 /blog/2019/05/ac-tips/ https://www.example.com/blog/ac-maintenance-tips/
Redirect 410 /old-team-gallery/
# Pattern rule: move every URL under /news/ to /blog/
RedirectMatch 301 ^/news/(.*)$ https://www.example.com/blog/$1Platform notes: WordPress, Shopify, Wix and Squarespace
The platform you move to decides where redirects live and how much of the old URL structure you can keep. When you leave Wix or Squarespace, their redirect tools stop mattering, because they no longer serve your domain: the redirects must be created on the new site.
| Moving to | Can you keep old URLs? | Where to add redirects |
|---|---|---|
| WordPress | Often. Settings > Permalinks accepts a custom structure, so a Wix blog’s default /post/ path can be mirrored with /post/%postname%/ | A redirect plugin such as Redirection (free, logs 404s, imports CSV), or server rules |
| Shopify | Rarely. Products and collections sit under fixed paths such as /products/ and /collections/ | Content > Menus > View URL redirects, one at a time or by CSV import |
| Wix | Page slugs, yes; blog posts use a /post/ prefix by default, which can be renamed but not removed | SEO & GEO > Tools and settings > URL Redirect Manager |
| Squarespace | Page slugs, yes | URL mappings in the Developer tools panel, one rule per line |
On Shopify, a redirect only works from a URL that returns a 404, so the old path must not exist as a live page. Moving a whole WooCommerce store also involves product data, customers and order history, which our WooCommerce to Shopify migration guide covers.
Phase 3: What should you check on staging before launch?
Crawl the staging site and compare it with your URL list and benchmarks before launch day. Problems found here cost minutes to fix; found after launch, they cost traffic.
- Staging is password-protected, and none of it appears in Google.
- Every redirect in the map resolves in one hop to a page that returns a 200 status.
- Titles, meta descriptions, H1s and body copy of ranking pages are carried over or deliberately improved, not accidentally cut.
- Each new URL has a self-referencing canonical tag on the live domain, not the staging domain.
- Navigation, internal links and the new XML sitemap point to final URLs.
- Structured data, image alt text and any hreflang annotations are carried across.
- A live robots.txt is ready that blocks nothing important, and every development noindex rule is listed for removal.
- GA4 and Search Console verification work on the new templates, and key events fire.
- Core Web Vitals on the main templates are no worse than your benchmarks.
These checks belong to the testing stage of the website development process. For every crawl, indexing and markup check a new site needs, use our technical SEO checklist for new websites.
Phase 4: What do you do on launch day?
Launch early in the week, when your team can watch closely, and work through this list in order. Keep the old site’s files and database until the move is confirmed.
- Remove the staging password and noindex rules, and publish the live robots.txt.
- Deploy the redirects, then crawl your full old URL list in list mode to confirm each URL returns a 301 to the right page, or the planned 404 or 410.
- Submit the new XML sitemap in Search Console and keep the old one submitted for now. Google suggests using both during a move, then removing the old sitemap once it is processed.
- For a domain move, verify the old and new properties with the same Google account, confirm the old homepage 301s to the new one, then open Change of Address in the old property’s settings. Bing Webmaster Tools has its own Site Move tool.
- Run your most important new URLs through the URL Inspection tool.
- Update links you control outside the site: your Google Business Profile website field, social profiles, email signatures and ad final URLs. Then ask the sites that link to you most to update theirs.
Pakistan note
Moving from a .pk or .com.pk domain to a .com is a domain change, so it needs Change of Address. Google describes country-code domains as a strong signal that a site targets one country, so weigh that before leaving .pk if Pakistan is your main market. If you do move, keep the old domain renewed so its redirects keep working.
Moving hosting only?
If only the server changes, you don’t need a redirect map. Google recommends lowering your DNS TTL to a few hours at least a week before the move, then keeping the old hosting running until its server logs show no more traffic. A temporary drop in Googlebot’s crawl rate right after the switch is normal.
Phase 5: How long should you monitor after a migration?
Monitor closely for 8 to 12 weeks, then monthly until the old URLs have dropped out of Google’s index. Google says a medium-sized site can take a few weeks or more before new URLs replace old ones in results, and larger sites longer.
| When | What to check | Where |
|---|---|---|
| Days 1 to 7, daily | New 404s, redirect errors, key events and form deliveries | Redirect plugin or server 404 log, GA4 Realtime, a crawl of the old URL list |
| Weeks 1 to 4, weekly | New URLs being indexed and old URLs dropping out; crawl errors | Page indexing and Sitemaps reports in Search Console |
| Weeks 2 to 12, weekly | Clicks and impressions by page against the benchmark | Search Console Performance report, in compare mode |
| Weeks 4 to 12 | Rankings for tracked queries; key events by landing page | Your rank tracker and GA4 |
| Once the move is processed | Remove the old sitemap; keep redirects and the old domain | Search Console and your domain registrar |
Some movement in the first weeks is expected. What should worry you is a drop concentrated in particular pages or sections, because that usually points to a specific fault rather than normal reprocessing.
Website migration SEO problems: what goes wrong and how to recover
When traffic falls after a move, check this short list of faults first, comparing old and new URLs page by page. Each one can be fixed once you find it.
| Symptom | Likely cause | Fix |
|---|---|---|
| The whole site vanishes from results | A staging noindex rule or robots.txt block went live | Remove it, resubmit the sitemap and inspect key URLs |
| Old URLs show as not found | Missing or mistyped redirects | Add them from your 404 log and the redirect map |
| Old pages lose rankings instead of passing them on | Many URLs redirected to the homepage or a general category | Redirect each URL to its closest equivalent, or let it return 404 or 410 |
| Slow reindexing | Redirect chains, or internal links still pointing to old URLs | Point redirects at final URLs and update internal links |
| Wrong URLs indexed | Canonical tags pointing to staging or old addresses | Make canonicals self-reference on the live domain |
| Traffic seems to fall while rankings hold | The analytics tag or key events are missing on new templates | Reinstall and test tracking, and annotate the gap |
| Specific pages drop | Content cut or merged during the redesign | Restore the depth the old page had, or improve on it |
Recovery depends on how long a fault ran and how quickly Google recrawls the fixed URLs, so there’s no fixed timeline. If rankings haven’t returned weeks after the fixes, run a full SEO audit with free tools to rule out other causes.
How TechZone can help
TechZone plans and runs website migrations as part of our web development services, whether you’re redesigning on WordPress, leaving Wix or Squarespace, moving to Shopify or changing domain. Our SEO audit service turns these checks into a fix list ordered by impact. We build the benchmarks, URL inventory and redirect map with you, test on staging, handle launch day and monitor Search Console afterward. Nobody can promise zero ranking movement, but a careful process keeps the risk low. Book a free 30-minute consultation before you set a launch date.
Frequently asked questions
What is the difference between a 301 and a 302 redirect for SEO?
A 301 redirect tells Google a page has moved permanently, and Google uses it as a signal that the new URL should be the canonical one shown in results. A 302 redirect says the move is temporary, so Google doesn’t treat the target as canonical. Use 301 or 308 redirects for migrations, and keep 302 or 307 for genuinely temporary changes.
Should I change my domain and redesign my website at the same time?
Changing domain and redesigning at the same time is possible, but it makes problems harder to diagnose, because a traffic drop could come from the new domain, the new URLs or the new content. Where timelines allow, move the domain first with URLs and content unchanged, let traffic settle, then launch the redesign. If both must happen together, benchmarks and the redirect map matter even more.
How long should I keep my old domain after a website migration?
Keep the old domain registered and redirecting for as long as possible. Google’s Change of Address guidance suggests paying for the old domain for at least a year, partly so nobody else can buy it and misuse it, and its site-move guide recommends keeping redirects for at least a year. Because backlinks to the old domain can keep sending visitors for years, renewing it indefinitely is often the safer choice.
Can you migrate a website without losing any traffic?
A website migration can be done without lasting traffic loss, but short-term fluctuation is normal while Google recrawls and reindexes the new URLs. The goal is a small, brief dip, achieved through complete redirects, carried-over content and fast fixes. Be wary of anyone who guarantees no ranking change during a migration, because nobody controls how quickly Google reprocesses a site.
Who should handle a website migration, the developer or the SEO specialist?
A website migration works best when the developer and the SEO specialist plan it together from the start. The SEO specialist owns benchmarks, the URL inventory, the redirect map and post-launch monitoring, while the developer implements redirects, canonicals and server settings. On small projects one experienced person can do both, provided the redirect map is written before the build begins.
Sources and further reading
- Site Moves and Migrations – Google Search Central
- Change of Address tool – Search Console Help
- Redirects and Google Search – Google Search Central
- Changing Your Web Hosting and SEO – Google Search Central
- Creating and managing URL redirects – Shopify Help Center
- Customize permalinks – WordPress.org Documentation
