How to Migrate a Website Without Losing SEO
A website migration does not have to cost you rankings. Follow this structured process to protect your organic traffic through every step of the move.
To migrate without SEO loss: keep URL structure or implement 301 redirects, update the sitemap, preserve meta tags, maintain internal links, update Search Console, and monitor rankings for 30 days post-migration.
Pre-migration checklist
Doing these things before you touch anything means the difference between a clean migration and a traffic disaster.
- Benchmark current rankings. Document your current positions for your top 20 keywords. Use Google Search Console or an SEO tool.
- Record all current URLs. Export a full list of indexed URLs from Search Console. This is your URL map.
- Log performance metrics. Note your current organic traffic, conversion rate, and Core Web Vitals scores.
- Back up everything. Full site backup: files, database, and configuration.
- Set up the new environment. Build the new site on a staging URL or subdomain. Keep the old site live until migration day.
- Test in staging. Verify all pages, forms, and functionality on the new site before cutting over.
URL mapping method
The single most important SEO step in a migration: every old URL must map to exactly one new URL. No exceptions.
For each URL in your old site, decide:
- Same URL. If the new site keeps the same path, no redirect needed. This is the safest option.
- New URL, same content. One-to-one 301 redirect from old to new. Each page gets its own redirect.
- Merged content. If multiple old pages are combined into one, redirect all old URLs to the single new page.
- Removed content. Redirect to the closest relevant category or parent page. Never redirect to the homepage.
Create a spreadsheet with two columns: Old URL and New URL. Every old URL gets exactly one new URL. This spreadsheet is your redirect map.
Redirect implementation
Implementing redirects correctly is the technical core of an SEO-safe migration.
| Redirect type | When to use | Implementation |
|---|---|---|
| 301 (permanent) | Content has permanently moved to a new URL | Server-level redirect via .htaccess (Apache) or config (Nginx) |
| 302 (temporary) | Only for temporary moves (rare in migrations) | Same methods as 301 but indicates temporary |
| Wildcard redirects | Entire directory structure has changed | Redirect /old-category/* to /new-category/* |
| Regex redirects | Complex URL patterns (e.g., date-based URLs) | Use regex matching in .htaccess or redirect plugin |
After implementation, test every redirect manually. Use a browser or a redirect checker tool. Confirm that each old URL redirects (301, not 302) to the correct new URL.
Post-migration monitoring
The 30 days after migration are critical. Here is what to watch:
- Week 1: Check Search Console daily for crawl errors, 404s, and indexing issues. Update your sitemap and resubmit.
- Week 2: Monitor organic traffic daily. A small dip is normal (5–15%) in the first week. A drop below 20% needs investigation.
- Week 3: Check rankings for your top keywords. Some fluctuation is expected as Google re-indexes the new URLs.
- Week 4: Compare against pre-migration benchmarks. Traffic should be recovering. If not, audit your redirects and internal links.
Common ranking drops and fixes
If you see a traffic drop, here are the most common causes and their fixes.
| Symptom | Likely cause | Fix |
|---|---|---|
| Traffic drops 30%+ immediately | Missing or incorrect 301 redirects | Audit all redirects. Test old URLs. Fix broken mappings. |
| Pages not indexed | Sitemap not updated or submitted | Generate new sitemap. Submit in Search Console. Request indexing. |
| Rankings dropped but pages indexed | Internal links not updated | Update all internal links to point to new URLs. |
| Traffic slowly declining | Lost backlink equity | Check backlinks pointing to old URLs. Request updates from linking sites. |
| Site appears in search with wrong title/desc | Meta tags lost in migration | Verify meta tags on all pages. Use Search Console's URL inspection tool. |
Timeline
Here is a realistic migration timeline for a standard business website (up to 100 pages):
| Phase | Duration | Key actions |
|---|---|---|
| Pre-migration preparation | 1–2 weeks | Benchmarking, URL mapping, staging setup, content review |
| Build and test | 2–4 weeks | Build new site on staging, test all pages and redirects |
| Migration day | 1 day | DNS cutover, deploy redirects, submit sitemap |
| Post-migration monitoring | 30 days | Daily monitoring, fix issues as they appear |
| Full recovery | 4–8 weeks | Traffic and rankings should stabilise at or above pre-migration levels |
Need help with an SEO-safe migration? Contact BahrainServer — we handle the entire process end to end.
Frequently asked questions
No. A properly executed migration with correct 301 redirects, updated sitemaps, and preserved meta tags should cause minimal traffic loss. Most sites recover fully within 4–8 weeks. The damage comes from bad redirects or broken URLs.
Most sites see a small dip (5–15%) in the first 1–2 weeks, then recover to baseline by week 4–6. Full recovery including ranking improvement typically takes 4–8 weeks.
Keeping the same URL structure is always best for SEO. If URLs must change, implement one-to-one 301 redirects from every old URL to its new equivalent. Never redirect multiple old URLs to the same new URL unless the content is merged.
The biggest mistake is moving without documenting current URLs, rankings, and traffic. Without a baseline, you cannot measure the impact. The second biggest is redirecting everything to the homepage instead of mapping pages one-to-one.
Yes. Submit a new sitemap in Google Search Console and use the 'Request Indexing' tool for critical pages. Also update your address in Search Console if the domain changed.