A new website is exciting. A new design, a faster platform, maybe a new domain. But a website migration is also one of the fastest ways to lose Google rankings you spent years building. Pages disappear, links break and traffic drops, often without anyone noticing until the phone stops ringing.
I’ve handled migrations from WordPress to Next.js, from page builders to custom themes and from old domains to new ones. The sites that keep their rankings all follow the same process. This website migration SEO checklist walks you through it: what to do before, during and after launch.
Quick answer: Before launch, save a full list of your current URLs, rankings and traffic, then map every old URL to its new one. At launch, set up 301 redirects, keep titles, content and internal links, remove any “noindex” tags and submit a new sitemap. After launch, watch Search Console for errors and traffic changes for at least a few months, and keep the redirects in place for at least a year.
What Counts as a Website Migration?
A migration is any big change that affects how Google finds and reads your site. The most common types are:
- Platform change: for example, Wix or WordPress to Next.js
- Domain change: moving from oldname.com to newname.com
- URL structure change: such as /services.php?id=4 to /services/roof-repair/
- HTTP to HTTPS: moving to a secure address
- Redesign: new layout and content, even on the same platform
Each one carries risk, and combining several at once makes problems harder to spot. If you can, change one major thing at a time.
Before Launch: Your Pre-Migration Checklist
This is the most important phase. Most traffic losses come from steps skipped here.
1. Crawl and Save Every Current URL
Use a crawler such as Screaming Frog to list every page on the current site. Also export pages from Google Search Console and Google Analytics, because crawlers miss pages with no internal links. Your list should include service pages, blog posts, images and PDFs.
2. Record Your Current Performance
Save a snapshot of where you are now: organic traffic by page, top keywords and positions, leads from organic search and pages with the most backlinks. Without this baseline, you can’t tell whether the new site is doing better or worse.
3. Build a Redirect Map
Create a spreadsheet with two columns: old URL and new URL. Every old page should point to its closest match on the new site. Don’t send everything to the homepage. Google may treat that as a soft 404, and visitors land somewhere unhelpful.
4. Keep What’s Working
Pages that rank well should keep their core content, headings and keywords. Rewriting or merging your best pages during a migration is a common cause of ranking drops. Improve them later, once the move has settled.
5. Set Up a Staging Site Google Can’t See
Build and test the new site on a staging address protected by a password or blocked from indexing. This stops Google indexing a half-finished copy of your site as duplicate content.
6. Check the New Site Before Launch
Crawl the staging site and compare it with your old one. Check that titles, meta descriptions, headings, internal links, image alt text and structured data have all carried over.
Launch Day: What to Do When You Go Live
7. Put 301 Redirects in Place
Add the redirects from your map as server-side permanent redirects. Google’s site move guide recommends permanent redirects such as 301 or 308, and says to keep them “for as long as possible, generally at least 1 year.”
Test a sample of old URLs straight after launch. Each should go to the right new page in one hop, not through a chain of several redirects.
8. Remove Staging Blocks
This is the mistake I see most often. The “noindex” tag or robots.txt block used on the staging site gets copied to the live site. Google then drops the whole site from search. Check the live site’s robots.txt and page source on launch day.
9. Update Canonical Tags and Internal Links
Canonical tags should point to the new URLs, not the old ones or the staging address. Update internal links to go directly to new URLs instead of relying on redirects.
10. Submit a New Sitemap
Submit the new sitemap.xml in Google Search Console so Google finds your new URLs quickly. If you moved to a new domain, verify it in Search Console and use the Change of Address tool, which Google says is only needed when moving from one domain or subdomain to another.
11. Check Tracking
Make sure Google Analytics, Google Ads conversion tags and any call tracking still work on the new site. A migration that quietly breaks tracking can look like a traffic drop when it isn’t one, or hide a real one.
After Launch: Monitoring Checklist
12. Watch Search Console Every Week
Look at the Pages report for new 404 errors, redirect errors and pages that are “Crawled, currently not indexed.” Fix broken URLs by adding missing redirects.
13. Compare Rankings and Traffic
Compare organic traffic and rankings with your baseline. Some movement is normal. Google says that for medium-sized websites, it can take a few weeks or more for new URLs to replace the old ones in search, and longer for large sites.
14. Update Your Business Listings and Backlinks
Update your website link on your Google Business Profile, social profiles and directories. Ask sites that link to your most important pages to update their links to the new URLs.
15. Keep the Old Domain
If you changed domains, keep renewing the old one and keep its redirects running. If it expires, every backlink pointing to it is lost.
Website Migration SEO Checklist at a Glance
| Phase | Task | Why it matters |
|---|---|---|
| Before | Save all URLs and performance data | Gives you a baseline to compare |
| Before | Build a redirect map | Keeps rankings and backlinks |
| Before | Block staging from Google | Avoids duplicate content |
| Launch | Add 301 redirects | Sends users and Google to new pages |
| Launch | Remove noindex and robots blocks | Keeps the site in search |
| Launch | Submit new sitemap | Speeds up discovery of new URLs |
| After | Monitor Search Console weekly | Catches errors early |
| After | Keep redirects for at least a year | Protects long-term rankings |
Common Migration Mistakes
- Redirecting every old page to the homepage
- Launching with “noindex” still on the site
- Deleting pages that bring traffic without redirecting them
- Changing domain, design, content and URLs all at once
- Letting the old domain expire
- Forgetting to update tracking codes
If traffic has already dropped after a migration, don’t panic. Most problems can be fixed with missing redirects and a technical check, especially if you act quickly.
Frequently Asked Questions
Will I lose rankings when I migrate my website?
A short dip is common while Google processes the change, but a well-planned migration usually recovers within weeks. Big, lasting losses usually come from missing redirects, deleted content or indexing blocks left on by mistake. Following a website migration SEO checklist avoids most of them.
How long does it take to recover SEO after a migration?
For small and medium sites, rankings often settle within a few weeks to a couple of months. Google says larger sites can take longer. If traffic is still falling after two months, check for missing redirects, crawl errors and changed content.
How long should I keep 301 redirects?
Google recommends keeping redirects for as long as possible, and generally for at least a year. In practice, I suggest keeping them permanently, because old backlinks and bookmarks keep sending visitors for years.
Do I need to tell Google I moved my website?
Submit your new sitemap in Search Console for any migration. If you moved to a new domain, also verify the new domain and use the Change of Address tool in Search Console. Redirects do most of the work of telling Google where pages moved.
Should I redesign and change my domain at the same time?
It’s better not to. Each big change can affect rankings, and doing several at once makes it hard to find the cause of any drop. If you can, move the domain first, let it settle, then launch the redesign.
Final Thoughts
A website migration doesn’t have to cost you rankings. Save your data first, map every URL, redirect carefully, remove staging blocks and watch Search Console closely after launch. Follow this website migration SEO checklist and your new site should keep the traffic your old one earned.
If you’re planning a move, I can handle the SEO side for you. See my SEO audit and technical SEO service, or if you’re moving to a faster platform, compare Next.js vs WordPress and static site vs WordPress first. You can also contact me for a free migration review.
Comments
Be the first to share your thoughts or ask a question.
Leave a comment
Your email will not be published. Comments appear after review.