August 1, 2026
How to Migrate a Website Without Losing Rankings (2026)
Migrating a website destroys rankings when nobody maps the old URLs to the new ones — do that mapping first and the rest of the move is mechanical.
- A 1:1 redirect map is the single biggest factor in how to migrate your website without losing rankings.
- 301 redirects at launch beat fixing broken links after Google recrawls the site.
- Google Search Console re-verification and sitemap submission should happen same day as launch, not a week later.
- Most migrations that lose traffic recover within 30 to 90 days if redirects were done right the first time.
- Nuvora builds redirect maps before touching a client's live site, not after.
Why this matters
Google indexes URLs, not brands. When you launch a new site on new templates, new navigation, or a new domain, every one of those old URLs stops resolving unless you tell Google exactly where each one moved.
Miss that step and the ranking signals attached to your old pages — years of backlinks, click history, and topical authority — go nowhere. They don't transfer automatically. A migration without a redirect plan is a ranking reset, not a relaunch.
The fix isn't complicated. It's tedious, sequential, and easy to skip when a launch deadline is looming. That's exactly when rankings get lost.
What you'll need
- A full crawl export of every live URL, including ones with zero visible traffic
- Google Search Console and Google Analytics access on the current property
- A staging environment separate from the live domain
- A spreadsheet mapping every old URL to its new destination
- A domain registrar login if the DNS is changing — see how to choose a domain name for your small business website if the domain itself is part of the move
- A launch window with low traffic (early morning, off-peak day)
- 30 to 90 days of post-launch monitoring capacity
The steps
1. Crawl and inventory every URL before you touch anything
Run a full crawl of the live site and export every indexed URL, not just the ones in your navigation menu. Old blog posts, category pages, and even broken legacy URLs that still rank matter here.
Cross-check this list against Google Search Console's Pages report to catch URLs the crawler missed. Skipping this step is the number one cause of lost rankings after migration — you can't redirect a page you didn't know existed.
Common mistake: crawling only the sitemap.xml, which often excludes orphaned pages that still carry backlinks.
2. Build a 1:1 redirect map
Every old URL gets exactly one new destination — never a blanket redirect to the homepage. A spreadsheet with two columns (old URL, new URL) is enough; sophistication doesn't matter here, coverage does.
Match by topic, not convenience. A page about pricing should redirect to the new pricing page, not the closest-sounding category.
Common mistake: redirecting everything to the homepage "to be safe." Google treats this as a soft 404 pattern and can drop the redirected pages from the index entirely within a few weeks.
3. Stage the new site and QA every template
Build the new site on a staging URL, blocked from indexing with a noindex tag or password wall. Test every page type — homepage, category, single post, contact form — before launch, not after.
Check that meta titles, meta descriptions, and header tags carried over or were rewritten intentionally. A migration is also the moment internal links quietly break if URL structures shift.
Common mistake: launching with staging noindex tags still active, which hides the entire new site from Google on day one.
4. Set 301 redirects at launch, not after
The redirect map from step 2 goes live the same moment the new site does — 301 redirects, permanent, not 302 temporary redirects. A 302 tells Google the move isn't permanent, so ranking signals don't transfer with the same strength.
Test a sample of 20 to 30 URLs manually right after launch, checking that each one lands on the correct new page and returns a 301 status, not a 200 or 302.
Common mistake: redirect chains — old URL to an intermediate URL to the final URL. Each hop dilutes signal; keep every redirect a single hop.
5. Update Google Search Console and submit the new sitemap
Add the new site as a property in Google Search Console if the domain changed, and submit the new XML sitemap the same day. If the domain stayed the same, re-submit the sitemap anyway to prompt a faster recrawl.
Use the URL Inspection tool on 10 to 15 high-value pages to request indexing manually rather than waiting for Google's own crawl schedule.
Common mistake: forgetting to update the sitemap URL referenced in robots.txt, which leaves Google crawling a sitemap that no longer matches the live site.
6. Lock down DNS, SSL, and security settings
If hosting or domain providers changed, verify SSL certificate installation before launch — a broken certificate throws security warnings that tank both rankings and user trust within hours. Review best website security features for small business sites for the baseline checks worth confirming post-migration.
Confirm DNS propagation is complete (usually 24 to 48 hours) before declaring the migration finished.
Common mistake: launching with an expired or mismatched SSL certificate carried over from the old host.
7. Monitor rankings and crawl errors for 30 to 90 days
Check Google Search Console's Coverage report daily for the first week, then weekly through day 90. A spike in "Not Found (404)" errors means redirects were missed somewhere in step 2.
Track your top 20 keywords by position daily for the first two weeks — small fluctuations are normal, but a sustained drop on a specific page usually points to a broken redirect or a content mismatch on the new destination.
Common mistake: assuming silence means success. No news in Search Console for two weeks after a migration is a red flag, not reassurance — it usually means Google hasn't recrawled yet.
Troubleshooting
Traffic dropped but rankings look stable. Check for tracking code issues first — Google Analytics tags sometimes get lost in a template rebuild, making it look like traffic vanished when it didn't.
A specific page lost its ranking entirely. Pull that URL's redirect status. A 302 instead of a 301, or a redirect chain longer than one hop, is the usual cause.
Search Console shows a spike in 404s. Cross-reference the 404'd URLs against your original crawl export from step 1 — these are almost always URLs that were missed in the redirect map.
Rankings dropped across the whole site, not just individual pages. This usually means the new site launched with noindex tags still active, or robots.txt is blocking crawlers. Check both within the first 24 hours.
The new domain isn't showing up in search at all. Confirm the new property was added and verified in Google Search Console — a domain change without re-verification means Google is still crawling the old property's data.
Tools and resources
- Google Search Console — coverage reports, URL inspection, sitemap submission
- A crawler (Screaming Frog or similar) for the pre-migration URL inventory
- Your hosting provider's redirect rules panel or .htaccess/nginx config access
- Best website hosting plans for small business owners if hosting itself is changing as part of the migration
- A rank tracker for the daily keyword check in step 7
Migrating a site in 2026?
Nuvora handles the redirect map, QA, and Search Console reset as part of every rebuild.
What to do next
Once the migration holds for 90 days and rankings stabilize, shift focus to keeping the site from drifting again. Ongoing uptime, security patching, and content updates are what prevent the next migration from being a rescue mission instead of a routine rebuild.
FAQ
How to migrate your website without losing rankings?
Build a 1:1 redirect map before launch, set 301 redirects the moment the new site goes live, and resubmit your sitemap to Google Search Console the same day. Most sites that follow this order recover fully within 30 to 90 days.
How long does it take for rankings to recover after a website migration?
Rankings typically stabilize within 30 to 90 days if redirects were set correctly at launch. Migrations without a redirect map can take much longer, or never fully recover, because the old ranking signals were never passed forward.
Do 301 redirects pass full SEO value to the new page?
A 301 redirect passes the large majority of a page's ranking signal to its new destination, which is why it's the standard for permanent moves. A 302 redirect, by contrast, tells Google the move is temporary and ranking signals transfer weaker or not at all.
Should I redirect every old URL to the homepage?
No. Redirecting everything to the homepage is one of the fastest ways to lose rankings during a migration. Each old URL should map to the new page covering the same topic, not a generic catch-all.
Do I need to update Google Search Console when I migrate my website?
Yes, especially if the domain changed — add and verify the new property, then submit the new sitemap the same day as launch. If the domain stayed the same, resubmitting the sitemap still speeds up recrawling.
What's the biggest mistake businesses make when migrating a website?
Skipping the pre-migration URL crawl. Businesses that only redirect the pages in their navigation menu miss orphaned URLs that still carry backlinks and traffic, and those pages lose their rankings with no warning.
Can a website migration hurt rankings even if the domain doesn't change?
Yes. Changing URL structure, templates, or navigation on the same domain can still break internal links and confuse crawlers if redirects and sitemap updates aren't handled the same way as a domain change.
How do I know if my migration broke something?
Check Google Search Console's Coverage report daily for the first two weeks. A spike in 404 errors or a sustained drop in a specific page's ranking position both point to a redirect that was missed or set up wrong.
One last thing
The migrations that lose the most traffic in 2026 aren't the ones with bad redirects — they're the ones where nobody checked the redirect map against the actual crawl. A spreadsheet built from memory instead of a real crawl export always misses URLs, and those missed URLs are exactly the ones with backlinks nobody remembered existed.